Scaling Agile To Work With Distributed Teams

1
Scaling Agile To Work With Distributed Teams

• Presented By MD.HABIBUR RAHMAN
• ID107229

2
Main Goal

• Scaling
• Distributed teams

3
The objectives are

• Know how to proactively manage dependencies
  between two teams
• Be able to scale the iteration planning meeting
• Understand how to cultivate communities of
  practice and the role of these play in scaling
• Be able to help teams

4
A. Use Rolling Look ahead planning
5
B. Share Team Members
6
Two Types of interfaces to worry about

• A. Unattended interface
• At least one is aware of the interface, but no
  one is doing anything about it.
• B. Unidentified interface
• An interface that exists but that no one has
  discovered yet.

7
C. Use an integration

• Takes on the unattended interfaces
• while on the look out for unidentified ones
• Can be virtual team with part time members
• common up to perhaps a dozen teams
• Larger projects will have a full time team
• may be more than one
• Not a dumping ground for poor performers

8
Scale up iteration planning

• Iteration planning meeting is the hardest to
  scale
• Other meetings require less coordination
• Two general approaches
• Stagger by a day
• The big room

9
Big room
10
Coordinate Teams

• Hold Scrum of scrums meeting
• Use communities of practice

11
(No Transcript)
12
Communities practice
13
Create better Environment for communities
14
Distribute Teams
15
Collaborating collocating teams

• Each Teams has all needed skills
• Teams in different locations work independently
  but collaborating to coordinate their work

16
Deliberately distributed teams

• Teams in different locations work independently
  but collaborate to coordinate their work.
• Each location has all needed skills
• We could from collaborating collocated teams
• But we choose not to
• Individuals in different cities work together as
  one team

17
Create coherent

• Acknowledge big cultural differences
• Acknowledge small cultural differences
• Strengthen functional and team subcultures
• Build trust by emphasizing early progress

18
Change how to communicate

• Add back some documentation
• Cannot rely as much on talking
• Add detail to the product backlog
• Encourage lateral communication

19

• Thanks to all