Agile rituals (shared) 05 2011
-
Upload
designed-culture -
Category
Business
-
view
1.538 -
download
1
Transcript of Agile rituals (shared) 05 2011
Rituals of ScrumWhy are they important?
Erin Beierwaltes | agileaction.blogspot.com
How do we keep Scrum going?
Erin Beierwaltes | agileaction.blogspot.com
Scrum Framework
Roles
• Product Owner
• ScrumMaster• Team
Rituals
• Daily Scrum• Sprint
Planning• Sprint Review• Sprint
Retrospective
Artifacts
• Product Backlog
• Sprint Backlog
• Burndown Chart
Erin Beierwaltes | agileaction.blogspot.com
Rituals
Sprint Planning
Daily Scrum
Meeting
Sprint Revie
w
Sprint Retrospective
Erin Beierwaltes | agileaction.blogspot.com
Sprint Planning Basics
Team selects User Story from the
product backlog they can commit to
completing
Sprint backlog items are created for the
User Story. Collaboratively.
Repeat until team can no longer commit. (Use velocity as a
check point)
Erin Beierwaltes | agileaction.blogspot.com
1. Select a Sprint Goal/Theme2. Product Owner presents
User Story3. Team accepts or declines
story after discussion with Product Owner (NOT a design session)
4. Team creates tasks in hours5. Product Owner continues to
present stories in priority order team capacity is reached
6. Team makes final sprint commitment (Fist of Five)
Sprint Planning
Team Capacity
Product Backlog
Current Product
Retrospective Action
Items
Sprint Goal
Sprint Backlog
VelocitySprint
Commitment
Erin Beierwaltes | agileaction.blogspot.com
How is your Sprint Planning going?
1. Are stories ready for consumption?2. Are you over-committing?3. Is the whole team engaged?4. Did you remember to include
technical debt and retrospective action items?
Erin Beierwaltes | agileaction.blogspot.com
Daily Scrum Basics
What did you do yesterday?
What will you do today?
Is anything in your way?
1
2
3
Erin Beierwaltes | agileaction.blogspot.com
Daily Scrum
WHAT IT IS
Daily 15 minutes Stand-up Everyone is invited
(this means the whole world)
Helps avoid other unnecessary meetings
WHAT IT IS NOT
Not a status meeting for ScrumMaster
Not for problem solving
Those not in scrum “roles” should not speak (talk to the ScrumMaster after)
Erin Beierwaltes | agileaction.blogspot.com
How is your Daily Scrum going?
Are the engineers talking directly to you?
Do conversations get into detail? Do team members every ask for
help?
Erin Beierwaltes | agileaction.blogspot.com
Sprint Review Basics
Team demonstrates working software
Erin Beierwaltes | agileaction.blogspot.com
Sprint Review
Team presents what it accomplished during the sprint (based on the agreed definition of “done”)
Demo of working, live software One demo stories that are “DONE” NO SLIDES Entire team participates Invite the World Final acceptance of stories (velocity) Review backlog and add/modify stories
Erin Beierwaltes | agileaction.blogspot.com
How is your Sprint Review going?
How is your definition of “done”? Who’s attending? Who’s demo-ing every week? Are you leaving acceptance to this
meeting?
Erin Beierwaltes | agileaction.blogspot.com
Sprint Retrospective Basics
Gather Data
(start, stop, continue)
Discuss and
Brainstorm
Create Action Items
Erin Beierwaltes | agileaction.blogspot.com
Sprint Retrospective
Review what is and what is not working with the scrum implementation
Done after EVERY sprint Whole team participation Time-boxed Create action items Formatted and Facilitated (Agile
Retrospectives by Esther Derby and Diana Larsen)
Erin Beierwaltes | agileaction.blogspot.com
How is your Retrospective going?
Do you have action items? Is everyone engaged and giving
ideas? How often does the team follow
through on the action items?
Erin Beierwaltes | agileaction.blogspot.com