Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2017 Scrum by Picture

994 views

Published on

The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.

Published in: Technology
  • Login to see the comments

2017 Scrum by Picture

  1. 1. SCRUM BY PICTURE 2017
  2. 2. based on The Scrum GuideTM November 2017 prepared by Paweł Lewiński
  3. 3. empiricism - knowledge comes from experience - make decisions based on what is known
  4. 4. THEORY
  5. 5. transparency - the process visible to those responsible for the outcome - observers share a common understanding of what is being seen
  6. 6. inspection frequently inspect: - Scrum artifacts - progress toward a Sprint Goal to detect undesirable variances
  7. 7. adaptation if any aspect of a process deviate outside acceptable limits process must be adjusted as soon as possible
  8. 8. VALUES
  9. 9. SCRUM TEAM
  10. 10. self-organizing choose how best to accomplish their work
  11. 11. cross-functional have all competencies needed to accomplish the work
  12. 12. Product Owner - one person - maximizing the value of the product - managing the Product Backlog - the entire organization must respect PO decisions
  13. 13. Development Team - professionals who do the work of delivering a potentially releasable increment of "Done" product at the end of each Sprint - empowered to organize and manage their own work - 3 to 9 members - no sub-teams - no titles for members
  14. 14. - responsible for promoting and supporting Scrum - helping everyone understand Scrum - servant-leader for the Scrum Team - serves the Product Owner, the Development Team and the Organization Scrum Master
  15. 15. EVENTS
  16. 16. Sprint - time-box of one month or less - creates useable, and potentially releasable product Increment new starts immediately after the conclusion of the previous
  17. 17. Sprint - no changes are made that would endanger the Sprint Goal - quality goals do not decrease - scope may be clarified and re- negotiated
  18. 18. - what can be done this Sprint? - how will the chosen work get done? - time-box of eight hours or less Sprint Planning
  19. 19. Sprint Goal an objective set for the Sprint that can be met through the implementation of Product Backlog - it provides guidance - gives some flexibility - As the Development Team works, it keeps the Sprint Goal in mind
  20. 20. Sprint Planning: what - Development Team forecast the functionality that will be developed - all collaborates on understanding the work of the Sprint - the number of items selected from the Product Backlog is solely up to the Development Team
  21. 21. Sprint Planning: how - Development Team decides how it will build this functionality into a "Done" product Increment - The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog - enough work is planned - The Product Owner can help to clarify the selected Product Backlog items
  22. 22. Daily Scrum - 15-minute time-boxed - Development Team plans work for the next 24 hours - inspect progress toward the Sprint Goal - the Development Team should understand how it intends to work together as a self-organizing team to accomplish the Sprint Goal - an internal meeting for the Development Team
  23. 23. Sprint Review - the presentation of the Increment is intended to elicit feedback and foster collaboration - held at the end of the Sprint to inspect the Increment and adapt the Product Backlog - all collaborate about what was done in the Sprint - result of the Sprint Review is a revised Product Backlog - max four-hour meeting for one-month Sprints
  24. 24. Retrospective - an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint - occurs after the Sprint Review and prior to the next Sprint Planning - the Scrum Team plans ways to increase product quality by improving work processes - max three-hour meeting for one-month Sprints
  25. 25. ARTIFACTS
  26. 26. - an ordered list of everything that is known to be needed in the product - The Product Owner responsibility - dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful - higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones Product Backlog
  27. 27. Sprint Backlog - the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal - includes at least one high priority process improvement identified in the previous Retrospective - emerges during the Sprint - belongs solely to the Development Team
  28. 28. Artifact Transparency - Scrum relies on transparency - The Scrum Master’s job is to work with the Scrum Team and the organization to increase the transparency - Transparency doesn’t occur overnight, but is a path
  29. 29. Definition of "Done" - everyone must understand what "Done" means - Development Teams deliver an useable Increment of product functionality every Sprint
  30. 30. Creative Commons License Attribution This is a derivative work by Paweł Lewiński based on the Scrum Guide ©2017 by Scrum.Org and ScrumInc, available at http://scrumguides.org. Offered for license under the Attribution Share-Alike license of Creative Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at http://creativecommons.org/licenses/by-sa/4.0/. By utilizing this Scrum Guide you acknowledge and agree that you have read and agree to be bound by the terms of the Attribution ShareAlike license of Creative Commons. This work is not associated with Scrum.org nor Scrum Inc in any way.

×