10 Tips for Distributed Agile Success
Download as PPTX, PDF0 likes598 views
The document outlines ten tips for successful distributed agile practices, emphasizing the importance of organizational agility for global success. Key recommendations include starting with teams familiar with agile, co-locating team members initially, and utilizing effective tools and communication. The document also references a case study that highlights significant improvements in innovation cycle time and reduced development costs through agile transformation.
10 Tips for Distributed Agile Success
- 1. Distributed Agile 10 Tips for Success
- 2. “88% of executives cite organisational agility as key to global success.” “50% say that agility is not only important, but a core differentiator.” Agile businesses have 29% higher earnings per share. Why Agile?
- 3. Why distributed Agile?
- 5. 1. Don’t do distributed Agile!
- 6. 10 Point Checklist 2. Start with a team that ‘gets’ Agile
- 7. 10 Point Checklist 3. Start co-located for a few weeks 3. Start co-located for a few weeks
- 8. 4. Rotate people through locations
- 9. 10 Point Checklist 5. Attempt similar time zones
- 10. 6. Tools are essential to success
- 11. 10 Point Checklist 7. Have a „good‟ I.M. in each location 7. Have a good IM at each location
- 12. 8. Structure teams to the work
- 13. Review Review Iden fica on Risk Daily Stand- Look Ahead Management Planning ups Planning Showcase Retrospec ve Planning Iden fica on Iden fica on Iden fica on Assessment Review Assessment Iden fica on Response Response Review Review Offline Iden fica on Conversa on Assessment Response Review 9. Do Continuous Risk Management
- 14. 10. Continuously Improve!
- 15. Summary… It can be done… Revamp HP LaserJet software across product line 5% to 40% innovation Cycle time from 2 months to 1 day Reduced development costs by 40% Enterprise Agile planning & prioritization 400 people, distributed Complex and fast changing market 3 years for transformation Started with CI & CD!
Editor's Notes
- #2: Net Margins +20%Return on Assets +30%Revenue Growth +8%
- #3: Net Margins +20%Return on Assets +30%Revenue Growth +8%
- #4: Distributed Agile is hardHave a good reason to do it, think about why and the cost/benefitCo-located agile teams are higher performingDifferent Languages and cultures make things even harder
- #5: Distributed Agile is hardHave a good reason to do it, think about why and the cost/benefitCo-located agile teams are higher performingDifferent Languages and cultures make things even harder
- #6: Distributed Agile is hardHave a good reason to do it, think about why and the cost/benefitCo-located agile teams are higher performingDifferent Languages and cultures make things even harder
- #7: Coaching Agile remotely is very hardDistributed Agile is mature AgileUse the seed and growprocess
- #8: Establish the project together, inception, initiate, release planning etcSeed and grow continuedBuild Relationships, build the teamUnderstand the problem and the domainGet comfortable before you get uncomfortable
- #9: Rotation keeps knowledge sharing and context sharing freshPeople get to see real problems first handRelationships are built and re-builtContext and challenges are shared through a common perspective
- #10: 2 hour time zone is a lot easier than 12Stand-ups are staggered for time zonesUS is turning to BrazilChina and Australia and AsiaPac
- #11: Electronic toolsReliable and redundant internet connections are mandatory and considered priority #1Project Management Tools – Mingle, JIRA, Community tools and sharingVideo walls and Skype – always on connections provide a window and connectivity you don’t appreciate until you’ve worked with a distributed teamsGet good quality cameras and microphonesDoesn’t have to cost the earth
- #12: Distributed teams meansDistributed CoordinationDistributed CommunicationDistributed Problem SolvingHaving dedicated end-points and conduits such as IM’s or leads aids thisYOU CAN ALWAYS NOT USE THEM and use mature, agile, functioning teams instead
- #13: LocationRolesProject is unclear and complex business you may need more BA’s closer to the source of informationIf timelines are tight and the team is working on established product, it may be more appropriate to have more devs and QA’sQuantitySkill Level and Capability
- #14: Risk management is overlooked by a lot of Agile teamsRisk management by the team is even more important to do regularlyGet away from registers and PM’s doing itCreate shared walls, stand-ups and meetings for the team to talk about risk and resolve issues
- #15: Get it workingThen get it working betterThere’s always room for improvementEspecially with distributed agile teams.