SCRUM: don't panic
- 1. SCRUM: donât panic Shoot the breeze to find out more about it Nico Spadoni
- 2. Scrum: definition By the official Scrum Guide ââ A framework within which people can address Complex Adaptive problems, while productively and creatively delivering products of the highest possible value. Ken Schwaber / Jeff Sutherland (1995)
- 3. At the beginning was LEAN In pursuit of excellence To put customer needs at the heart To discover and remove waste Continuous improvement
- 4. Then AGILE came From software industry difficulties has risen the Manifesto (2001) OVER INDIVIDUALS AND INTERACTIONS WORKING SOFTWARE CUSTOMER COLLABORATION RESPONDING TO CHANGE PROCESSES AND TOOLS COMPREHENSIVE DOCUMENTATION CONTRACT NEGOTIATION FOLLOWING A PLAN
- 5. Traditional development vs Agile Focus on Process REQUIREMENTS DESIGN IMPLEMENTATION TEST REQUIREMENTS DESIGN IMPLEMENTATION TEST BIG BANG ITERATIVEANDINCREMENTALDELIVERY
- 6. Traditional development vs Agile Focus on Complexity Disorder Complicated SimpleChaotic Complex sense ANALYZE respond PROBE sense respond sense CATEGORIZE respond ACT sense respond Unknown unknows known unknows Known knowsUnknowable unknows AGILE Works better in a COMPLEX DOMAIN Cynefin Framework - Scholar David J. Snowden (1999)
- 7. Traditional development vs Agile Focus on Value Value at risk (MVP) Tempo Value(ROI) Cumulative costs Produced Value Value at risk (MVP) Tempo Value(ROI) Cumulative costs Produced Value OpportunitĂ } Learning Traditional Agile
- 8. Scrum framework Process, artifacts and events SPRINT 1-4 weeks Daily Meeting 15 minutes Inception Release Sprint Review Retrospective Sprint Planning Product Backlog Refinement SCRUM Inception and Product Backlog Refinement Are agile practices which arenât provided by scrum guide. Though they are useful for success of a project. Especially the Inception because itâs a critical activity for product envisioning and people alignment. Vision Product Backlog Sprint Backlog Stories TaskNeeds
- 9. Scrum framework Team, Actors and Roles Scum MasterProduct Owner Development Team Stakeholder He is the sole person managing the Product Backlog and ordering it to maximize value. They make sure the Backlog is visible and understood. He is a servant-leader who ensures that everyone unerstand and act the activities in the right way. He also ensure the continuous improvement of the team. It consists of everyone directly building the product. They are self-organizing and decide how to turn backlog items into working solutions. The Development Team is responsible for the quality of the outcome. They are the ones who have desires, wants, and needs and are the reason the Team is developing the software in the first place. Also someone of them should pays us for it.
- 10. Some side note To reassure ourself remember that... ââ Scrum, among all agile frameworks, is the most common because it is very easy to understand. However it is pretty difficult to act. So, what we need for? Never stop to learn A coach always available Really want to experience and improve
- 11. And now... ...thanks a lot! ď Nico Spadoni Lean & Agile Transition Agent IT Project Manager Risk Management Modeler Blogger & Story writer Email me: spadoni.nico@gmail.com Nico Spadoni Lean & Agile Transition Agent IT Project Manager Risk Management Modeler Blogger & Story writer Contact me: spadoni.nico@gmail.com