Top Banner
Transcending Cultures, Timezones, and Countries Presented by Mahesh Baxi Prepared by Chirag Doshi, Nitin Dhall & Mahesh Baxi January 2010 1
27

Transcending Cultures, Timezones and Countries

May 06, 2015

Download

Technology

Naresh Jain

How to Scale with Distributed Agile?

During this presentation we'll take you through an exciting journey of key lessons learned from one of the largest agile projects executed at ThoughtWorks which will cover:

* Key agile principles
* What challenges comes along with the scale of up to 200+ people with added complexity of distributed location
* How is it different from other agile projects in terms of planning ahead, release plans, scope management, infrastructure
* Communication - The most important ingredient for large scale agile projects to be successful
* What kind of team structure would work best?
* How to stay focused? How to identify bottlenecks and work through them
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • 1.Transcending Cultures, Timezones,and CountriesPresented by Mahesh BaxiPrepared by ChiragDoshi, NitinDhall & Mahesh BaxiJanuary2010
    1

2. 2
3. About Me
3
4. About the Topic
4
Key Tenets of Agile
Something that can negatively impact the success of an agile project
Large scale development
Distributed development
Command-and-control
Forcingagile on teams
5. What Does Scaling Mean?
Team Size Geographical Distribution Domain Complexity Technical Complexity Volumes DurationPerformance Release Planning Project Management DistributedMulti-Team Projects Functionality Stakeholders Integration Points
5
6. Journey Through Agile Key Principles
6
Early and continuous delivery of valuable software
Welcome changing requirements
Deliver working software frequently
Collaboration
Face-to-face conversation
Maintain constant pace indefinitely
Attention to technical excellence and good design
Self-organizing teams
7. What you dont want
7
8. Agility and Scale It can work
8
Shared goal, vision and objectives
Team Organization
Planning
Communication
Bottlenecks
Implementing new ideas
Team rotations
Continuous Integration
Staying Focused
Importance of Toolsets
9. Shared Vision, Goals & Objectives
9
10. Shared Vision, Goals & Objectives
10
11. Team Organization Typical Agile Team
11
Installables
Continuous Integration
Code Repository
Cruise
12. Team Organization Scaled Agile Team
12
Installables
Continuous Integration
Code Repository
Cruise
13. Planning
13
Inceptions
Across Teams
Roll-up Plans
Capacity& Schedule
Dependencies
14. Planning Watch out for
14
Story size and estimate baseline across teams
Story dependencies between teams
Individualteam velocity not to be used for comparison
Story and feature level automation
15. Agility and Scale It can work
15
Shared goal, vision and objectives
Team Organization
Planning
Communication
Bottlenecks
Implementing new ideas
Team rotations
Continuous Integration
Staying Focused
Importance of Toolsets
16. Communication
16
17. Communication Be Creative
17
Video conferencing
Scrum of scrums
Daily delivery catch-up
Information radiators
Release charts with key dates
Dependency charts
Program update meetings
Huddles
Knowledge sharing and maintaining shared context
18. Bottlenecks / Constraints put it in perspective
18
Story sign-offs
Automation / Regression
UAT
Release Planning
Builds
Check-ins / SVN / Branching
Capacity Planning
19. Ideas Ground-up, Keep it coming
19
Idea Wall
Larger Picture
High impact
Allocate Capacity
Communicate Innovation
20. Team Rotations - Ownership
20
Collective Ownership
Financial Impact
Capacity Planning
Technical Excellence
Aspiration / Happiness
21. Agility and Scale It can work
21
Shared goal, vision and objectives
Team Organization
Planning
Communication
Bottlenecks
Implementing new ideas
Team rotations
Continuous Integration
Staying Focused
Importance of Toolsets
22. Continuous Integration
22
Faster Feedback
Installers
Impact of broken builds
Single Build vs. aggregation
Conflict Resolution
Tool Selection
23. Staying Focused
23
Executive
Dashboard
Programme Status
Work Steam Status
24. Staying Focused
24
25. Importance of Tools Key Player
25
Scalability is important
Change is not easy
Easy to use / Intuitive
Flexibility
Reporting / Dashboarding
Should fit with architecture
26. Scalable Agility across cultures, countries and Time zones
26

  • Early and continuous delivery of valuable software

27. Welcome changing requirements 28. Deliver working software frequently 29. Collaboration 30. Face-to-face conversation 31. Maintain constant pace indefinitely 32. Attention to technical excellence and good design 33. Self-organizing teams