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 will have acceptance tests as an action item for the feature work to be considered done. In an ideal world, developers would have all the necessary information ready ...
Waiting for requirements information
Get Hands-On Continuous Integration and Delivery now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
