Scaling Agile To Work With Distributed Teams Presented By: MD.HABIBUR RAHMAN ID:107229 Main Goal • Scaling • Distributed teams 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 A. Use Rolling Look ahead planning B. Share Team Members 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. 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 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 Big room Coordinate Teams • Hold Scrum of scrums meeting • Use communities of practice Communities practice Create better Environment for communities Distribute Teams Collaborating collocating teams • Each Teams has all needed skills • Teams in different locations work independently but collaborating to coordinate their work 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 Create coherent • Acknowledge big cultural differences • Acknowledge small cultural differences • Strengthen functional and team subcultures • Build trust by emphasizing early progress Change how to communicate • Add back some documentation • Cannot rely as much on talking • Add detail to the product backlog • Encourage lateral communication Thanks to all