When agile development teams commit to getting user stories done, it’s often in the face of several unknowns around the implementation, team dependencies, and technology assumptions.

Let’s say there’s a value stream tied to a product with multiple agile development teams working on enhancements and several IT operation teams involved in support functions.

In software development the traditional approach, dubbed ‘Waterfall‘, is linear and breaks the development phases into increments of Analysis, Design, Coding and Testing. A common constraint ...