4. Scrum Events

Question 1

What are the four scrum Events?

Answer 1

• Sprint planning
• Daily scrum
• Sprint Review
• Sprint Retrospective

All these meetings have to be time boxed!

Question 2

The scrum events, are time boxed, how much time is set apart?

Answer 2

• Backlog refinement = no more than 10% of the development team’s capacity
• Sprint planning = max 8 hrs for monthly sprints, shorter for more frequent sprints
• Sprint Review = 4hrs
• Sprint Retrospective = 3 hrs

The idea behind these events is loads of opportunity to inspect and to adapt. These scrum events reduce the need of other formal meetings. Efficient. But also still comunication around this events if necessary.

Question 3

the Sprint

Answer 3

Agile fancy word for a period of time

During which a potentially relaesable product increment is created. Show the customer, get feedback, decide on the goal of the next sprint. It’s all about adaptability.

No longer than 1 month, no less than 1 week, 2 weeks is quite popular. How often do iterations need releasing, what is sensible for development pace and people’s diaries.

• Understand what the requirements are
• What is needed from the customers right now?
• Consider work items for the sprint
• Discuss with development team for what is achievable
• Discuss and decide on the Sprint Goal
• Choose the work items from the Product backlog should go into this Sprint to Achieve the Sprint goal

Question 4

1. The Sprint planning

Answer 4

Product owner enters with a goal in mind and current information of the product and market, preferably product backlog refinement.

The Scrum Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice. The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting.

Product owner with developer create sprint goal.

Answer three questions:
1. Why sprint valuable
2. What can be Done in this sprint?
3. How will chosen work get done?

these three questions are build into the sprint goal and sprint backlog

Developers themselves are responsible for creating the increment during the sprint.

Product owner can cancel sprint if sprint goal becomes obsolete.

Question 5

2. The Daily scrum

Answer 5

Short daily meeting for developers by developers

No need for management or other members to be forced to be there. The purpose of the Daily scrum is to inspect progress toward the Sprint Goal and Adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. A chance to review progress, keep the vision alive and the goal in sight → Sprint goal

Done yesterday
Doing Today
Blockers

Question 6

3. The sprint review

Answer 6

Entire scrum team, working session, Review what was done and not completed in sprint. Understand what the customer needs, in future increments, should be done.

PO is looking to get:
- Sense of progress
- Clarify what is need from newt sprint
- Satisfying customer requirements
- Product backlog items for next sprint

Question 7

4. Sprint Retrospective

Answer 7

A meeting for improvement by the scream team, How did we do last sprint?

• Teamwork
• Processes
• Tools
• Planning