The immediate impact of Scrum Masters (and how reducing committed work leads to more delivery)

Share:
  1. How important is a Scrum Master to a team?
  2. Can an experienced Scrum Master with no domain knowledge have an immediate impact on a team?
  3. How important are realistic sprint commitments?

Here’s a quick article answering all the above questions. Spoiler alert: The short answers are (1) Very, (2) Yes and (3) Very. Continue reading “The immediate impact of Scrum Masters (and how reducing committed work leads to more delivery)”

Share:

6 Reasons: From 12 Months to 2 Weeks for Feature Delivery

Share:

This article is a supplementary appendix to the post: The Power of Feature Hypotheses.

Where We Were: 12 Months to Deliver a Small Feature

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.

An example of a small feature that took 12 months to deliver in waterfall. In agile this can easily be done in two weeks.

Continue reading “6 Reasons: From 12 Months to 2 Weeks for Feature Delivery”

Share: