Monday, January 25, 2010

Why the CIO Loves Agile Development

Let's say you're following my last two posts on negotiating business priorities. You're the CIO and have just been given a set of business priorities and now need to get your IT team aligned and executing. Let's play out a couple of scenarios:

  • You go back to the sponsors, assign a business analyst and work on requirements and a project plan. Once requirements are largely stable, you then look at delivery options, technology choices, assign teams, etc. We all know this as the waterfall approach.
  • Option b, the agile methodology - would essentially assign a team to work with the business manager to identify the most business critical, or technical risky aspects of the project. The team would then commit to some deliverables it would provide in a relatively short iteration - usually 2-4 weeks. The team would then offer to demo their work at the end of the iteration, then would focus on the next set of critical items for the project.
Obviously, I'm grossly simplifying but want to point out a couple of key differences. In waterfall, the project team has to engage the business manager for a significant amount of time and up front work to define requirements. Projects are broken into milestones that have no specified rhythm of delivery (some milestones may be weeks, others months) and no requirement or expectation to demo functionality. Bottom line, the CIO taxes the sponsors up for details and must wait an undefined period of time to demonstrate milestones of product delivery.

In agile, the CIO is getting the following significant advantages:
  • Low up front business investment - Teams can start working on the most critical features and risky technical areas without overtaxing the business sponsors for up front information.
  • Frequent delivery leads to better execution - Let's say your teams does two week iterations - in three months they complete six iterations giving them plenty of time to prove themselves, mature the agile process, and time for the CIO to make adjustments. This is really one of the key points since no team is perfect and tech execution always carries risk. CIOs can leverage this process to prove the team's credibility
  • Allowing Sponsors to prioritize at the beginning of each iteration leads to better Business / IT alignment. The Sponsor gets to prioritize based on customer feedback, the CIO gets the IT team direct engagement from the Sponsor.
If you're the CIO trying to establish credibility and dialogue (beyond negotiation!) between Business and IT, agile planning, development and delivery are very well constructed management processes to enable both short and long term success. Also see that:

Credibility + Dialogue = Collaboration and that Collaboration between Business and IT Leads to Innovation.

2 comments:

  1. This comment has been removed by a blog administrator.

    ReplyDelete
  2. Wonderful blog & good post.Its really helpful for me, awaiting for more new post. Keep Blogging!





    Agile Coaching

    ReplyDelete

Share