#IWDev11 - A Sprint for Scrum

Transcript

1. A Sprint for Scrum in 30 minutes #IWDev1011 Wednesday, 8 May 13
2. Hello World • Garth Oatley - @garth • Development Manager at SAS Institute • Working remotely past 13 years • Waterfall, RUP, SOP, Agile/Scrum • Java, Ruby, Visual Basic • Agile many shapes and forms Wednesday, 8 May 13
3. Why Scrum? Wednesday, 8 May 13
4. Software Engineering Wednesday, 8 May 13
5. Requirements Design Implementation Verification Maintenance Wednesday, 8 May 13
6. Requirements Known vs. Lack of Flexibility Wednesday, 8 May 13
7. Wednesday, 8 May 13
8. What is Scrum? • Lightweight process framework for Agile development • Change-friendly and flexible • Fixed deadlines - sprints • Progress is highly visible - Scrum meetings • Ship a working product each sprint Wednesday, 8 May 13
9. Roles Stories Product / Release Backlog Planning Poker Velocity Sprint / Iteration Done Daily Scrum Meetings Acceptance Documentation Wednesday, 8 May 13
10. Roles • Product Owner • ScrumMaster / Iteration Manager • Team Members • Typical Scrum team size 5 - 9 people Wednesday, 8 May 13
11. Product Owner • Represents the customer • Writes Stories • Owns the product backlog, prioritises the backlog • Creates acceptance criteria • Answers questions • Decides what goes in a sprint Wednesday, 8 May 13
12. ScrumMaster • Coach and Mentor • High Performing and Self Organising Team • Removes blocks, protects the team • Not the boss • Helps everyone Wednesday, 8 May 13
13. Team Member • Developer, Tester, UI/UX, DBA, Architect • Full time on the sprint • Everyone Estimates • Responsible for updating task board! Wednesday, 8 May 13
14. Stories • Feature of the system similar to a use case • Small enough to be written on a card • Form part of the product backlog • Communication • Confirmation (Story Acceptance) Wednesday, 8 May 13
15. Story Format • As an user I would like to do something so that I can get value. • As an account holder, I would like to withdraw cash from an ATM so that I can get money when the bank is closed. Wednesday, 8 May 13
16. INVEST • Independent • Negotiable • Valuable • Estimable • Small • Testable Wednesday, 8 May 13
17. Product Backlog • Collection of all the stories • Continually prioritised and worked on • Story ‘massaging’ • Used as a basis for planning the sprint • Plan ahead Wednesday, 8 May 13
18. Planning Poker • Size Stories • Complexity, not time based • Card score system 0, 1, 2, 3, 5, 8, 13 • Story is presented • Team members vote • Promotes story conversation Wednesday, 8 May 13
19. PlanningPoker.com Wednesday, 8 May 13
20. Velocity • Planning iterations • Team Performance • Settles down through sprint cycles • Stretch stories :( Wednesday, 8 May 13
21. Sprint or Iteration • Lasts up to 4 weeks • Planning meeting lasting a day • Stories move to sprint backlog • Product Manager decided what goes in • Lots of sprints Wednesday, 8 May 13
22. Sprints look like this Backlog Stories Sprints Finished Product Wednesday, 8 May 13
23. Sprints cont. • Once committed no changes • Team members create tasks • Product Manager writes PMATs • Testers write TAPs and detailed tests • Developers start designing/coding/unit tests Wednesday, 8 May 13
24. Sprint Board Wednesday, 8 May 13
25. Burn down charts Wednesday, 8 May 13
26. Define ‘Done’ Wednesday, 8 May 13
27. Daily Scrum Meetings • Everyone invited • Usually at the start of the working day • Only Scrum team members can speak • Yesterday, Today, Needs? • Lasts 15 minutes maximum • Stand up, sit down, choose someone? • Remote? • Not a platform for design discussions Wednesday, 8 May 13
28. Acceptance • Showcase • Customer Presentation • Questions from stakeholders • Don’t surface bugs! Wednesday, 8 May 13
29. Documentation “If you have working software, automated tests, an up-to-date backlog, and an actively participating product owner, you have everything you need.” Wednesday, 8 May 13
30. Phew, Questions? Wednesday, 8 May 13