Starting Agile in a Company
Download as PPT, PDF1 like1,237 views
The document provides tips for organizing teams, projects, and support when adopting Agile in a company. It recommends splitting the organization into cross-functional feature teams and creating a backlog of prioritized product features for each team to work on. Teams should be kept together permanently to become high-performing. Support work should also be planned and prioritized in the backlog instead of handled reactively to reduce fires and bugs. The document stresses starting the transition now with courage and external help if needed.
![Thank you Vaidas Adomauskas [email_address] http://scrum.agile.lt Let’s Scrum!](https://image.slidesharecdn.com/1vaidasadomauskasstartingagileinacompany-111006071422-phpapp01/85/Starting-Agile-in-a-Company-48-320.jpg)
Starting Agile in a Company
- 1. Starting Agile in a Company Tips how to organize projects/products portfolio and cross-functional teams Vaidas Adomauskas 2011-10-06
- 2. Vaidas Adomauskas Blog : http://scrum.agile.lt Twitter : @adomauskas SlideShare : http ://www.slideshare.net/vaidasa LinkedIn : http://www.linkedin.com/in/vaidas
- 3. Adform ( www.adform.com ) Founded in 2002 in Copenhagen, Denmark Handling campaigns in more than 25 countries 10 offices 130+ employees (100+ in Lithuania) 60+ developers
- 4. Agile in organization January April Split your organization Split your product Spilt time Optimize business value Optimize process $ $$$ Create product in increments Henrik Kniberg “ The essence of Agile” AgileEE 2010
- 5. Agenda Why teams? Organizing Teams Organizing Projects Organizing Support Summary and Q/A Split your organization Split your product Optimize business value $ $$$
- 6. Why teams?
- 7. Which group gets better results?
- 8. Viktorija Truba čiūtė http://www.slideshare.net/AgileLietuva/vieno-pilotinio-projekto-istorija , Lietuvos Agile Diena 2011 Which ones they will be?
- 9. No common purpose… Group of people Common purpose Performing team! A team comprises a group of people or animals linked in a common purpose . http://en.wikipedia.org/wiki/Team
- 10. http://en.wikipedia.org/wiki/Forming-storming-norming-performing Bruce Tuckman model: http://3.bp.blogspot.com/-H9_AmIgf464/TaJeGbKuyQI/AAAAAAAAARs/H_lLhVAXyeQ/s1600/Tuckmans+model.png It takes TIME to build performing team!
- 11. My team in Adform IMHO: it takes ~2 months to grow to performing team
- 13. Anyone else? … ir vienas svarbiausių dalykų - darbuotojai pradėjo dalintis žiniomis ir kartu siekti bendro tikslo, kartu atsakyti už klaidas, neįvykdytus įsipareigojimus . "Ashburn International" … one of the most important things – employees started sharing knowledge and seek for common goal together, care for mistakes and not fulfilled commitments together. "Ashburn International" http://www.linkedin.com/groups/Scrum-CSM-CSP-95979.S.71543428
- 14. Permanent teams are most effective
- 15. Organizing Teams
- 17. Feature Team Component Team How to split? Craig Larman, Bas Vodde - “Practices for Scaling Lean & Agile Development”: http://www.craiglarman.com/
- 18. Component Teams… Good Easy start - developers know components, not features Cross-functional - testers/analysts divided to teams Consider How to divide components? How to run valuable sprint reviews ? How to plan features ? Warning! Are you really that big (more than 50 people)?
- 19. How many teams? #teams = #people / 7 Warning! It seems easier to work in smaller teams… be aware more teams – more “management”!
- 20. Anyone else? Company: “We need to split our departments in different cities and organize them around our products. ”
- 21. Form cross-functional feature teams
- 22. Organizing Work
- 23. Create Product Backlog (Project Portfolio) List all projects Prioritize (order) them
- 24. Create Product Backlog (Product) Slice your product Prioritize slices
- 25. What tool to use?
- 26. Follow experiment @adomauskas
- 27. What if our projects are big? Break it to minimal marketable features (MMF) Project 1 Project 3 Project 2 (3 months ) P1F1 P2F1 Project 3 P1F2 P2F2 P1F3 Time to Complete Project 1 (4 months)
- 28. Work for teams (not vise versa!) http://www.solutionsiq.com/Portals/93486/images/many-teams-many-backlogs-one-backlog-agile.png
- 29. Anyone else? Big insurance system cars, houses, life insurance; customers data, integration with banks, accounting and billing, authorization flows… Insure a car No integrations, billing… Insure Volvo cars Insure Volvo V70
- 30. Work for teams (not vise versa)
- 33. Which one your company looks more alike to? Planned work Unplanned work
- 34. Fires! Urgent client requests Production bugs Minor features Development bugs
- 35. Urgent client requests Is it urgent? Yes! Will you use it tomorrow? No… Will you use it next week? Yes… Great, we will do it during in next sprint (NOT urgent)
- 36. Urgent client requests Is it urgent? Yes! Will you use it tomorrow? Yes… Really, we will check? Ok.. Maybe next week Great, we will do it during in next sprint (NOT urgent)
- 37. Urgent client requests Is it urgent? Yes! Will you use it tomorrow? I need it yesterday!!! OK, Get on it right now (urgent) How we can plan this next time ?
- 38. Fires! Urgent client requests Only small % Plan most in product backlog Production bugs Critical ones – yes, decrease them! Major/minor – plan them in product backlog Minor features NO, plan them in product backlog Development bugs NO, this is part of sprint task
- 39. Team handles it Time “pillow” Max 30% of sprint Visualize on sprint board Measure it! Get it to 0%!
- 40. Support team Good: “ Focus” on bug fixing Issues: Knowledge of the system Demotivating work No team ownership for good code
- 41. Support is our life… Are you sure??! Use Kanban!
- 42. Prevent the fires!
- 43. Summary
- 45. Courage
- 46. External help
- 47. Start NOW
- 48. Thank you Vaidas Adomauskas [email_address] http://scrum.agile.lt Let’s Scrum!
Editor's Notes
- #9: How long will they work together? Usually… less than a 1 month Usually… analysts at the beginning , testers will join in the end How many projects will they work on? Usually… 2 or more What activities will we take to build a team ? Usually… beers!