Portfolio Kanban - Sandy Mamoli

512 views

Published on

Published in: News & Politics, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
512
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Portfolio Kanban - Sandy Mamoli

  1. 1. Portfolio Kanban Sandy Mamoli @smamol sandy@nomad8.com www.nomad8.com Wednesday, 25 September 13
  2. 2. Wednesday, 25 September 13
  3. 3. We’ll talk about Problems Causes Solutions Portfolio Kanban - how we implemented it How we prioritised Benefits & Challenges Wednesday, 25 September 13
  4. 4. Problems Wednesday, 25 September 13
  5. 5. What’s going on? Wednesday, 25 September 13
  6. 6. I asked and found ... ‣ Projects take a really long time to get finished ‣ We don’t know where our projects are at ‣ We can’t trust the estimates Wednesday, 25 September 13
  7. 7. Project stickies Wednesday, 25 September 13
  8. 8. We realised... ‣ Heaps of projects are in progress ‣ We have no idea of what our capacity is Wednesday, 25 September 13
  9. 9. Causes Wednesday, 25 September 13
  10. 10. Lack of visualisation Wednesday, 25 September 13
  11. 11. Organisational stop-go Wednesday, 25 September 13
  12. 12. Solution Wednesday, 25 September 13
  13. 13. Moving targets - fix them! Wednesday, 25 September 13
  14. 14. Stable teams Team 1 Wednesday, 25 September 13 Team 2 Team 3
  15. 15. Stable priorities Wednesday, 25 September 13
  16. 16. Portfolio Kanban Wednesday, 25 September 13
  17. 17. Portfolio Kanban 1. Visualise your workflow 2. Limit work in progress 3. Manage flow 4. Make exit policies explicit 5. Implement feedback loops 6. Improve collaboratively Wednesday, 25 September 13
  18. 18. 1. Visualise your workflow Wednesday, 25 September 13
  19. 19. Step 1: Visualise Wednesday, 25 September 13
  20. 20. 2. Limit your WIP Wednesday, 25 September 13
  21. 21. Step 2: Limit WIP Wednesday, 25 September 13
  22. 22. Block stuff in progress Wednesday, 25 September 13
  23. 23. Wednesday, 25 September 13
  24. 24. Blocked means don’t work on it! Really Wednesday, 25 September 13
  25. 25. Track progress Wednesday, 25 September 13
  26. 26. 3. Manage flow Wednesday, 25 September 13
  27. 27. Step 3: Manage flow Wednesday, 25 September 13
  28. 28. 4. Exit policies Wednesday, 25 September 13
  29. 29. Make exit policies explicit Wednesday, 25 September 13
  30. 30. Make your rules explicit Wednesday, 25 September 13
  31. 31. 5. Feedback loops Wednesday, 25 September 13
  32. 32. You get what you measure Wednesday, 25 September 13
  33. 33. What matters to Trade Me? ‣ Get stuff out fast ‣ Have high quality ‣ Have happy clients (business people/ end users) ‣ Have happy employees ‣ Build the right thing Wednesday, 25 September 13
  34. 34. Get stuff out fast - cycle time Wednesday, 25 September 13
  35. 35. Get stuff out fast - stories shipped Wednesday, 25 September 13
  36. 36. Happiness surveys Wednesday, 25 September 13
  37. 37. Example: business survey On a scale of 1 to 5 do you feel... ... you have confidence that the problem you have will be solved, it will be solved well and it will be solved quickly? ... your projects are hitting the promised dates? ... the amount of time to get a project delivered is right and reasonable? ... project progress is highly visible and you always know what will happen next? ... you know how you can help and also influence successful delivery yourself? Wednesday, 25 September 13
  38. 38. Example: Employee survey Wednesday, 25 September 13
  39. 39. 6. Improve collaboratively Wednesday, 25 September 13
  40. 40. Step 6: Improve collaboratively Wednesday, 25 September 13
  41. 41. How we prioritised Wednesday, 25 September 13
  42. 42. Prioritisation session Wednesday, 25 September 13
  43. 43. What about started projects? Wednesday, 25 September 13
  44. 44. Democratic dot vote Wednesday, 25 September 13
  45. 45. Update the board Wednesday, 25 September 13
  46. 46. Prioritisation session outcomes ‣ A ranked list of 14 projects ‣ Shared understanding of all projects ‣ An agreement to do this every 3 months ‣ Acceptance that things will change Wednesday, 25 September 13
  47. 47. Where are we now? Wednesday, 25 September 13
  48. 48. Fewer projects in progress Wednesday, 25 September 13
  49. 49. Now ‣ Partially there ‣ Collect more data ‣ Have measures to know if we’re moving in the right direction Wednesday, 25 September 13
  50. 50. Benefits & challenges Wednesday, 25 September 13
  51. 51. Work on the right stuff Wednesday, 25 September 13
  52. 52. Shiny new things Wednesday, 25 September 13
  53. 53. Getting stuff out Wednesday, 25 September 13
  54. 54. Getting stuff out Wednesday, 25 September 13
  55. 55. Getting stuff out m co E Wednesday, 25 September 13 y ne Mo GE AT MC ats Bo
  56. 56. Getting stuff out m co E Wednesday, 25 September 13 y ne Mo GE AT MC ats Bo
  57. 57. Discussion point Wednesday, 25 September 13
  58. 58. Where are the bottlenecks? Wednesday, 25 September 13
  59. 59. Missing link to squads Wednesday, 25 September 13
  60. 60. Intangible goodness “I think tech get more empathy now that it’s all visible.” David Mole, Head of Projects Wednesday, 25 September 13
  61. 61. Challenge: Ownership Wednesday, 25 September 13
  62. 62. Challenge: keep changing it! Wednesday, 25 September 13
  63. 63. Challenge: Location Wednesday, 25 September 13
  64. 64. Portfolio Kanban 1. Visualise your workflow 2. Limit work in progress 3. Manage flow 4. Make exit policies explicit 5. Implement feedback loops 6. Improve collaboratively Wednesday, 25 September 13
  65. 65. If you’re interested in seeing this presentation live feel free to get in touch. I live in Wellington, New Zealand. @smamol sandy@nomad8.com www.nomad8.com Wednesday, 25 September 13

×