3. Estimation Meetings
•Preparation for
Sprint Planning
•Formal estimation
•Have at least two
meetings per
Sprint
•Estimate only Size
not Time
•Provides input for
Release Planning
3
4. Sprint Planning - Part 1
The team should
review and analyze
the:
•Product Backlog
•Team capabilities
Business
•
conditions
Technology
•
stability
Executable
•
product increment
4
5. Sprint Planning - Part 2
And then analyze
and design the:
•Sprint Goal
•Selected
Product
Backlog
In order to get the
Sprint Backlog
5
6. Daily Scrum Meeting
•Daily 15 minute meeting
•Same place and time every
day
•Team room - with task
board
•Chickens and pigs
•Three questions:
What have you
•
ACHIEVED since last
meeting?
What will you ACHIEVE
•
before next meeting?
• What is in your way?
Impediments and
•
Decisions
6
7. Sprint Review
•Attended by the
Scrum Team + all
interested
stakeholders
Review Selected
•
Product Backlog
•Show built (done)
functionality
Groom Product
•
Backlog based on
outcome of Sprint and
conversation
• Set next Sprint goal
7
8. Evaluation
Consequences
•Move back to the backlog
unfinished work and
reprioritize it
•Review the backlog to see
if it’s still current
•Decide to make changes in
team configuration and
tasks assignation
•Changes in team
configuration might include
(not recommended) adding
extra muscle to try to keep
on schedule or sped up
production
8
9. Sprint Retrospective
•Team meets with
Scrum Master to
inspect and adapt
their process
Team devises
•
solution to one or two
most important
problems
•Changing everything
at the time is not
possible, the true and
lasting improvement
comes for small but
sustainable changes 9
