Extreme Agile Wallboards – Delta and Northwest Style

“Delta and Northwest announced their merger in April 2008. They immediately began planning for what turned out to be an 18-month sprint to integrate 1,200 systems across the two airlines — everything from customer loyalty programs to aircraft operations, all without interrupting service. Managers built this master guide to break down when these systems would need to start working together. Each note represents a project that could involve thousands of tasks.”

Two things to note here regarding this wallboard:

  • 18-Month Sprint – Really? Is that Agile? – I know that Delta/Northwest and the people working on this project wanted this project to be “Agile.” I’m seeing now… that it may be a different flavor of Agile…
  • Managers built this – Need I say more?

“Ms. Wise, who has a doctorate in applied mathematics, devised a low-tech solution: she set up a timeline of the steps that had to be performed by pinning colored Post-it notes on the wall of a conference room.”

So… maybe it wasn’t an Agilist who built it. Would love to have anyone who knows how this is going comment. What a giant undertaking!!!

[VIA: NYTimes]

9 Replies to “Extreme Agile Wallboards – Delta and Northwest Style”

  1. Didn’t see anything in the actual NYT article that suggested anyone spoke about being agile in any way or used the term “sprint.” Given this, what is the concern for an 18-month project length and the fact that managers were doing the planning (given the size and minutiae involved)?

    1. Actually… I’m speaking from ‘personal’ knowledge here. This project was potentially a client of mine… I know they are doing agile 🙂

      1. What does “doing Agile” mean in the context of merging two airlines? Not asking for anything proprietary, but what might convince someone they should consider using an Agile approach for this broad and “scattered” an effort (esp. based on the things in the NYT article)? I can see certain iterative and close communication ideas being useful (as well as some others), but as this is not a software effort, what actual “practices” might have been envisoned as useful and Agile? (We just had a Scrum Gathering Open Space discussion about Agile for Non-Software in Seattle, so this interests me.)

  2. New here, just found the site while looking for Agile conferences in Amsterdam.

    You could do an Agile “sprint” over 18 months, ok sprint would be the wrong word to use but if someone was using a more kanban approach or even “scrumban” people might see this as an 18 month sprint?

    Although I would like to know what their WIP limits are going by that board 😉

Leave a Reply