Humorous Anecdotes, Observations & Accounts of Marathon Running & Agile Adventures.
In classes I teach, there is often confusion between what is a feature and what is a user story. This article is a simple analogy (a quest for sushi) that helps to explain:
This article is a supplementary appendix to the post: The Power of Feature Hypotheses.
The graphic below is an example of a feature that previously took 12 months to deliver when we were working waterfall. This was the typical cycle-time for a small feature. Larger features would usually take over two years to flow through the system. With agile, we would now expect this same feature to be complete in a two week sprint. This article provides the six main reasons for the massive cycle-time reduction.
Continue reading “6 Reasons: From 12 Months to 2 Weeks for Feature Delivery”