the BPM freak !!

Home » BPM » Does Agile really means Fast ?

Does Agile really means Fast ?

Follow me on Twitter


The concern for most of the higher managements and the CxO level executives, is to promote dynamic growth and at the same time optimize the operational cost. This is quite a challenging task.

Although agilility is a critical component of most modern enterprise strategies, the key is going about change in an effective and sustainable way.

The word “Agility” is inferred differently by different groups of people. But in general, for the common crowd, “agility is all about being fast

Does Agile really means Fast ?

Not at all!! The underlying premise driving towards business agility is that such agility delivers superior business value, but what the haste to achieve agility might results in low quality. And moreover the speed of change is unsustainable from a business operational perspective, which might lead to deteriorating efficiency

If the current business cannot paceup with the changes that are being incorporated, the efficiency and the quality of the product gets HIT badly – which might actually result in drop of customers.

Its like mortgaging the company’s future by over-investing and taking too many risks. What is the point in preparing for the future if in the process you ruin your current business?

The following things must be in place for agile change to be valuable over time:

  • Choose the right changes that deliver better business outcomes with the least amount of resources and disruption.
  • Maintain business performance and integrity while executing change.

Agility is not really about speed but is about choosing the right changes and implementing those changes the right way in a timely fashion.

To sum-up : “A balance between the efficiency and effectiveness is very important for smooth movement of business and achieving the milestones based on sustainable changes”

The long-term effectiveness is actually based on continuous business re-engineering towards strategic objectives.Along with the strategic journey, an enterprise also needs to compliment, continuously adjust and optimize the current state efficiency to maintain business integrity and performance

A quick snapshot of a happy Enterprise Business Application architecture:

Please do share a thoughts and inputs on Agility at Enterprise level and correct me if my understanding is wrong.

This blog is based on the reading that have been doing recently on Combining Business Process Management and Enterprise Architecture for Better Business Outcomes” – IBM Redbook.


Happy Learning!! 🙂



  1. cashzilla says:

    Reblogged this on cashzilla.

  2. It’s an interesting perspective, I always enjoy your blog posts. I agree that agile isn’t about being fast. In my understanding being agile means delivering small amounts of value early, and being able to adapt to deliver the more value based on early feedback from stakeholders. I disagree that agile is about choosing the right changes, to me frequent deliverables of valuable, usable functionality allow you to quickly (there’s the speed part) get customer feedback. This feedback lets you know quickly if you’ve chosen the right things so that if your stakeholders don’t value what you’ve delivered you’re able to move onto what is right having spent a limited amount. The iterative delivery/feedback loop also means that you’re keeping pace with changes in the business which helps deliver what’s actually needed right now rather than what was needed when the changes were first planned.

    • Thanks a lot Amanda. nice to to learn you liked the blog posts. And very rightly said “agile refers to – delivering small amounts of value early, and being able to adapt to deliver the more value based on early feedback from stakeholders”
      Agreed these days, agile model is taking the driving seat and waterfall model is becoming obsolete. But there are still some processes in different domains where the frequency of change of business requirements is not very high i.e very stable and consistent. In such cases it is good to to go with a waterfall model as agile might be a overkill or overhead.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: