Communicating pain points to team members
It is important that team members are able to effectively communicate the particular pain points or blockers that are inhibiting progress. There are several pain points we will discuss in this section, including waiting for requirement information, undocumented steps in the deployment pipeline, too many holders of keys to the kingdom, and too many communication channels.
Waiting for requirements information
It is often the case that developers will start work on a particular story/feature and not have all the necessary requirements in order to complete their assigned work. This is especially problematic for developers because whatever code they work on might need to be scrapped and redone depending on how far off the requirements were from being done correctly. Developers need all the requirements up front before they can start on a story; there must exist processes for each feature to work in grabbing all the requirements, and each story ideally...
