A sprint is a short time period which a scrum team takes to complete a specific task. Scrums use sprints to manage projects which allow the teams to produce quality work fast and frequently as well as be flexible to adapt to change.
Executing Scrum Sprints
Sprint planning is where the team meets to discuss what work will be done in the sprint and how the work will be done.
Daily scrums are held to know the progress of the task.
Sprint review is where the team demonstrates what they have done before the work is pushed to production.
The sprint retrospective is where the team discusses areas that need improvement.
Things to note
-
During the sprints ensure that the team understands the goal and the metrics to how success will be measured
-
Have a clear backlog with the dependencies and priorities in order
-
Have an understanding of velocity and how it reflects on team meetings
-Use sprint planning to get specific details of the task that needs to be done
-
When a decision is made it should be noted for everyone to know
-
Have achievable tasks, avoid taking in too much work.
-
Schedule time for quality assurance and engineering health
-
Listen to concerns raised by the team and act on them, do not ignore
Sprint planning
The sprint planning involves the product owner describing the objective and backlog that are aligned with the task. The team plans the work to deliver the sprint goal. In sprint planning, the team and product owner should all be present it cannot take place without either of them. The product backlog acts as the input of the sprint with a list of items to be done. The output is the team working towards the goal of the sprint.
Prepping for sprint planning meeting
Set a time limit for sprint planning
Focus on the outcome, there is no perfect plan.
Estimates will be required but estimate what you know