1 / 14

Scaling Agile: Finding your Agile Tribe

Scaling Agile: Finding your Agile Tribe. CHEN YI-XUN. Outline. Introduction Project Background Project Challenges What We Learned Conclusion. Introduction. This report describes an experience with a largescale global development effort

anne
Télécharger la présentation

Scaling Agile: Finding your Agile Tribe

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Scaling Agile: Finding your Agile Tribe CHEN YI-XUN

  2. Outline Introduction Project Background Project Challenges What We Learned Conclusion

  3. Introduction • This report describes an experience with a largescaleglobal development effort • our primary challenge to scalingagile became finding the right people to form our agile“tribe • It‘s led to an identified set of attributes that describe the type of person that we believe will thrive in a large-scale Agile environment.

  4. Outline • Introduction • Project Background • Project Challenges • What We Learned • Conclusion

  5. Project Background • The project under discussion was a large-scaleglobal development effort for the Health Services (HS)division of Siemens Medical Solutions USA • Thehealthcare industryservices to over 5,000healthcare organizations in 20 countries • The projectteam consisted of 300 developers, product analysts,scrummasters, and testers across 25 scrum teams inthree development sites: USA, India, and Europe

  6. The project was organized into three sub-programs: • core application(1)---->(11) • common architecture components(2)---->(7) • a common supporting application(5)---->(7)

  7. Outline • Introduction • Project Background • Project Challenges • What We Learned • Conclusion

  8. Project Challenges • Integration & Dependency Management • The number of concurrent work streams increased, sodid the number of dependencies. • Managing Heavily-Used Services • As their customer baseincreased, so did the requirements to customize, or“tweak”, services to accommodate the consumers ofthese services • Managing Distributed Teams

  9. Outline Introduction Project Background Project Challenges What We Learned Conclusion

  10. What We Learned When addressing thesechallenges, we sought to adhere to the basic principalsof the Agile manifesto as much as possible We sought to empowerindividuals and teams to make decisions and formulatetheir own processes, and to take calculated riskswithout fear of reprisals

  11. Most of the Scrum teamsrapidly evolved to highly performing teams anddemonstrated tremendous productivity. • In smaller projects • we work encourage team members to focus exclusively on their individual team goals as expressed in the backlog • Inlarge-scale projects • team members must participate incross-team activities and allocate time to project-wideactivities

  12. Outline Introduction Project Background Project Challenges What We Learned Conclusion

  13. Conclusion The challenge is locating these people Rule #1:Don’t base your decision on Agile experience! Agile isa mindset, not a skill set.

  14. Q & A

More Related