Sprint-plannings, Backlog-grooming And Sprint-retrospectives

Updated 3,290 Days AgoPublic

Actions

Sprint Planning meeting:

The Kolab sprints begins with the sprint planning meeting. At this meeting, the team negotiate which Tasks from the backlog the team will work on during the next sprint. The meeting is happening during (the end) of the current sprint. The meeting is online, and needs to be limited to 2 hours. If 2 hours is not enough, a new meeting will need to be planned.

The team is looking at the backlog (in Phabricator) in the workboard of #sprint_xxx_next, where the Product Owners already has placed the highest priority tasks of the product backlog. The team evaluates each task from the top down, give it story-points, and evaluates how much of the backlog can be done. The Process Managers remove the #sprint_xxx_next tag from the tasks if they are estimated not to be done in this sprint. These tasks will then not be visible in the sprint backlog anymore.

Backlog grooming:

Sprint retrospective: