Art of distributed scrum teams

13
ART OF DISTRIBUTED SCRUM TEAMS Usha Seetharaman

Transcript of Art of distributed scrum teams

Page 1: Art of distributed scrum teams

ART OF DISTRIBUTED SCRUM TEAMS

Usha Seetharaman

Page 2: Art of distributed scrum teams

Agenda Challenges with Distributed Teams

Communication Collaboration and Trust

What not to do in Distributed Teams? Continuous Integration and Continuous

Delivery

Page 3: Art of distributed scrum teams

Challenges with Distributed Teams

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

Page 4: Art of distributed scrum teams

Improve Communication Face to Face communication Tools

Telepresence / Video conference Webex , Skype Hip Chat, Messengers

Innovative ways to do Design meetings, Retrospectives

Build relationships

Page 5: Art of distributed scrum teams

Be Truly Collaborative and Inclusive

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

Page 6: Art of distributed scrum teams

What not to do in Distributed Agile Teams

Slice the responsibilities across team based on phases

Have different ways of working Water-cooler effect Measuring story points across teams Euro Disney effect

Page 7: Art of distributed scrum teams

Why Continuous Integration

• 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

Page 8: Art of distributed scrum teams

CI Practices

Write automated developer

testsAll tests

and inspections must pass

Run private builds

Don’t commit

broken code

Fix broken builds

immediately

Commit code

frequently

Avoid getting broken code

Page 9: Art of distributed scrum teams

Components of CI system

Page 10: Art of distributed scrum teams

Why Continuous Delivery 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

Page 11: Art of distributed scrum teams

Improve Value by Value Stream Mapping

Page 12: Art of distributed scrum teams

CI-CD Pipeline

Page 13: Art of distributed scrum teams

References Continuous Delivery by Jez Humble and

David Farley Continuous Integration by Paul M. Duvall

With Steve Matyas and Andrew Glover