Edit Module
Bookmark and Share Email this page Email Print this page Print Pin It
Feed Feed

Mar 9, 201501:00 PMOpen Mic

Send us your blog for consideration!

Why agility matters in today’s evolving business climate

(page 1 of 2)

Agility [uh-jil-i-tee]

Noun

1. The power of moving quickly and easily; nimbleness.

2. The ability to think and draw conclusions quickly; intellectual acuity.

In the current business technology lexicon, “agile” and “agility” have become almost as ubiquitous as “cloud” and “mobile.” With business executives and technical folks alike talking about the importance of being agile, it’s easy to lose track of knowing why agility matters.

At the beginning of an agile transformation, the first question I always ask is, “Why are you interested in becoming agile?”

The response is almost always, “To deliver higher-quality products more quickly.”

This common answer mirrors the first definition of “agility” listed above. However, there is much more to the story.

A tale from the road

I have witnessed many organizations transform the way they develop software, and ultimately the way they run their businesses, by embracing agility. In one example, a client was building a new software product using more traditional methodologies:

  • Gather all product requirements up front.
  • “Architect” the product horizontally.
  • Build the product.
  • Test the product.
  • Release the product to the market/customer.

The company spent longer than a year and more than $1 million on requirements-gathering and product architecture. After these initial time-consuming and costly efforts, it had a hefty requirements document and an equally hefty technical architecture, but still little to show product-wise.

After embracing agile concepts and tools, it made the decision to immediately test the market for a new software product. To validate market interest, it quickly introduced a minimally viable product (MVP).

Once the MVP was released, it became clear there was not a market for the new product. This is a common tale in software product development (and product development as a whole). Had the client released an MVP sooner, even more valuable time and resources could have been saved. Lesson learned.

(Continued)

Add your comment:
Bookmark and Share Email this page Email Print this page Print Pin It
Feed Feed
Edit Module

About This Blog

Make your voice heard with IB's "Open Mic." Send your blog entry to Online Editor Jason Busch at jason@ibmadison.com for consideration.

Archives

Feed

Atom Feed Subscribe to the Open Mic Feed »

Recent Posts

Edit Module