Summer Scrum Public
- 1. Summer Scrum A refreshing intro Angeliki Plati
- 2. What is Scrum? • Lightweight agile p.m. framework • Mainly for software development • Iterative and incremental approach
- 3. Scrum Cornerstones • Individuals and interactions over processes and tools • Working software over comprehensive documentation
- 4. Scrum Cornerstones • Customer collaboration over contract negotiation • Responding to change over following a plan
- 5. Scrum Main Components • The three roles:
- 6. Scrum Main Components • Prioritized Backlog End user requirements • Scrum Events: Sprint Planning Meeting, Daily Scrum Meeting, Sprint Review Meeting, Sprint Retrospective Meeting
- 7. Scrum Main Components • Sprints
- 8. The Scrum Team • follows the same norms and rules • is accountable for the delivery as a whole • is empowered • is working as autonomous as possible
- 9. The Scrum Team • is self organizing • has balanced member-skills • is small and has no sub-teams • has full worktime members
- 10. The Scrum Team • has collocated members Size of the Scrum Team: The ideal size is 7 +/- 2 people.
- 11. The Scrum Master • guards the Scrum Team from external requests and disruptions
- 12. The Scrum Master • acts as a change agent and adapts processes • coaches the Scrum Team • removes impediments for the Scrum Team
- 13. The Scrum Master • ensures efficient communication between the Scrum Team and the Scrum Product Owner • facilitates the various Scrum Events
- 14. The Scrum Product Owner • manages the Scrum Product Backlog • manages the releases • manages the stakeholders • works closely with the Scrum Team
- 15. The Process
- 16. Waterfall Model
- 17. Waterfall Model – Why does it fail? • Project phases strict sequential chain • Phase completed before starting the next one • Going back difficult, costly, frustrating to the team and time consuming
- 18. Waterfall Model – Why does it fail? • Project timeline planned at the start • Releasable product only at the end of the timeline • One phase delayed all phases delayed
- 19. Waterfall Model – Why does it fail? • Users try to anticipate all possibilities beforehand. • Requirement definition often difficult Many requirements change
- 20. Waterfall Model – Why does it fail? • Phases estimated separately BUT most of them work together/parallel
- 21. Waterfall Model – Conclusion Waterfall approach ok for small/simple projects risky and costly for bigger, complex projects less efficient than Scrum
- 22. Scrum – Why does it succeed? • Quality is no longer an option
- 23. Scrum – Why does it succeed? • Definition Of Done (DoD) when a feature is complete - quality - required testing - documentation … • No incomplete or untested feature will be released to the customer
- 24. Scrum – Why does it succeed? • Functionality defined throughout the project and implemented incrementally • Remain flexible, change in a controlled manner no additional costs/risks
- 25. Scrum – Why does it succeed? • End of Sprint available result • Result shown and discussed with the customer • Get and incorporate feedback as soon as possible
- 26. Scrum Effects • Increased productivity • Better product quality • Reduced or stable project costs after introducing agile methods
- 27. Scrum Effects • Higher customer satisfaction • Increased satisfaction and motivation of employees
- 28. Scrum Central Aspects • Team’s self-organization • Communication within the team • Continuous improvement: inspect & adapt
- 29. Inspect & Adapt The Scrum Team •inspects and assesses its created artifacts and processes •adapts and optimizes them
- 30. Inspect & Adapt • results get optimized • predictability increases • overall project risk gets minimized
- 31. Question • How do you perceive the meaning of flexibility in Scrum?
- 33. Some interesting quotes “Scrum is like your mother-in-law, it's constantly pointing out your shortcomings." Ken Schwaber “We don’t need an accurate document. We need a shared understanding.” Jeff Patton “If you define the problem correctly, you almost have the solution.” Steve Jobs
- 34. Some interesting quotes “The goal is NOT to write code. If we could ship products and make all this money without writing any code, we would. Your job is ship products EXACTLY on time. It doesn’t matter whether you’re a developer, tester, program manager, product manager–whatever. Everybody’s job is the same.” Chris Peters
- 35. Some interesting quotes “What does it mean to be agile? I mean, my definition is that you accept input from reality, and you respond to it.” Kent Beck “The first thing to realize when formulating your first DoD (Definition of Done) is that it isn’t cast in stone. You don’t need to spend an eternity deliberating what it should be, because it can evolve over time“ Ilan Goldstein
- 36. References • “SCRUM REVEALED: THE ONLY BOOK YOU CAN SIMPLY LEARN SCRUM!”: http://www.scrum- institute.org/Scrum_Books_International_Scrum_Institute.php • “Scrum: a Breathtakingly Brief and Agile Introduction” by Chris Sims & Hillary Louise Johnson authors of The Elements of Scrum • “What does the agile manifesto mean?” https://www.scrumalliance.org/community/articles/2013/2013- april/what-does-the-agile-manifesto-mean
- 37. References • “Scrum Values” https://www.scrumalliance.org/why-scrum/core-scrum- values-roles • “Responding to Change or Looking Forward to Good Change” https://www.scrumalliance.org/community/articles/2014/septe mber/responding-to-change-or-looking-forward-to-good-ch • “AGILE QUOTES” http://agilequotes.com/quotes
- 38. Thank you Angeliki Plati
Editor's Notes
- #3: Scrum is a lightweight agile project management framework mainly used for software development. It describes an iterative and incremental approach for project work.
- #4: The Scrum Framework implements the cornerstones defined by the agile manifesto: Individuals and interactions over processes and tools Working software over comprehensive documentation
- #5: Customer collaboration over contract negotiation Responding to change over following a plan
- #7: A prioritized Backlog containing the end user requirements Scrum Events: Sprint Planning Meeting, Daily Scrum Meeting, Sprint Review Meeting, Sprint Retrospective Meeting
- #9: Rules & Norms time and location of the Daily Scrum Meeting the Definition Of Done (DoD) used to decide if work is finished or not coding guidelines tools to use Empowerment & Self organization what it will commit to deliver at the end of the sprint how the expected results have to be broken down into tasks who will perform the task and in which order they are performed
- #11: Empowerment & Self organization:The Scrum Team has to be empowered to define what it will commit to deliver at the end of the sprint how the expected results have to be broken down into tasks who will perform the task and in which order they are performed
- #13: acts as a change agent and adapts processes to maximize productivity of the team coaches the Scrum Team removes impediments for the Scrum Team
- #18: Strict sequential chain of the different project phases Phase completed before starting the next one Going back is in most cases difficult, costly, frustrating to the team and time consuming The project timeline is planned at the start. A releasable product is delivered only at the end of the project timeline. If one phase is delayed all other phases are also delayed.
- #19: Strict sequential chain of the different project phases Phase completed before starting the next one Going back is in most cases difficult, costly, frustrating to the team and time consuming The project timeline is planned at the start. A releasable product is delivered only at the end of the project timeline. If one phase is delayed all other phases are also delayed.
- #20: Users try to anticipate all possibilities beforehand. Requirement definition in such an early phase is often very difficult. Many requirements change (or should change) throughout the project.
- #21: Users estimate each phase separately. But most of these phases are normally not separate. They are working together and in parallel.
- #22: The Waterfall approach can work forsmall and simple projects. For bigger and more complex projects it can be highly risky, often more costly and generally less efficient than Scrum Project Management Framework.
- #23: The Scrum framework changes the classical triangle of project management. The compromise is no longer between Time, Budget and Quality. It is now becoming the triangle of Budget, Time and Functionality.
- #24: The Definition Of Done (DoD) specifies the factors that define when a feature is complete (in terms of quality, required testing, documentation etc.) No incomplete or untested feature will be released to the customer.
- #25: The functionality to implement will be defined throughout the course of the project and implemented incrementally. Remain flexible, change in a controlled manner without the additional costs/risks of jeopardizing large chunks of previous work.
- #26: At the end of each increment (Sprint) a result is available that can be shown and discussed with the customer to get and incorporate feedback as soon as possible.
- #29: In Scrum, changes and optimizations of product, requirements and processes are an integral part of the whole engineering cycle.