Scrum Meetings

In Scrum, each sprint is required to deliver a potentially shippable product increment. This means that at the end of each sprint, the team has produced a coded, tested, and usable piece of software.

Show what was achieved in the Sprint.

Focus on the outcome, what the benefit is. Not report status on actions.

Changes

1. 'Refactor product in production' => 'Show the product and gathered requirements'
2. 'Meeting with workload team' => 'Show product and tell' (engagement)

The sprint planning meeting is the kickoff to every sprint.

The Planning meetings typically consist of two parts. In the first part, the team and product owner identify the backlog items that the team feels it can commit to completing in the sprint, based on experience with previous sprints. These items get added to the sprint backlog. In the second part, the team determines how it will develop and test each item. They then define and estimate the tasks required to complete each item. Finally, the team commits to implementing some or all the items based on these estimates.

Questions

• Do we already have a theme for the sprint (Increment) to formulate the sprint goal?

Retrospecitve is about self-reflection of the team.

No matter how good a Scrum team is, there is always an opportunity to improve. Although a good Scrum team will constantly be looking for improvement opportunities, the team should set aside a brief, dedicated period at the end of each sprint to deliberately reflect on how they are doing and find ways to improve. This occurs during the sprint retrospective.