Scrumban Style

Transcript

1. SCRUMBAN STYLE By Shani Raba (or: scrum and kanban making

   the most of both)

2. Agenda

3. • Split your Organization • Split your work • Split

   Time • Optimize the release • Optimize the Process Scrum

4. Scrum

5. • What is the meaning of Kanban? • What is

   Kanban? – Signaling System – Visual – Limited Supply Kanban

6. • Visualize workflow • Limit Work In Progress (WIP) •

   Measure Lead Time Kanban

7. •So with Kanban you don’t do iterations? Quiz - Q

   #1

8. •With Kanban you don’t estimate? Quiz – Q #2

9. •So, Kanban is better than scrum… Quiz – Q #3

10. More details about the scrum vs. kanban

11. DEEP DIVE Let’s learn about the tools - Time Boxed

    iterations\sprints - Limit WIP - Lead Time - Resist a change - Poker Planning - Velocity

12. Time Boxed iterations • Origin: Scrum • Idea: choose a

    length and stick with it • Why: Establish a Rhythm

13. Free Style: Time Boxed #1 Week 1 Week 2 Week

    3 Week 4 Week 5 Week 6 Week 7 Week 8 Retro Plan Release aka: Fastrekanization

14. Free Style: Time Boxed #2 Week 1 Week 2 Week

    3 Week 4 Week 5 Week 6 Week 7 Week 8 Retro Plan Release On demand

15. Limits WIP • Origin: Kanban • Idea: limit the amount

    of items that can be in- progress • Why: GTD => get the current items done before starting new stuff (eliminating waste)

16. Limit WIP • In Quality Software Management: Systems Thinking, Gerald

    Weinberg proposed a rule of thumb to calculate the waste caused by project switching

17. Lead Time • Origin: Kanban • Idea: Measure the average

    time for an item to reach to DONE • Why: Metric for measuring productivity and improvement

18. Lead Time - Experiments • Experiment #1: – Developers =

    2 – WIP Limit = 1 • Experiment #2: – Developers = 4 – WIP Limit = 8 • Experiment #3: – Developers = 4 – WIP Limit = 4 We’ve got 2 new developers Let’s increase the limit to 8 Let’s limit to 4

19. Resists a Change (and response time) • Origin: Scrum •

    Idea: Scrum resists a change within and iteration • Why: scrum team commits to a sprint to get something DONE

20. Resists a Change (and response time) • How long will

    it take to react to Feature E (new feature)?

21. Estimations and Velocity (Poker Planning) • Origin: Scrum • Idea:

    Poker Planning • Why: In order to measure yourself (scale) • Why: based on the past (velocity) you can predict the future

22. Real Life – Poker Planning

23. Real Life – Poker Planning

24. Velocity • Origin: Scrum • Idea: amount of work a

    TEAM can do from time to time. • Why: based on the past (velocity) you can predict the future

25. Velocity • My team can do 25 SP per sprints,

    how long will it take me to run 100SP?

26. TIPS

27. • Visualize your Flow • Prioritize • Measure your Execution

    (either lead time or Velocity) • Limit your Work • Communicate During a change Tips

28. Tips Ideas\Concept Write Spec (3) GD (1) Coding Done B

    C D A A B C D

29. Zen Wisdom

30. • Don’t be afraid o Experiment and fail • Retro

    It The Only big failure is the failure to learn from a failure Final Words

31. THANKS

32. Appendix Scrum • http://en.wikipedia.org/wiki/Scrum_(software_development) • https://www.scrum.org/portals/0/documents/scrum%20guides/scrum_guide.pdf • http://www.agilehelpline.com/2011/03/10-scrum-rules.html • http://www.agilehelpline.com/2011/03/scrum.html

    • https://www.scrum.org/scrumbut • http://www.scrumalliance.org/why-scrum (scrum in 30 seconds) • First scrum implementation - http://www.scrumalliance.org/resources/35

33. Appendix Kanban • http://agile.dzone.com/articles/kanbans-not-better-scrum-its • http://www.crisp.se/gratis-material-och-guider/kanban

34. Appendix The rest • Multi tasking with humans – •

    http://www.codinghorror.com/blog/2006/09/the-multi-tasking-myth.html • http://www.joelonsoftware.com/articles/fog0000000022.html • http://foreachbiscuit.wordpress.com/2007/12/20/context-switching-on-multiple- projects/

35. Notes • Measure and play the time… • ??