CONFLUENCE OF AGILE METHODS- A JOURNEY
Reference: http://www.sei.cmu.edu/library/abstracts/reports/08tn003.cfm


1. Agile Manifesto (2001) - Kent Beck, Ron Jeffries, Alistair Cockburn, Jim Highsmith, Bob Martin, Mike Beedle, Ken Schwaber, Jeff Sutherland group of leaders who represented the most successful of the new lightweight methods met.

• Authored the Manifesto for Agile Software Development [ (C) 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice]

2. Agile Alliance (Non Profit Organisation) -Mary Poppendieck & others, branched from Agile Manifesto.

• Organising Agile Conference in US yearly to encourage the adoption of Agile Methods.
• Support those who explore and apply Agile principles and practices to make the software industry productive, humane, and sustainable

3. Agile Project Leadership Network (APLN- Non Profit Organisation-2005) - Jim Highsmith & Alstair Cockburn gathered a similar group of early Agile adopters, including David Anderson, Mike Cohn, Todd Little, and others.

• Established the six management principles known as the Project Management Declairation of Inderdependence (PMDoI) [©2005 David Anderson, Sanjiv Augustine, Christopher Avery, Alistair Cockburn, Mike Cohn, Doug DeCarlo, Donna Fitzgerald, Jim Highsmith, Ole Jepsen, Lowell Lindstrom, Todd Little, Kent McDonald, Pollyanna Pixton, Preston Smith and Robert Wysocki.] to encouraging better leadership and management in the IT sector
and software engineering profession.

 Level 4 Behaviours using Agile/Lean (Kanban)

1. David Anderson has achieved predictability in sustaining engineering at Corbis with a release every two weeks, but the content of the release is not bound until five days prior to release due to the unpredictable nature and dynamic character of the work scope. (Corbis - Microsoft Corp)

Kanban in Action @ Corbis - Quote"kanban system allows us to deliver on 3 elements of my recipe for success: reduce work-in-progress (in fact it limits it completely); balance capacity against demand (as new CRs can only be introduced when a kanban card frees up after a release); and prioritize. We hold a business prioritization meeting once per week with vice presidents from around the company. They get to pick new CRs from the backlog to allocate against free kanban cards. This forces them to think about the one, two, or three most important things for them to get done now. It forces prioritization."

Sixth Month Review @Corbis -  Results speak for themselves, quote

1. 13 software release to production in 6 months

2. Average of a release to production every 9.5 business days

3. Zero escaped defects since 6 months

The challenge now is to take our success with software maintenance and apply it to major projects in our portfolio.

Corbis Published reults of KANBAN

 

2. High Maturity Agile Team: Sky in London - Sky satellite broadcasting being run by Simon Baker and Gus Power. Quote" Gus was all apologetic about how they hadn’t yet matured to provide the financial metrics to show return on investment against features developed like I describe in my book. The truth is I’ve never seen a team that could do it consistently. At Corbis we were only partially capable of relating cost and investment to realized value in the market."