distributed scrum - recipe for success
TRANSCRIPT
![Page 1: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/1.jpg)
DISTRIBUTED SCRUM TEAM
Recipe for Success
- Sakshi Mahajan
![Page 2: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/2.jpg)
Who am I?
■ 11+ years experience in the IT industry
■ PMI-ACP Certified
■ Currently working as an Agile Technical Coach with Capital One Bank (A Fortune 500 company) in Virginia, US
■ Wore many hats in he Agile world – Scrum master, Product Owner, Agile PM, Coach
■ Experience in coaching Scrum, Kanban as well as XP practices
![Page 3: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/3.jpg)
Agenda
■ Scrum in Brief
■ Need for distributed teams
■ Challenges for distributed teams
■ Myths regarding scrum
■ Various Models of Distributed Scrum
■ Solution
![Page 4: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/4.jpg)
Scrum in Brief
![Page 5: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/5.jpg)
Need for Distributed Team
■ High quality resources
■ High business agility
■ Cost effective
Image courtesy : http://agilekata.co/
![Page 6: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/6.jpg)
Challenges for Distributed teams
■ Language
■ Time zone
■ Cultures
■ Lack of visibility
■ Various project phases – played by people distributed across
![Page 7: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/7.jpg)
Myth 1 of Distributed Scrum
■ Scrum methodology can only be followed in co-located teams
– Though it has been empirically proven that co-located teams can deliver faster, but scrum is not impossible in distributed teams
![Page 8: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/8.jpg)
Myth 2 of Distributed Scrum
■ Distributed development is chaotic
http://www.maxmetrics.com/
![Page 9: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/9.jpg)
Myth 3 of Distributed Scrum
■ Distributed development increases the amount of documentation
![Page 10: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/10.jpg)
Various Models of Distributed Scrum
![Page 11: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/11.jpg)
Development team co-located and Product Owner at a different location
Product Owner
Scrum Team
![Page 12: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/12.jpg)
Development team distributed
Product Owner
Scrum Master
Team
members
Team
members
![Page 13: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/13.jpg)
Multiple scrum teams – distributed (Scaled Scrum)
Product Owner
Scrum Team
Product Owner
Scrum Team
![Page 14: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/14.jpg)
Solution
Do you have the Agile Mindset ?
![Page 15: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/15.jpg)
Solution : Recipe for success
Communicate
Collaborate
Trust
![Page 16: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/16.jpg)
Solution: Open communication channels
■ Manager/scrum master should not be a bottleneck
■ Video conference wherever possible
Image courtesy : http://blogs.atlassian.com
![Page 17: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/17.jpg)
Solution : Team members visit the other side
■ Improves bonding
■ Increases trust
■ Helps understand each other's style of work
■ Cultural understanding
![Page 18: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/18.jpg)
Solution: Include all in Scrum Ceremonies
■ All meet at least once a day to synch thoughts
■ Keep in mind time zone difference
■ Everyone part of sprint planning –just once in 2-3 weeks
■ Everyone showcases in demos
■ Share opinion in retrospective
http://codevanced.net
![Page 19: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/19.jpg)
Solution : Continuous Integration
■ Frequent check-ins
■ Code review automation
■ Static code analyser
■ Automation suite integrated
■ Nightly builds
Reduces the risk of finding bugs late in lifecycle
![Page 20: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/20.jpg)
Solution: Digital ALM tools
■ Use ALM tools like Mingle, Rally, JiRA, etc and keep them updated
■ Digital whiteboards
■ All can see backlogs, burndowns, etc
![Page 21: Distributed Scrum - Recipe for Success](https://reader034.vdocuments.net/reader034/viewer/2022051017/55aa83bc1a28ab1f1c8b462d/html5/thumbnails/21.jpg)
Solution: Collaboration tools
■ Different time-zones, and different locations hinders collaboration
■ Documenting on wikis very useful
– All contribute and co-own
■ Found multiple tools useful
– Mindmeister
– Google docs
– Google apps
– Trello