It is also very important that all activities are planned during a sprint that needs to be done to meet the Definition of Done (more about this later in this post). To avoid problems in Sprint Planning, the team members must spent about 10% of their sprint time, looking at backlog items for the next sprint or the next 3 or 4 sprints. As I described in ( Part 2 and Part 3) grooming is a constant activity that needs to be done by all team members. However, what most teams forget is that there is always the next sprint. When all tasks of a specific PBI are done, the Product Owner validates the Acceptance Criteria, validates the Definition of Done and “stamps” the PBI as “done” when all of these criteria are met.īasically this is what a sprint contains. During the sprint the team updates the Product Owner and shows the intermediate results. The three questions that need to be answered are: Every day the team comes together during their Daily Standup meeting and tell each other how they are doing. The team made a breakdown in tasks and this is exactly where to start working on. During the sprint the team focuses on the Product Backlog Items that were selected during Sprint Planning. When sprint planning is done, it is time to get to work. Where grooming is used, you can replace that with refinement. Nowadays this is known as backlog refinement and refining. Using TFS in your Sprint Review and Retrospectiveĭisclaimer: Within these series I talk about backlog grooming a lot. Using TFS for grooming your Product Backlogĥ. You can find more introduction in part 1Ģ. The series is based on my session that I presented at Microsoft TechDays. This is the fourth part of the series TFS as perfect tool for Scrum.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |