program selection system

If planning for a large co-located 30+ development team is not enough to make you want to pull your hair out then try a 30+ development team located across several time zones, in places with different cultures and languages. Now, you’ve reached a level in the Agile planning game that would send most product owners running home to their mommies.

In an ideal world, everyone on an Agile team is collocated in one place, fostering cooperation and collaboration throughout the team’s growth. Unfortunately, the real world isn’t that simple. The current trend to fund teams split over multiple locations is inherently anti-Agile. Does this mean that we cannot do Agile with distributed teams? Distributed teams are a reality at Yahoo! In the past three years of coaching, we have seen creative solutions that that have allowed distributed teams to uphold the Agile Manifesto principle of people over process.

(above is for program)

Now that Agile has crossed Moore’s technology adoption chasm we’re finding that we need to address many of the scaling issues that we’ve mostly ignored until now. There is more to scaling agile than addressing the need of large or distributed teams. This presentation overviews the challenges and issues which the agile community must address in order to scale agile techniques and philosophies to meet the needs of modern organizations. Experiences and potential solutions from within IBM and several customers will be discussed, including both what works and what doesn’t.