Art of distributed scrum teams
This document discusses challenges with distributed teams, ways to improve collaboration and trust between distributed teams, and practices for continuous integration and continuous delivery. Some key challenges with distributed teams include communication and collaboration. The document recommends using tools like video conferencing and messengers, as well as innovative ways to conduct design meetings and retrospectives remotely. It also stresses the importance of including all teams early in discussions, having common processes and standards, and dividing responsibilities across phases rather than having different ways of working. The document outlines practices for continuous integration like writing automated tests, committing code frequently, and fixing broken builds immediately. It describes how continuous integration and continuous delivery can reduce risks, improve collaboration and feedback, and help develop software more rapidly.
Art of distributed scrum teams
- 2. Challenges with Distributed Teams Communication Collaboration and Trust What not to do in Distributed Teams? Continuous Integration and Continuous Delivery
- 3. Collaboration Ways of Working Level of Trust Between Teams Yes/ No Democratic/ Hierarchical Good/Average/ Poor Within Teams Yes/ No Democratic/ Hierarchical Good/Average/ Poor
- 4. Face to Face communication Tools Telepresence / Video conference Webex , Skype Hip Chat, Messengers Innovative ways to do Design meetings, Retrospectives Build relationships
- 5. Include teams early in discussions Have common responsibilities for all. Everyone does design, coding, testing, support Have a common process that everybody follows Have common recruitment standards
- 6. Slice the responsibilities across team based on phases Have different ways of working Water-cooler effect Measuring story points across teams Euro Disney effect
- 7. • Reduce Risks • Create deployable software at any time • Significantly reduces integration problems • Increases opportunities for feedback • Develop cohesive software more rapidly • Improves Collaboration • Establish confidence
- 8. CI Practices Write automated developer tests All tests and inspections must pass Run private builds Don’t commit broken code Fix broken builds immediately Commit code frequently Avoid getting broken code
- 9. Components of CI system
- 10. Reduce cycle time from Development to Production Automated, reliable ,repeatable release process Makes the process of build, deploy, test and release visible to everyone Improve collaboration between teams Reduces human error Improves the feedback loop Enables the team to deploy and release any version of software to any environment Reduces Cost
- 13. Continuous Delivery by Jez Humble and David Farley Continuous Integration by Paul M. Duvall With Steve Matyas and Andrew Glover