Sprints are ideally 30 day cycles, where the team works on a subset of the features from the product backlog, which is agreed upon by the team, the scrum master and the product owner during the sprint planning meeting ( 1 day meeting for 30 day sprints). This subset of the features, which are taken up for production during the sprint is known as the sprint backlog.
Sprints should be ideally of same duration. This is becuase, over a period of time the team will learn to accurately estimate what they can achieve during a specific time frame. Once the sprint durations fluctuate, the team will never learn to estimate the work. It is not necessary that sprints should be 30 day cycles. For our projects, we are doing 6 day sprints, where at the every week, a new set of features are released.
Sprint backlog feature in CollabTeam
The above screenshot is the collabteam screen for creating sprints. The entries on the left are the product backlog. Against the entries in the product backlog (not yet developed), check boxes are provided to choose the features for the sprint under consideration. The selected features from the product backlog are transferred to the sprint backlog.
No comments:
Post a Comment