Agile riga jelena_scicko_v3
- 1. Agile experienceat Evolution Gaming LatviaJelena Scicko,Agile Riga Day 2011, 05.03.2011
- 2. Jelena ScickoQA engineer at Evolution Gaming Latvia since January 2010;
- 3. Before - QA engineer, business analyst, project manager @ bank (5 years)Agile experience – 1 year
- 5. DevelopmentOperationsHead of newproductsDEVELOPMENTNew products, featuresEnhancements,Bugfixes,New functionalityDBPMsProjectsCTOTechnical architectureRMTechnical enhancements, architecture,environments
- 6. Presentation purposeShare experience:What was good and was not with SCRUM?Why did we switch to Kanban?What did we achieve and what are we missing?
- 7. WhySCRUMwasgood?(for us)Simple: split organization into teams, split work into prioritized list of small deliverables, split time into short fixed-length iterations, optimize the process by having a retrospective after each iteration;Clear: 3 roles prescribed, SCRUM master leads the process, process is visualized on the board, stand-up meetings;Light: no heavy documentation, no prescribed engineering practices.
- 8. What wasnot good in SCRUM (for us)Fixed scope of the sprint – cannot take high priority items as soon as they appear;Team growth and resource conflicts – how to split the team? How to share resources?;Several big projects planned – how to split? Why to split?Prioritized backlog – prioritization effort will only affect the next sprint.
- 9. Why Kanban?WIP limited per workflow state;
- 10. Can add new items whenever capacity is available;
- 11. Cross-functional teams are optional. Specialist teams allowed;
- 12. No particular item size is prescribed;
- 13. Prioritized product backlog is optional;Kanban challengeHow to define WIP?How to set priorities?Do we need stand-up meetings and the Master?
- 14. What was achieved with Kanban?Team spitted into Business Units – dedicated team membersfor each BU;
- 15. WIPs are under control – depending on the item size and priority;
- 16. Priorities are under control within the BU and within the whole backlog;Conclusions andadvicesfor KanbanHave some reserve in WIPs for Live incidents;Consider, what will you do, if limit will be too small or too high?Use board, experiment with columns and rows – it will bring fun and order;Think about having a Master and stand-up meetings;Consider, how will you set priorities?
- 17. ConclusionsBoth, SCRUM and Kanban are good, because they leave a lot of space for experiments:Size and number of teams;WIP limits;Length of 1 iteration;The less constraints you have, the more you can experiment, the more you can fail, the more you can win!Do not limit yourself to one tool;Non of the tools is perfect or complete, except “Do the right thing”
- 18. Thank you!Questions are welcomed!