Scrum in 30min
- 1. Ingo Matzner IT-Consulting Scrum Framework Ingo Matzner | 15.02.18
- 2. 15.02.18 Scrum Framework 2 Ingo Matzner IT-ConsultingAgenda Agile Manifesto Definition of Scrum Scrum Theory Scrum Values Scrum Team Scrum Events Scrum Artifacts Artifacts Transparency Definiton of Done Sprint Task Board
- 3. 15.02.18 Scrum Framework 3 Ingo Matzner IT-ConsultingAgile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 4 Values
- 4. 15.02.18 Scrum Framework 4 Ingo Matzner IT-ConsultingDefinition of Scrum Lightweight Simple to understand Difficult to master Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. The Scrum framework consists of: Scrum Teams and their associated roles Events Artifacts Rules
- 5. 15.02.18 Scrum Framework 5 Ingo Matzner IT-ConsultingScrum Theory Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from: experience + making decisions based on what is known. Scrum employs an: iterative, incremental approach to optimize predictability and control risk.
- 6. 15.02.18 Scrum Framework 6 Ingo Matzner IT-ConsultingScrum Values & Pillars = TRUST Commitment Courage Focus Openness Respect Transparency Inspection Adaption
- 7. 15.02.18 Scrum Framework 7 Ingo Matzner IT-ConsultingScrum Team Product Backlog - - - - - - Sprint Backlog - - - - - - Scrum Guide - - - - - - Product Owner Development Team Scrum Master
- 8. 15.02.18 Scrum Framework 8 Ingo Matzner IT-ConsultingScrum Events Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Sprint
- 9. 15.02.18 Scrum Framework 9 Ingo Matzner IT-ConsultingScrum Events – Sprint Time-Box event of 4 weeks or less A useable and potentially releasable Increment of „Done“ is created Sprint Planning, Daily Scrums, Dev-Work, Sprint Review, Sprint Retro Each Sprint has a goal of what is to be built Sprint
- 10. 15.02.18 Scrum Framework 10 Ingo Matzner IT-ConsultingScrum Events – Sprint Planning Sprint Planning Time-Box of max 8h for a four weeks Sprint The entire Scrum-Team colloaborates during Sprint Planning What can be delivered in the Increment of this Sprint? How can the work be achieved? Product Backlog - - - - - - Dev-Team Capacity + Past Performance + +Last Increment
- 11. 15.02.18 Scrum Framework 11 Ingo Matzner IT-ConsultingScrum Events – Daily Scrum 15min time-boxed event for the DEV-Team Every day of the Sprint Inspecting work since last Daily and forecasting work Inspect progress towards the Sprint Goal What did I do yesterday to achieve the Sprint Goal? What will I do today to meet the Sprint Goal? Do I see any impediments which prevent the Sprint Goal? Daily Scrum
- 12. 15.02.18 Scrum Framework 12 Ingo Matzner IT-ConsultingScrum Events – Sprint Review 4h meeting for Sprint of four weeks or less Inspect the Increment and adapt the Prodcut Backlog Informal meeting for Product Demo, not a status meeting Scrum-Team and key stakeholders invited by the Product Owner Product Owner explains which Product Backlog items have been „Done“ Review of the timeline, budget, potential capabilities Attendees collaborate on the next things that could be done to optimize value Sprint Review
- 13. 15.02.18 Scrum Framework 13 Ingo Matzner IT-ConsultingScrum Events – Sprint Retrospective 3h event for the Scrum-Team Scrum-Team inspects itself and creates a plan for improvements How went the last Sprint with regards to people, relationships, processes, and tools Identify and order items that went well and potential improvements Sprint Retrospective Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation
- 14. 15.02.18 Scrum Framework 14 Ingo Matzner IT-ConsultingScrum Artifacts Product Backlog - - - - - - Sprint Backlog - - - - - - Increment
- 15. 15.02.18 Scrum Framework 15 Ingo Matzner IT-ConsultingProduct Backlog Product Backlog - - - - - - Dynamic Never complete Ordered list of everything that is known to be needed in the product Single source of requirements for changes Product Owner is responsible for its content, availability and ordering Lists all features, functions, requirements, enhancements and fixes Attributes of a Product Backlog item are description, order, estimate and value
- 16. 15.02.18 Scrum Framework 16 Ingo Matzner IT-ConsultingSprint Backlog Sprint Backlog - - - - - - Selected items from the Product Backlog Forecast of the Dev-Team which functionality will be in the next Increment Dev-Team modifies the Sprint Backlog during Sprint Only the Dev-Team is responsible for the Sprint Backlog Highly visible, real-time picture of work during the Sprint
- 17. 15.02.18 Scrum Framework 17 Ingo Matzner IT-ConsultingIncrement Sum of all Product Backlog items completed during a Sprint + the value of the Increments of all previous Sprints At the end of a Sprint a new Increment must be „Done“ It must be in useable condition and meet the Dev-Team‘s criteria of „Definition of Done“ Product Owner decides if the Increment is released to Production Increment Ready Sprint 1 DoneDoneDone Sprint 2 Sprint n Ready Ready
- 18. 15.02.18 Scrum Framework 18 Ingo Matzner IT-ConsultingArtifact Transparency Scrum relies on Transparency The Scrum Master must work with the Product Owner, Dev-Team, and other involved parties for complete artifact transparency This work involves learning, convincing and change Transparency doesn‘t occur over night, but is a path Product Backlog - - - - - - Sprint Backlog - - - - - - Increment
- 19. 15.02.18 Scrum Framework 19 Ingo Matzner IT-ConsultingDefinition of „Done“ Everyone must understand what „Done“ means Guides the Dev-Team on how many Product Backlog items can be selected for a Sprint Dev-Teams deliver an Increment product functionality every Sprint The Scrum Team needs to create a definition of „Done“ Each Increment is additive to all other Increments and thoroughly tested Definitions of „Done“ will expand over time and mature
- 20. 15.02.18 Scrum Framework 20 Ingo Matzner IT-ConsultingSprint Task Board Story Epic To Do WiP Blocked Done Epic #1 Story #1 Story #2 Story #3 Task 5 Task 3 Task 4 Task 2 Task 1Task 6 Epic #2 Story #1 Story #2 Story #3 Epic #3 Story #1 Story #2 Task 5 Task 3 Task 4 Task 8 Task 1Task 6 Task 7 Task 2 Task 10 Task 1 Task 4 Task 8 Task 3 Task 6 Task 7 Task 5 Task 9 Task 2
- 21. 15.02.18 Scrum Framework 21 Ingo Matzner IT-ConsultingGet in touch Ingo Matzner | IT-Consulting | [email protected]
- 22. 15.02.18 Scrum Framework 22 Ingo Matzner IT-ConsultingBackup Slides
- 23. 15.02.18 Scrum Framework 23 Ingo Matzner IT-Consulting12 Principles Customer satisfaction through early and continuous software delivery Accommodate changing requirements throughout the dev process Frequent delivery of working software Collaboration between the business stakeholders and developers throughout the project Support, trust, and motivate the people involved Enable face-to-face interactions 12 Principles
- 24. 15.02.18 Scrum Framework 24 Ingo Matzner IT-Consulting12 Principles Working software is the primary measure of progress Agile processes to support a consistent development pace Attention to technical detail and design enhances agility Simplicity Self-organizing teams encourage great architectures, requirements, and designs Regular reflections on how to become more effective 12 Principles