The first read through Agile Principles and practices gives an impression that Agile is suited for smaller, co-located projects. A deeper thought around the agile principles, imbibing the principles and then trying to push the boundaries by trying to use agile principles and practices on larger distributed projects can eventually lead to amazing results, but the path is not well paved and has a number of pit falls.
For anyone trying to use Agile on a large distributed project, it is important to understand the pit falls and what might succeed. In this talk, Nitin will be sharing his experience and learnings of leading multiple distributed agile projects with team sizes ranging from 30 to 220 members, over the last 5 years. This is must attend talk for anyone trying to use agile on large distributed projects.

Outline/Structure of the Experience Report

The session will be focused on discussing my expierence of applying the agile principles and practices to large teams ranging between 30-220 members. I will be talking about my learnings from my success and failures in running large agile teams.

Learning Outcome

The session will be focused on discussing my learning from from my success and failures in running large agile teams. The attendees will be able to take away a lot of ideas about what has succeeded and what did not for managing large agile teams. This will be thought provoking for the attendees and will help them to decide on their own strategies for managing large agile teams.

Target Audience

Anyone who is trying to scale an agile team beyond 10-15 member team. It will be very useful for IT Directors, Head of Development/Engineering, who are trying to scale agile teams.

schedule Submitted 7 years ago