Mind map
Scrum Events
Map content
Scrum Events
The Sprint
- a working product increment
- is developed
- duration 2 weeks or one month
- This duration remains constant
- for all sprints in the project
- This duration remains constant
- Provides guiadance to the team
- on why it is building the increment
- Thus each Sprint is associated with it
- definition of what is to be built
- design
- flexible plan
- that will guide building it
- development work
- resultant product increment
- Thus each Sprint is associated with it
- on why it is building the increment
- a working product increment
Sprint Retrospective
- Duration
- 1 hour
- 2 weeks duration sprints
- 3 hours
- one month duration sprints
- 1 hour
- Purpose
- Combine learnings from the last Sprint
- To People
- Relationships
- Process and Tools
- Identify the major items
- that went well
- and potential improvements
- that went well
- Creation of a plan
- for implementing improvements
- to increase product quality
- for implementing improvements
- Combine learnings from the last Sprint
- Ocurrs
- After the Sprint Review
- Prior the next Sprint Plannig
- Duration
Daily Scrum Meetings
- Duration
- 15 minutes
- conducted daily
- 15 minutes
- understand the work
- since the last Daily Scrum Meeting
- Create a plan for the next 24 hours
- since the last Daily Scrum Meeting
- During the meeting
- each team
- explains
- What did he do yesterday that helped
- the Team meet the Sprint Goal?
- Does he see any impediments that
- prevent him or the Team
- from meeting the Sprint Goal?
- prevent him or the Team
- What will he do today to help the
- Team meet the Sprint Goal?
- What did he do yesterday that helped
- explains
- each team
- Benefits
- Improve communication within the team
- Identify impediments
- Improve the Team's level of knowledge
- Promote quickly decisions
- Duration
Sprint Planning
- The work to be performed
- is planned in the Sprint Planning Meeting
- Duration
- 4 hours
- 2 weeks sprints
- 8 hours
- one month sprints
- 4 hours
- Focuses on 2 questions
- What needs to be and can delivered
- in the Sprint Increment ?
- How will the work needed for the
- execution of Sprint be achieved?
- What needs to be and can delivered
- The inputs to this meeting
- Product Backlog
- Projected capacity of the team
- during the Sprint
- Latest Product Increment
- Past Performance of the team
- The work to be performed
Sprint Review
- A presentation of the increment
- that is getting released
- is reviewed
- that is getting released
- Objective
- obtain feedback and progress unitedly
- Scrum Master ensures that
- Meeting takes place
- Participants understand the purpose
- Meeting is focused on the required agenda
- is completed within the requiered duration
- Aspects
- The team discusses
- what went well during the sprint
- Problems
- How solve this problems
- The team demostrates
- the work that it has completed
- answers questions about increment
- the work that it has completed
- The entire group discusses
- what to do next
- The results of Sprint Review
- is an updated Product Backlog
- Product owner explains
- what Product Backlog items
- have been
- completed
- not completed
- have been
- what Product Backlog items
- The team discusses
- A presentation of the increment
Information
- Description
- Mind Map on Scrum Events, created by Erick Marroquin Vasconez on 26/10/2017.
- Created by
- Erick Marroquin Vasconez · Oct 2017
- Updated
- Oct 27, 2017
- Views
- 0
- Rating