Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Agile intro module 3

641 visualizaciones

Publicado el

Fourth module of agile/scrum course. Planning, user stories and velocity

  • Sé el primero en comentar

Agile intro module 3

  1. 1. Agile Intro Module 3Estimating & Planning
  2. 2. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan2
  3. 3. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan2
  4. 4. User Story As a trainee I want to know how to do planning in Agile projects Because without planning we don’t know what to do, and how far we are3
  5. 5. Agile versus Plan-driven • Agile opposite to plan-driven? • No BPUF ! But, a lot of planning.4
  6. 6. Six levels of planning strategy portfolio product release iteration day5
  7. 7. Cone of Uncertainty coarse, inaccurate estimate precise estimate6
  8. 8. Three levels of planning At 31/10 our site should Release go live, and we can start selling! As a user I want to pay Iteration with Visa card 8 I don’t get that #$%@! connection Daily to VISA working!7
  9. 9. Release planning • Release • >> Iteration • typically 3-6 months • date-driven or user story-driven8
  10. 10. User story backlog Sprint 1 Sprint 2 Sprint 3 As a user ... As a user ... As a user ... 8 1 8 As a user ... As a user ... As a user ... 3 8 3 As a user ... As a user ... As a user ... 5 5 8 As a user ...9 5
  11. 11. User story matrix Fully functional As a user ... As a user ... As a user ... 8 1 8Fully featured As a user ... As a user ... As a user ... 1 5 3 As a user ... As a user ... As a user ... 5 5 8 As a user ... 10 5
  12. 12. User story matrix Fully functional As a user ... As a user ... As a user ... 8 1 8Fully featured As a user ... As a user ... As a user ... 1 5 3 As a user ... As a user ... As a user ... 5 5 8 As a user ... 10 5
  13. 13. User story matrix Fully functional As a user ... As a user ... As a user ... 8 1 8Fully featured As a user ... As a user ... As a user ... 1 5 3 As a user ... As a user ... As a user ... 5 5 8 As a user ... 10 5
  14. 14. Release planning iteration length? Release Estimate user velocity? Goal stories prioritise user stories11
  15. 15. Story points • Value for size / complexity, without dimension • Not directly for effort • Relative way of estimating (x = 2y) • Usually with (0), 1, 2, 3, 5, 8, 13, 20, 40, 100 • Start with some stories as baseline • Create a reference set12
  16. 16. Planning Poker • After story explanation, each team member picks a card • 1-2-3 turn cards • discuss High/Low • re-iterate13
  17. 17. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan14
  18. 18. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan14
  19. 19. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan14
  20. 20. User Story As a trainee I want to poker Because that sounds ‘fun’15
  21. 21. Thuiszorg App Lending application of utilities •voor borrowers •voor support16
  22. 22. Thuiszorg App As system admin As system admin I want to register stock Lending application I want register lending data So I can start lending stu of utilities ff So I know where what is •voor borrowers As system admin s •voor support As customer I want to add action product ucts I want to see a product overview So I can m ake unknown prod So I can borrow what I need more popular Als local physician As customer As customer I want to send ‘receipts’ I want to receive invoices I want to order on-line So utilities can be paid by the So I can charge my ave So that I don’t need to le insurance company insurance company homeAs system admin As system admin As customerI want to register payment data I want to get reports I want to register onceSo I can send invoices So I know status So I can save time later16
  23. 23. Case - Home care • Create a release plan for our system • assign a PO • 3-4 sprints • Define sprint goals • Estimate story points in • Give T-shirt sizes for the rest17
  24. 24. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan18
  25. 25. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan18
  26. 26. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan18
  27. 27. User Story As a trainee I want to perform a sprint planning Because just theory is insufficient to start applying this in my company19
  28. 28. Sprint Planning • Product Owner + Team + Experts • Create Sprint Goal • For each User Story in this iteration 1. PO clarifies story, team asks questions 2. Team (w/o PO) creates tasks, (re)estimates size (story or tasks)20
  29. 29. Let’s practice ... • Perform a sprint planning meeting21
  30. 30. Scrum board To Do In Process Done As a user ... As a user ... As a user ... As a user ... As a user ... As a user ... As a user ... As a user ...22
  31. 31. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan23
  32. 32. Sprint Backlog TO-DO DOING DONE Concepts Case Iteration Plan23
  33. 33. Retrospective Start doing Stop doing Continue doing24
  34. 34. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.25
  35. 35. 12 principes Our highest priority is to satisfy the customer Working software is the primary 1 measure of progress. 7 through early and continuous delivery of valuable software. Agile processes promote sustainable Welcome changing requirements, even late in development. The sponsors, developers, 2 and users should be able to maintain a 8 development. Agile processes harness change for the customers competitive advantage. constant pace indefinitely. Continuous attention to technical Deliver working software frequently, from a 3 excellence and good design enhances 9 couple of weeks to a couple of months, with a agility. preference to the shorter timescale. Simplicity--the art of maximizing the Business people and developers must work 4 amount of work not done--is essential. 10 together daily throughout the project. The best architectures, requirements, Build projects around motivated individuals. 5 and designs emerge from self-organizing teams. 11 Give them the environment and support they need, and trust them to get the job done. At regular intervals, the team reflects The most efficient and effective method of on how to become more effective, then 6 tunes and adjusts its behavior 12 conveying information to and within a development team is face-to-face conversation. accordingly.26

×