2 WEEK SPRINTSTHE SPRINT OF CHAMPIONS

2 WEEK SPRINTS - WHY

• Reduce waterfall behavior• Increase client interaction• Improve estimates• Improve predictability• Encourage better stories• Increase business value (ROI)• Promote continuous improvement• Enhance innovation & agilty

2 WEEK SPRINTS – WHAT IS REQUIRED

• Product owner engagement • Consistent estimates • Vertically story slicing• 2 - 3 sprints of ready stories

EFFECTIVELY ESTIMATE

EFFECTIVELY ESTIMATE – 5 POINTS CAP

• Keeps water fall behaviors out• Estimates are more accurate • Reduce cost of wasted stories• Reduce risk of low value

features• Increases consistency and

predictability of sprints• Improves product innovation

EFFECTIVELY ESTIMATE - HOW

• Start with a baseline story:• 12 to 14 work hours• Had very little complexity• Had very little unknown• Had no dependences• Satisfied with finished product

• Call this an effort of 2

ESTIMATE STORIES

ESTIMATE STORIES

VERTICALLY SLICING USER STORIES

• A vertically sliced user story will be:• Independent (complete):• Analysis • Coding• Testing

• Valuable (to the user):• Increase revenue & efficiency, avoids cost• Create future options or awareness• Increase innovation

VERTICALLY SLICING USER STORIES - ITERATION

9 VERTICALLY SLICING PATTERNS1. Workflow Steps2. Operations3. Business Rule Variations4. Variations in Data5. Interface Variations6. Major Effort7. Simple/Complex8. Defer Performance9. Break Out a Spike (As a Last Resort)

LAST SLIDEQuestions…