Mastering Scrum

A presentation I first gave in 2010. I used it as Agile coach to introduce teams to scrum.

Transcript

1. Mastering Agile
   GEERT.THEYS@ALTAGE-CONSULT.COM
   VERSION Beta http://www.flickr.com/photos/fengschwing/3278956517/
2. Agenda
3. Agenda The ancient ways Different Agile Styles Scrum Style Results How to test your Scrum
4. To improve our kungfu we need to know what went wrong. Po: I know you're trying to be all mystical and Kung Fu- ey, but could you tell me where we're going?
5. Traditional Software Development
6. Traditional Software Development Plan everything Stick to the Plan Follow the process
7. Building the wrong thing We assume: The customer knows what he wants The Developers know how to build it Nothing will change during execution
8. Most IT projects fail What is definition of Succes? Standish Group used : on-time, on-budget and with most of the expected features This is not succes but a failure in estimation. Project success is more about whether the software delivers value that's greater than the cost of the resources put into it - but that's very tricky to measure. (Martin Fowler) 23% 49% 28% Succes Challenged fail
9. What are the different Agile styles?
10. Scrum Daily Scrum Sprint Backlog Burndown Chart Sprint Planning Meeting Sprint Demo Scrum Master Product Owner Product Backlog Team XP Collective Ownership Whole team Coding Standard Customer Tests Pair Programming Refactoring Planning Game Continous Integration Simple Design Sustainable Pace Metaphor Small Releases Scrum & XP http://blog.crisp.se/henrikkniberg/
11. Agile Assumes http://www.flickr.com/photos/b2tse/3960471608/sizes/o/ We assume: The customer discovers what he wants The developers discovers how to build it Things change on the way
12. Let’s focus on SCRUM
13. Agile Mind Tries to be predictable Fixes Time, Price and scope on projects Values Methodology and its processes more than the people Measures succes of project by their conformance to plan Resist Change in software requirements and development process Sees the system specification as the generated documentation Accepts that predicatbility in business software is impossible Time and price are fixed but not the scope Values people more than the process, hence it accepts a process instead of imposing Success of the project is measured by the value it gives to the customer Welcomes Change in software requirements and development process Sees the system specification as the development code
14. Transparancy Inspection Adaption Three Legs
    http://www.flickr.com/photos/chrisafer/2427399932/sizes/l/
15. Scrum Roles http://www.flickr.com/photos/clintjcl/305229885/
16. Product Owner
17. Product Owner Must have authority to manage the product log The product owner is not a comittee
18. The Team
19. The Team Self Organised - Cross functional - max 9 members
20. Scrum Master
21. Scrum Master Teaches Scrum by coaching an leading it Removes all impediments
22. Chicken and Pig
23. Chicken and Pig Product owner Scrum Master The Team Users Managers Others
24. Scrum Process
25. Product Backlog First person Shooter Multiplayer Singe Player Tutorial Missions Storyline Online Cooperative Gameplay Player Control AI Death Match Split Screen
26. Product Backlog
27. Product Backlog Owned by the product owner Never complete Best-understood requirements Evolves Sorted in order of priority
28. Sprints
29. Sprint Planning Defining the sprint length and goal What are we going to build How are we going to build it When will it be “done”
30. Sprint Backlog Owned by the team Team allocates tasks No additions from outside the team
31. Taskboard
32. Sprint Burndown
33. Daily Standup http://www.flickr.com/photos/jonnimont/3763340830/
34. Daily Standup Answer: What did I do and what am I going to do? Comitment to the team not the Scrum Master Take responsibility on your own work! MAX : 15 and don’t sit down! http://www.flickr.com/photos/jonnimont/3763340830/
35. Sprint Review Everybody is welcome No mockups - Show working code Get feedback on your product Accept or Reject features
36. Done? Avoid 90% problem General concensus needed what is done... Done should be clear to everyone!
37. Sprint Retrospective
38. Sprint Retrospective Good Bad Do more Do Less Evolution
39. Results
40. Incremental Change Deliver feature by feature - Highest value first Quick Results - Quick Fail Shorter time to market
41. Flexibility Respond easily to change No danger of missing a deadline
42. Higher Quality Continous testing Continous integration Inspect - Adapt
43. http://www.flickr.com/photos/mcanevet/289262598/ More fun - happy teams http://www.flickr.com/photos/32034590@N04/4657598751/
44. Grading your mastery http://www.flickr.com/photos/mcanevet/289262598/
45. Shu-Ha-Ri stages of learning Shu = Follow the rules Ha = Change the rules Ri = Never mind the rules
46. Scrum.org
47. ScrumAlliance Graduate Proffesional Guide Certified Product Owner Certified Scrum Master Certified Scrum Developer Certified Scrum Proffesional Certified Scrum Trainer Certified Scrum Coach
48. Questions?
49. slideshare.net/geerttheys twitter/toadi be.linkedin.com/in/gtheys geert.theys@altage-consult.com geerttheys geerttheys.com
50. This presentation was inspired by the works of many people, and I cannot possibly list them all. Though I did my very best to attribute all authors of texts and images, and to recognize any copyrights, if you think that anything in this prevention should be changed added or removed, please contact me at geert.theys@altage-consult.com http://creativecommons.org/licenses/by-nd/3.0/