• Planned at the beginning of an iteration
•The volume of work the team can commit
to getting “DONE” within the iteration ...
Upcoming SlideShare
Loading in …5
×

Scrum methodology Infographic

1,096 views

Published on

Another one-pager presenting the mechanics of the scrum methodology on a small (but quite complete) infographic

Published in: Business
1 Comment
2 Likes
Statistics
Notes
No Downloads
Views
Total views
1,096
On SlideShare
0
From Embeds
0
Number of Embeds
306
Actions
Shares
0
Downloads
10
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

Scrum methodology Infographic

  1. 1. • Planned at the beginning of an iteration •The volume of work the team can commit to getting “DONE” within the iteration time box (e.g. 2 weeks) • The Scrum Master protects the team from changes to the committed work within the Iteration •Daily status meeting 15 minutes or less •Held in front of the user story wall •Team members answer three questions What have I done since we last met? What will I do before we next meet? What impediments do I face? •Iteration burndown chart updated •Open meeting for all, only team members can talk •Product Backlog prepared prior to meeting •Top priority items are selected from the product backlog •Team select items to commit to complete in iteration (referring to estimates) •Product owner available to answer questions •Update release plan • “DONE” work within the iteration should be of production quality Roles Team Member •Team containing all required skills •Responsible for iteration delivery •Responsible for iteration planning •Empowered to deliver iteration plan Product Owner •Accountable for product success •Defines all product features •Responsible for building / maintaining product backlog •Responsible for prioritising product backlog •Is available to answer the team questions Scrum Master •Conducts the daily stand-up •Removes blockers •Shields the team for external interference •Conducts iteration retrospective •Is a facilitator not a manager •Guardian of the iteration process •Maintained by the product owner but anyone can contribute •Needs to be groom every iteration •The one source of truth for product requirements •One backlog per product •Analysis done on highest priority items first •Team reflects on the teams performance and experiences during the iteration •Team identifies possible improvement actions and agrees on approach for the next iteration •Team present “DONE” work from the iteration plan •Showcase working software •Get feedback from product owner and stakeholders •Potentially update the product backlog from feedback gathered •Update release burn up chart

×