01_Sprint - Facts & Rules

Source:  Agile Project Management with Scrum by Ken Schwaber

 

Duration:

 

1.       Time-boxed to 20 consecutive calendar days (04 Weeks) 

2.       This is the amount of time required for a Team to build something of significant interest to the Product Owner and stakeholders and bring it to a state where it is potentially shippable.

3.       This is also the maximum time team can work, before it requires artifacts and documentation to support its thought processes.

4.       This is also the maximum time that most stakeholders will wait without losing interest in the Team’s progress and without losing their belief that the Team is doing something meaningful for them.

5.       Well, selection of iteration length should be guided by the following factors:

a.       The length of the release being worked on

b.       The amount of uncertainty

c.        The ease of getting feedback

d.       How long priorities can remain unchanged

e.       Willingness to go without feedback

f.         The overhead of iterating

g.       A feeling of urgency is maintained

 

 

PB Change During Sprint:

 

6.       Team commits to PB during the Sprint planning meeting. No one is allowed to change this Product Backlog during the Sprint. PB is frozen until the end of the Sprint.

7.       Team can add or remove items after consulting with the Product Owner, during the current Sprint.

 

8.       If the Sprint proves to be not viable, due below reasons, the ScrumMaster can abnormally terminate the Sprint and initiate a new Sprint planning meeting to initiate the next Sprint.

a.       If the technology proves unworkable,

b.       if the business conditions change so that the Sprint will not be of value to the business, or

c.        if the Team is interfered with during the Sprint by anyone outside the Team.

 

9.       The Scrum Master can make this change on his/her  own accord or as requested by the Team or the PO.

 

 

Team Responsibility During Sprint:

 

10.    The Team members have below administrative responsibilities during the Sprint:

a.       Attend the Daily Scrum meeting, and

b.       Keep the Sprint Backlog up-to-date.

c.        Keep updated day-to-day hours remaining for each task.

d.       New tasks must be added to the Sprint Backlog as they are conceived

 

Keep Blogging...

Regards,

Arun Manglick