Scrumban Ideacamp - Amsterdam Scrum Gathering 2010

3. © 2010 Proyectalis Gestión de Proyectos S.L. Ángel Medinilla  Telecom Engineer / vocational programmer  13+ years in industry, mainly as a project manager & agile consultant  Entrepreneur, Blogger  Motorbikes, Aikido, gaming, books, travel, music, gourmet cooking, wines, comics…  Certified Scrum Master - PMI Member - Agile Spain Co- Founder angel.medinilla@proyectalis.com http://twitter.com/angel_m http://es.linkedin.com/in/angelm http://slideshare.net/proyectalis http://www.presionblogosferica.com (spanish) http://www.proyectalis.com/en/blog (english, upcoming)

7. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Ready Valid. Pending Integration Done! 3 4 1 1 There is someone very similar to a Product Owner, and sometimes (maybe on a weekly / monthly basis) he’ll call for a prioritization, estimation & planning meeting

8. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Ready Valid. Pending Intergration Done! 3 4 1 1 He will be responsible for writing stories, prioritizing them and even setting a Quality of Service for each story

9. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Ready Valid. Pending Integration Done! 3 4 1 1 On those meetings, maybe they’ll do a Demo and give their stakeholders (uh, I meant chickens) a whole vision of what they’re building and ask for some feedback

10. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Ready Valid. Pending Integration Done! 3 4 1 1 The team would be probably doing some kind of Daily Meeting, so they can share, coordinate and decide

11. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Ready Valid. Pending Integration Done! 3 4 1 1 In order to fine-tune their Kanban board, they’ll have to frequently reflect on how to become more effective (continuous retrospective)

15. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! They probably started with the typical Scrum Board, with columns mapping their value stream, but with no WIP limit or queues Burn-down:: Release Plan:

16. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! Sometimes they have to do some bug fixing, and sometimes the client asks for small and / or urgent tasks Burn-down:: Release Plan: !!!!

17. © 2010 Proyectalis Gestión de Proyectos S.L. This leads to Context Switching it’s identified as an impediment by the team, and even though the Product Owner understands it, client & product nature makes this emergent tasks unavoidable.

18. © 2010 Proyectalis Gestión de Proyectos S.L. Different approaches as a Separate Maintenance Team were tried but it made situation worse: maintenance team motivation dropped, knowledge was scattered and value stream was worsened for this kind of work.

20. © 2010 Proyectalis Gestión de Proyectos S.L. They looked at Scrum Literature, but all they could find was something about Focus Factor It was like reading “it’s your fault you can’t focus only on Product Backlog during Sprints, and we don’t care a bit about what happens out of your focus factor” 

22. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! They created a separate board (or a new lane on the old board) where they started to track bugs and emergent tasks Burn-down:: Release Plan: Selected. Dev. Valid.Pending Integration Done!

23. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! They didn’t estimate bugs or emergent tasks in advance, but they gave them some effort number once they were done. Burn-down:: Release Plan: Selected. Dev. Valid.Pending Integration Done! This was definitely a 3… 5 1

24. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! So at the end of the sprint, they could measure up how much effort did they put on bugs & unpredictable tasks Selected. Dev. Valid.Pending Integration Done! V Scrum V Kanban

25. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! (By the way, they called this “Kanban”, even tough it’s not really Kanban as there’s no WIP limit yet… Just hope the Kanban Police doesn’t find out ) Selected. Dev. Valid.Pending Integration Done! V Scrum V Kanban

26. © 2010 Proyectalis Gestión de Proyectos S.L. As soon as they had some numbers, they were able to commit better on how much effort would they put both in Scrum & Kanban development V Scrum V Kanban 80 20 85 20 75 30 70 35 75 25 80 25 ? ? ¿Your prediction? Uuuh… Well, on average we make something like 75 scrum points per sprint. Guess we can commit on that as long as you keep the kanban level safe… That means somewhere below 25 kanban points

27. © 2010 Proyectalis Gestión de Proyectos S.L. They were also able to understand and explain what happened during a given Sprint V Scrum V Kanban 80 20 85 20 75 30 70 35 75 25 80 25 60 50 Yaaargh! You failed on your commitment! No, in fact we did 110 points of aggregated velocity, which is quite good. It was YOU who told us to prioritize 50 Kanban points during the Sprint and made us fail the sprint goal That means we’re great and you suck. Maybe we should discuss this with the CEO  !

28. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! Soon, they started to differentiate good Kanban (value to the customer) from bad Kanban (bug fixing). Bad Kanban does not add to velocity, but affects it. Selected. Dev. Valid.Pending Integration Done! V Scrum V Kanban + V Kanban -

30. © 2010 Proyectalis Gestión de Proyectos S.L. So they could take decisions on things like increasing investment on bug fixing or stop emergent tasks if project is running late Velocity Vavg Scrum Vavg Kanban + Vavg Kanban -

31. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! They still had a problem: how to know on which task should they work next? Should they get the next Scrum task or the next Kanban task? Burn-down:: Release Plan: Selected. Dev. Valid.Pending Integration Done! ? ? ? ?

32. © 2010 Proyectalis Gestión de Proyectos S.L. Selected. Dev. Valid.Pending Integration Done! So they implemented a simple and visual quality of service mechanism(QoS) Burn-down:: Release Plan: COMMITTEDPRIO Fire! ASAP

33. © 2010 Proyectalis Gestión de Proyectos S.L. Fire! Selected. Dev. Valid.Pending Integration Done! The Fire lane meant “drop whatever you’re doing, there’s a server on fire and we don’t care if velocity drops – go fix it now!!!” Burn-down:: Release Plan: COMMITTEDPRIOASAP

34. © 2010 Proyectalis Gestión de Proyectos S.L. Fire! Selected. Dev. Valid.Pending Integration Done! There should be some kind on control mechanism on Fire QoS, so it doesn’t open the gates of hell to the team Burn-down:: Release Plan: COMMITTEDPRIOASAP Mwaa-hahaha!!!

35. © 2010 Proyectalis Gestión de Proyectos S.L. Fire! Selected. Dev. Valid.Pending Integration Done! I.E., every Fire request should be audited post-mortem and there should be a limit on how many of them you can open on a given sprint (that’s why it’s a small lane). Burn-down:: Release Plan: COMMITTEDPRIOASAP Was this really a fire??? No it wasn’t… Time to coach our P.O. Uh-oh…

36. © 2010 Proyectalis Gestión de Proyectos S.L. Prio Fire! Selected. Dev. Valid.Pending Integration Done! PRIO lane means “as soon as you finish what you are doing right now, please choose this urgent task”. Burn-down:: Release Plan: COMMITTEDASAP

37. © 2010 Proyectalis Gestión de Proyectos S.L. Prio Fire! Selected. Dev. Valid.Pending Integration Done! This is not as disruptive as a Fire, but still introduces some controlled context switching, so it shouldn’t be over-used by the Product Owner either. Burn-down:: Release Plan: COMMITTEDASAP

38. © 2010 Proyectalis Gestión de Proyectos S.L. ASAPPrio Fire! Selected. Dev. Valid.Pending Integration Done! The key words in the asAP QoS definition are “As Possible”, You should do some of those, but only as long as it doesn’t compromise the Sprint Goal Burn-down:: Release Plan: COMMITTED

39. © 2010 Proyectalis Gestión de Proyectos S.L. ASAPPrio Fire! Selected. Dev. Valid.Pending Integration Done! Soon the Team started to keep a separate Kanban Burndown so they could see if they could invest more on kanban or not. Sprint Burn-down: COMMITTED Kanban burndown: Uh-oh, hold the Kanban, guys!! Mmm…Guess I’d like some Scrum done too…

40. © 2010 Proyectalis Gestión de Proyectos S.L. Some teams found it difficult to give a story-point estimate to kanban tasks, so they used a different scale (hours, bug size, kanban points or whatever) V Scrum V Kanban 80 7500 85 7000 75 8000 70 8500 75 7500 80 7000 ? ? ¿Your prediction? Uuuh… Well, on average we make something like 75 scrum points per sprint. Guess we can commit on that as long as you keep the kanban level safe… That means somewhere below 7500 kanban points

41. © 2010 Proyectalis Gestión de Proyectos S.L. This worked like charm. You could even normalize average speeds and add them up, but that’s too much work, and there’s no real need to do so  Yaaargh! You failed on your commitment! No, in fact we did a lot more kanban than usual (you over- kanbanized us by 50%, which is quite a lot). It was YOU who told us to prioritize Kanban points during the Sprint and made us fail the sprint goal That means we’re great and you suck. Maybe we should discuss this with the CEO  ! V Scrum V Kanban 80 7500 85 7000 75 8000 70 8500 75 7500 80 7000 60 11.200

43. © 2010 Proyectalis Gestión de Proyectos S.L. 1) Sustainable pace is about working always towards your average speed There’s no use in aiming for top speed every single sprint, except for undermining team’s morale

44. © 2010 Proyectalis Gestión de Proyectos S.L. Min. V Max. V This will be done for sure (boring) Yougottabekiddin’ me!  We will probably end up somewhere over here (average speed) – a.k.a. “We can do this!”  Backlog and average speed

45. © 2010 Proyectalis Gestión de Proyectos S.L. 2) No tool is foolproof if your P.O. is opening 25 PRIO Kanban every single day, I’ll give you a clue: the problem is not in the post-it notes brand you’re using… 

47. © 2010 Proyectalis Gestión de Proyectos S.L. http://creativecommons.org/ licenses/by-nc-nd/3.0/ This presentation is based upon the ideas and work of many people. And while I’ve tried to recognize copyrights and give credit and attribution where possible, I cannot possibly list them all, so if you feel like there’s something that should be added, changed or removed from this presentation, please drop me an e-mail at angel.medinilla@proyectalis.com Special thanks to Henrik Kniberg, on whose article “one day in kanban land” is this presentation inspired. You rock!! 

Scrumban Ideacamp - Amsterdam Scrum Gathering 2010

You are reading a preview.

Scrumban Ideacamp - Amsterdam Scrum Gathering 2010

More Related Content

Viewers also liked

Similar to Scrumban Ideacamp - Amsterdam Scrum Gathering 2010

More from Proyectalis / Improvement21

Featured

Related Books

Related Audiobooks