• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Transcending Cultures, Timezones and Countries
 

Transcending Cultures, Timezones and Countries

on

  • 2,617 views

How to Scale with Distributed Agile? ...

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

Statistics

Views

Total Views
2,617
Views on SlideShare
2,546
Embed Views
71

Actions

Likes
0
Downloads
37
Comments
0

6 Embeds 71

http://blogs.agilefaqs.com 62
http://www.slideshare.net 3
http://agilefaqs.com 2
http://nareshjain.com 2
http://translate.googleusercontent.com 1
http://localhost 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Transcending Cultures, Timezones and Countries Transcending Cultures, Timezones and Countries Presentation Transcript

    • Transcending Cultures, Timezones,and CountriesPresented by Mahesh BaxiPrepared by ChiragDoshi, NitinDhall & Mahesh BaxiJanuary 2010
      1
    • 2
    • About Me
      3
    • 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
      Forcing agile on teams
    • 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
    • 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
    • What you don’t want
      7
    • 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
    • Shared Vision, Goals & Objectives
      9
    • Shared Vision, Goals & Objectives
      10
    • Team Organization – Typical Agile Team
      11
      Installables
      Continuous Integration
      Code Repository
      Cruise
    • Team Organization – Scaled Agile Team
      12
      Installables
      Continuous Integration
      Code Repository
      Cruise
    • Planning
      13
      Inceptions
      Across Teams
      Roll-up Plans
      Capacity & Schedule
      Dependencies
    • Planning – Watch out for
      14
      Story size and estimate baseline across teams
      Story dependencies between teams
      Individual team velocity not to be used for comparison
      Story and feature level automation
    • 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
    • Communication
      16
    • 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
    • Bottlenecks / Constraints – put it in perspective
      18
      Story sign-offs
      Automation / Regression
      UAT
      Release Planning
      Builds
      Check-ins / SVN / Branching
      Capacity Planning
    • Ideas – Ground-up, Keep it coming
      19
      Idea Wall
      Larger Picture
      High impact
      Allocate Capacity
      Communicate Innovation
    • Team Rotations - Ownership
      20
      Collective Ownership
      Financial Impact
      Capacity Planning
      Technical Excellence
      Aspiration / Happiness
    • 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
    • Continuous Integration
      22
      Faster Feedback
      Installers
      Impact of broken builds
      Single Build vs. aggregation
      Conflict Resolution
      Tool Selection
    • Staying Focused
      23
      Executive
      Dashboard
      Programme Status
      Work Steam Status
    • Staying Focused
      24
    • Importance of Tools – Key Player
      25
      Scalability is important
      Change is not easy
      Easy to use / Intuitive
      Flexibility
      Reporting / Dashboarding
      Should fit with architecture
    • Scalable Agility across cultures, countries and Time zones
      26
      • 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
    • 27
      Thank you!