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.

Scrum and kanban

  • Sé el primero en comentar

Scrum and kanban

  1. 1. Scrum & Kanban Like Chocolate and Peanut Butter<br />
  2. 2. Synchronizing Multiple Scrum Teams<br />
  3. 3. Overview<br />Why bother?<br />Bird’s eye view of Scrum<br />Problems with multi-Scrum-team coordination<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  4. 4. Who is “The Customer?”<br />Market /Customers<br />Business Unit<br />Software Development<br />
  5. 5. Who is “The Customer?”<br />Market /Customers<br />Your offering<br />
  6. 6. Return on Investment<br />Return<br />Value<br />ROI =<br />Investment<br />Software<br />
  7. 7. The Time Value of Money<br />A<br />B<br />D<br />C<br />A<br />B<br />C<br />D<br />Cost<br />Value<br />
  8. 8. The Time Value of Money<br />Learning also has value<br />Value<br />A<br />B<br />D<br />C<br />Time<br />Investedhere<br />
  9. 9. Providing Value as Fast as Possible<br />Team in Kiev<br />$<br />Customers in Kiev<br />
  10. 10. Software Development Nirvana<br />Continuous flow of Working Software<br />Frequent communication<br />Problems found and solved right away<br />Going as fast as possible<br />Delivering as small an increment as possible<br />Providing as much value as possible<br />What do we all do that is like this today?<br />
  11. 11. The Lean Startup Model<br />
  12. 12. Why bother?<br />Bird’s eye view of Scrum<br />Problems with multi-Scrum-team coordination<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  13. 13. Bird’s Eye View of Scrum<br />Customers<br />
  14. 14. Why bother?<br />Bird’s eye view of Scrum<br />Problems with Scrum<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  15. 15. Product Management<br />Customers<br />
  16. 16. Int<br />Product Management<br />Customers<br />
  17. 17. Int<br />Product Management<br />Customers<br />
  18. 18. Problems With Multi-Team Synchronization<br />Can’t say you are “shippable” if work of all teams is not integrated<br />Hardening/stabilization iterations<br />“QA iterations” offset from “Dev iterations”<br />Integration iterations<br />Visibility into problems is clearest at end of iteration<br />Resolution may not come until for multiple iterations<br />Elisabeth says:<br />“No Stabilization sprints!!”<br />
  19. 19. Why bother?<br />Bird’s eye view of Scrum<br />Problems with multi-Scrum-team coordination<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  20. 20. Kanban<br />todo<br />wip<br />coded<br />tested<br />done<br />backlog<br />5<br />3226 – User wants to undo a depot operation<br />3146 – User wants to replicate adepot<br />8<br />3216 – User wants to remove a depot<br />3247 – User wants to combine depots<br />5<br />4246 – User wantsto unhide a depot<br />2<br />3241 – User wantsto hide a depot<br />2<br />3249 – User wants to copy a depot<br />3<br />5<br />1<br />3246 – User wantsa list of depots<br />3<br />3244 – User wants to remove areplica<br />8<br />3256 – User wants to rename a depot<br />1<br />3236 – User wants to split a depot<br />1) Visual system of managing work<br />2) Limited work in progress<br />3) Work is pulled through the system<br />
  21. 21. Kanban in Action<br />Int<br />Customers<br />
  22. 22. <ul><li>Whole product touch point after every story
  23. 23. Working software after ever story is complete</li></ul>Int<br />Product Management<br />Customers<br />Use Done Stories As Sync Points<br />
  24. 24. Why bother?<br />Bird’s eye view of Scrum<br />Problems with multi-Scrum-team coordination<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  25. 25. What’s in a User Story<br />5<br />3226 – User wantsto undo a depot operation<br />
  26. 26. Features of All Shapes and Sizes<br />S<br />D<br />Specify<br />Design<br />Code<br />Integrate<br />Document<br />Write tests<br />Test<br />C<br />I<br />W<br />T<br />D<br />Gradient or rhythm?<br />
  27. 27. One Piece Flow<br />Do you remember me?<br />5<br />3226 – User wants to undo a depot operation<br />I<br />W<br />T<br />D<br />S<br />C<br />Within an Iteration<br />D<br />
  28. 28. One Piece Flow<br />I<br />W<br />T<br />W<br />T<br />D<br />I<br />W<br />T<br />W<br />T<br />I<br />W<br />T<br />W<br />T<br />I<br />D<br />S<br />C<br />D<br />S<br />C<br />I<br />D<br />S<br />C<br />D<br />D<br />S<br />C<br />I<br />D<br />S<br />C<br />D<br />S<br />C<br />I<br />D<br />S<br />C<br />I<br />D<br />S<br />C<br />D<br />S<br />C<br />I<br />D<br />S<br />C<br />I<br />D<br />W<br />T<br />D<br />D<br />D<br />D<br />D<br />Within an Iteration<br />W<br />T<br />D<br />W<br />T<br />D<br />W<br />T<br />
  29. 29. Activity vs Achievement<br />
  30. 30. One Piece Flow<br />W<br />D<br />S<br />C<br />I<br />T<br />D<br />W<br />D<br />S<br />C<br />I<br />T<br />D<br />Within an Iteration<br />
  31. 31. One Piece Flow<br />W<br />W<br />D<br />S<br />C<br />I<br />T<br />D<br />S<br />C<br />I<br />T<br />D<br />D<br />W<br />W<br />W<br />W<br />W<br />W<br />W<br />D<br />S<br />C<br />I<br />T<br />D<br />S<br />C<br />I<br />T<br />D<br />S<br />C<br />I<br />T<br />D<br />S<br />C<br />I<br />T<br />D<br />S<br />C<br />I<br />T<br />D<br />S<br />C<br />I<br />T<br />D<br />S<br />C<br />I<br />T<br />D<br />D<br />D<br />D<br />D<br />D<br />D<br />W<br />D<br />S<br />C<br />I<br />T<br />D<br />Within an Iteration<br />
  32. 32. One Piece Flow<br />
  33. 33. Why bother?<br />Bird’s eye view of Scrum<br />Problems with multi-Scrum-team coordination<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  34. 34. Taskboard/Limited WIP/Pull<br />todo<br />wip<br />coded<br />tested<br />done<br />5<br />3226 – User wants to undo a depot operation<br />3146 – User wants to replicate adepot<br />8<br />3216 – User wants to remove a depot<br />3246 – User wantsto create a depot<br />5<br />3246 – User wants to combine depots<br />5<br />3247 – User wants to combine depots<br />5<br />4246 – User wantsto unhide a depot<br />2<br />3241 – User wantsto hide a depot<br />2<br />3249 – User wants to copy a depot<br />3<br />5<br />1<br />3246 – User wantsa list of depots<br />3<br />3256 – User wants to rename a depot<br />1<br />3236 – User wants to split a depot<br />
  35. 35. wip<br />coded<br />tested<br />done<br />todo<br />3241 – User wants to take a survey<br />3244 – Surveyor wants to remove<br />a question<br />1<br />3<br />3246 – Surveyor wants to create a true/false question<br />2<br />3247 – Surveyor wants to add a freeform question<br />3<br />3242 – Surveyor wants to browsesurvey results<br />5<br />3<br />3245 – Surveyor wants to create a multiple choice question<br />3<br />3243 – Surveyor wants to add anew question<br />
  36. 36. wip<br />coded<br />tested<br />done<br />todo<br />3241 – User wants to take a survey<br />3244 – Surveyor wants to remove<br />a question<br />1<br />3<br />3246 – Surveyor wants to create a true/false question<br />2<br />3242 – Surveyor wants to browsesurvey results<br />5<br />3<br />3247 – Surveyor wants to add a freeform question<br />3<br />3245 – Surveyor wants to create a multiple choice question<br />3<br />3243 – Surveyor wants to add anew question<br />
  37. 37. wip<br />coded<br />tested<br />done<br />todo<br />3241 – User wants to take a survey<br />3244 – Surveyor wants to remove<br />a question<br />1<br />3<br />3246 – Surveyor wants to create a true/false question<br />2<br />3242 – Surveyor wants to browsesurvey results<br />5<br />3<br />3247 – Surveyor wants to add a freeform question<br />3<br />3245 – Surveyor wants to create a multiple choice question<br />3<br />3243 – Surveyor wants to add anew question<br />
  38. 38. wip<br />coded<br />tested<br />done<br />todo<br />3241 – User wants to take a survey<br />3244 – Surveyor wants to remove<br />a question<br />1<br />3<br />3246 – Surveyor wants to create a true/false question<br />2<br />3247 – Surveyor wants to add a freeform question<br />3<br />3242 – Surveyor wants to browsesurvey results<br />5<br />3<br />3245 – Surveyor wants to create a multiple choice question<br />3<br />3243 – Surveyor wants to add anew question<br />
  39. 39. wip<br />coded<br />tested<br />done<br />todo<br />3241 – User wants to take a survey<br />3244 – Surveyor wants to remove<br />a question<br />1<br />3<br />3246 – Surveyor wants to create a true/false question<br />2<br />3247 – Surveyor wants to add a freeform question<br />3<br />3242 – Surveyor wants to browsesurvey results<br />5<br />3<br />3245 – Surveyor wants to create a multiple choice question<br />3<br />3243 – Surveyor wants to add anew question<br />
  40. 40. wip<br />coded<br />tested<br />done<br />todo<br />3241 – User wants to take a survey<br />3244 – Surveyor wants to remove<br />a question<br />1<br />3<br />3246 – Surveyor wants to create a true/false question<br />2<br />3247 – Surveyor wants to add a freeform question<br />3<br />3242 – Surveyor wants to browsesurvey results<br />5<br />3<br />3245 – Surveyor wants to create a multiple choice question<br />3<br />3243 – Surveyor wants to add anew question<br />
  41. 41. Why bother?<br />Bird’s eye view of Scrum<br />Problems with multi-Scrum-team coordination<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  42. 42. Scrum Activities Linked to Iterations<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />
  43. 43. Decoupling<br />4 week iterations<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />3<br />4<br />5<br />6<br />Iterations<br />
  44. 44. Decoupling<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />3<br />4<br />5<br />6<br />Iterations<br />
  45. 45. Stop!!<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />Decoupling<br />3<br />4<br />5<br />6<br />Iterations<br />
  46. 46. Decoupling<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />3<br />4<br />5<br />6<br />Iterations<br />
  47. 47. Decoupling<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />3<br />4<br />5<br />6<br />Iterations<br />
  48. 48. Decoupling<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />3<br />4<br />5<br />6<br />Iterations<br />
  49. 49. Decoupling<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />3<br />4<br />5<br />6<br />Iterations<br />
  50. 50. Decoupling<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />3<br />4<br />5<br />6<br />Iterations<br />
  51. 51. Trailing 4 Week Burnup<br />4 WeekBurnup<br />20<br />15<br />Story Points<br />10<br />5<br />0<br />10/4<br />10/2<br />10/9<br />10/11<br />10/11<br />10/15<br />10/17<br />10/19<br />10/23<br />10/25<br />Trailing 4 weeks<br />
  52. 52. Calculating Velocity<br />Per iteration<br />Iteration Velocity<br />40<br />30<br />Story Points<br />20<br />10<br />0<br />1<br />3<br />5<br />7<br />9<br />11<br />13<br />15<br />17<br />19<br />Iterations<br />Trailing 4 weeks<br />4 Week Velocity<br />40<br />30<br />Story Points<br />20<br />10<br />0<br />1<br />3<br />5<br />7<br />9<br />11<br />13<br />15<br />17<br />19<br />Iterations<br />
  53. 53. Decoupling Commitment<br />Or else what?<br />New Scrum Guide replaces commitment with forecast<br />Scrum Commitment<br />Team will get all committed stories to ‘done’<br />Everybody else will leave the team alone<br />Trust is the flip side of commitment<br />Trust is a two way street and requires flexibility<br />Handling the unexpected requires negotiation<br />
  54. 54. Scrum Without Iterations<br />Done<br />Retrospective<br />Iteration Review<br />Backlog grooming<br />Story estimation<br />Choose stories<br />Trailing 4 week burnup<br />Trailing 4 week velocity<br />Trust & negotiation<br />
  55. 55. Why bother?<br />Bird’s eye view of Scrum<br />Problems with multi-Scrum-team coordination<br />Bird’s eye view of Kanban<br />One-piece-flow (aka small batch size)<br />Applying Kanban basics to Scrum<br />Moving away from iterations<br />Synchronized Scrum Teams<br />
  56. 56. Int<br />Product Management<br />Customers<br />Multi-Stage Continuous Integration<br />
  57. 57. Int<br />Int<br />Int<br />Product Management<br />Customers<br />Multi-Stage Continuous Integration<br />
  58. 58. Product Management<br />Customers<br />Individuals and Interactions<br />
  59. 59. Product Management<br />Customers<br />Agile Project Management<br />
  60. 60. Web<br />Mobile<br />Int<br />DB<br />Int<br />Int<br />Server<br />Product Management<br />Customers<br />SCM (Version Control)<br />
  61. 61. Web<br />Mobile<br />Int<br />DB<br />Continuous Integration<br />Int<br />Int<br />Server<br />Product Management<br />Customers<br />
  62. 62. <ul><li>Whole product touch point after every story
  63. 63. Working software after ever story is complete
  64. 64. Scales up</li></ul>Int<br />Int<br />Int<br />Product Management<br />Customers<br />Continuous Delivery<br />$<br />
  65. 65. You want what!?<br />Why can’t we finish this?<br />Why won’t this integrate?<br />Int<br />Why is this unshippable?<br />What does that mean?<br />Int<br />Int<br />Product Management<br />Customers<br />Continuous Touch Points<br />
  66. 66. “Pure” Scrum<br />Roles<br />Self organizing team<br />Team Member<br />Product Owner<br />Scrum Master<br />Meetings<br />Sprint planning (Iteration planning)<br />Daily standup<br />Sprint review (Iteration review)<br />Retrospective<br />Artifacts<br />Product backlog<br />Sprint backlog<br />Burndown<br />Cycles<br />Daily<br />Sprints<br />Releases<br />
  67. 67. An Example Mix<br />Roles<br />Self organizing team<br />Team Member<br />Product Owner<br />Scrum Master<br />Meetings<br />Weekly story estimation<br />Daily standup<br />Monthly story review<br />Weekly retrospective<br />Artifacts<br />Product backlog<br />Trailing 4 week burnup<br />Cycles<br />Daily<br />Releases<br />Additional ingredients<br />Kanban board (Todo, WIP, Coded, Tested, Done)<br />One piece flow<br />WIP limits<br />Multi-stage Continuous Integration<br />Removed<br />Sprints<br />Sprint backlog<br />
  68. 68. Resources/Q&A<br />Do It Yourself Agile – Damon Poolehttp://damonpoole.blogspot.com<br />Don Reinertsen’s Books<br />Lean Software Development, Mary Poppendieck and Tom Poppendieck<br />Scrumban - Essays on Kanban Systems for Lean Software Development, Corey Ladas<br />Kanban and Scrum – Making the Most of Both, HenrikKniberg & MattiasSkarin<br />Agile Software Development with Scrum, Ken Schwaber & Mike Beedle<br />

×