Agile Project Management: Why?

This is part 1 of a 10-part series I am writing on Agile Project Management, by Jim Highsmith.

The first question to ask is, “Why should I consider using Agile Project Management?”

Time-to-market has shrunk. A lot of it had to do with “Internet-time”, but even after the bubble burst our schedules did not expand again. I have found unrealistic schedules to be the norm, with the occasional fantasy schedule thrown in for variety.

Customers rule. Customers are pickier than ever, and if you don’t have what they want, someone else will. There are too many competitors willing to fill a market need, so we can never become complacent in our offerings.

These factors combine to force the hand of anticipatory project management, the kind that “plans the work and works the plan.” But if the market is changing rapidly, then the plans set in stone 6 months ago really are outdated.

One response is to develop products incrementally, focusing on adding the most value first. This practice, known as iterative development, leads to software that evolves into a killer application instead of trying to design and implement one on first pass.

Agile Project Management (APM) recognizes that opportunity and risk lie in the software, not in the project management approach. So APM attempts to mitigate risk and maximize opportunity in order to meet the business objective of Reliable Innovation, which consists of five parts: continuous innovation, software adaptability, reduced delivery schedules, people and process adaptability, and reliable results. It attempts to deliver reliable innovation through its principles and framework (in tomorrow’s post!).

This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

3 Responses to Agile Project Management: Why?

  1. Amit Parikh says:

    It’s the need of the hour. It’s like we have no choice by denying it else the Project is a scrap or the vendor looses the Project. The stake vendor holders find themselves no more with the project.

    APM delivers light weight components and slowly progresses to complex deliveries. It is planning and implementation at it’s peak. Prepare, analyze, construct, test and deliver. Next time tie earlier deliverables with the new ones and proceed. It is a progressive exponential way to deliver. This also reduces the risk of employee retrenchment.

    Amitkumar Parikh


  2. Darrell says:

    Crimar – hey, I’m just summarizing from the book on this one. I kind of feel that agile methodologies are self-explaining if you’ve ever worked in a process-intensive work environment.

  3. crimar says:

    pretty brief ‘artivle’

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>