1

Sprint Duration Change2 OR 3 WEEKS SPRINT?

2Check-List

1. What are your motivations and expectations for the duration change? Too long sprint: hard to keep changes out of the sprint. Too short sprint: o Struggle with completing significant work within the sprint o Weaken DoD for achieving sprint done

3Check-List

Motivations or Problems for increasing sprint length Struggling for splitting stories Too long meetings Deployment – Integration is too hard Waiting time for getting feedbacks Dependency on another party “We can’t get anything done in two weeks”

4Check-List

2. Does every team member aware of the change, the motivations and expectations?

The whole team – that collective of ScrumMaster plus product owner plus team members such as programmers, testers, designers, DBAs, analysts… should be the ones that gets to select a sprint length

When in conflicts, who is the one to decide? Scrum Master or Product Owner?

5Check-List

3. What are the first feedbacks from team members? Are you running “trial” sprints after the changes? Is there a public pages that we can collect the ideas from team

members? Is there a change timeline?

6Check-List

4. What are the impacts of the changes to Scrum activities and Scrum members?

Unfreeze – Change – Refreeze

73 Weeks Sprint

Sprint Duration change won’t fix the general issues on team commitment, loosing the big picture, team integration. Instead, what increasing time helps the team is to reduce the overhead costs and reduce the pressure on running other quality control and integration activities.

Longer sprint does not mean more complicated stories

93 Weeks Sprint – Being Aware of the Cultural Reactions

Temporarily Activities get done, or get done efficiently Change is slowly taking effect Time is a process which belong to others as well

103 Weeks Sprint – Experiment

Changes in sprint duration can or can not take immediate effect Expectations: increase in average velocity (because of higher

performance or because of less overhead time), and what else? Scrum Master should be the one monitor and ensure the team

running with its best performance in given condition. SM should be objective, informed and should have only one “bias” is toward Scrum.

113 Weeks Sprint – Experiment

The boots-on-the-ground reality: will there many changes when shift from two weeks to three weeks sprint?

Time allocated for testing and preparing for the sprint review will be squeezed

123 Weeks Sprint – Experiment

Simple Rules should be strongly agreed and kept: Pick up more stories opportunistically Deliver functionality earlier in the iteration Allocate time to test Prepare for the sprint review from the start Visibility to all team challenges