Skip to main content
The Agile Dilemma



Who doesn’t want to be agile? Ballet dancers, weight lifters, and business executives alike aspire to be agile – that liveliness, coordination, and quickness is something we all desire in life and business. Why then is there an “Agile Dilemma” in software development?

voke defines the “Agile Dilemma” as the inherent risk and confusion created by the business desire for speed and flexibility misinterpreted as a mandate to participate in the developer-centric movement called Agile, which may not be appropriate to all organizations or projects.

What this really means is that business executives are expressing the need to be flexible, nimble, and responsive to customers to ensure satisfaction and a competitive edge. The software development team is listening to this business mandate and interpreting it as a call to participate in the Agile movement. But, is participation in the Agile movement right for every organization or every project?

We wanted to find out how software teams were interpreting and using Agile, so we conducted a survey. The survey ran from July 2011 to January 2012. We had over 200 individual participants from around the globe and companies of all types and sizes take the survey and give us their opinions on Agile as it relates to software development.

Once the survey was completed and the data analyzed we wrote a report that details all of the findings and provides analysis. Just to give you a couple of examples of what we found:

• Participants shared over 100 unique definitions of what Agile is

• 57% report confusion about Agile

These stats give you some insight as to why there is an “Agile Dilemma”.

The full report is available to voke’s premium research subscribers or available for on-demand purchase.

Do You Know What Your Cost of Rework Is?
While we were surveying people about Agile, it became clear that the cost of rework of their software was largely a mystery. Rework is something everybody has, everybody budgets for, but are reluctant to admit it – at least publicly.

Since rework is something everybody must deal with, we thought it would be valuable to create models associated with rework in Agile and non-Agile environments. voke analysts used scenarios described in the Agile survey to develop three scenarios focused on the cost of rework in an Agile environment. As a baseline, we used the standard “Cost of Quality” model for rework in a non-Agile environment.

These rework models have been requested by software engineering teams of all types for quite some time. Now, you can see how rework numbers compare for Agile and non-Agile projects.

The full report is available to voke’s premium research subscribers or available for on-demand purchase.

Help your teams with the "Agile Dilemma" and understand the cost of rework – the answers may surprise you!

t














Popular posts from this blog

Release Management - We Want YOUR Opinion

Releasing software, the last step to getting your software creation to your customers! Every team releases software differently, but everyone wants the release to be a success. So, regardless of how you release, how frequently you release, or how much you know about what you are releasing – we want your opinion! voke , the analyst firm focused on the edge of innovation, is conducting research on the topic of release management. We are looking for people exactly like you to share your opinion on software release management.  Please help out by letting us know what you think. The survey will take about 10 minutes to complete. Click here to share your story on release management. t

API Testing – Stop Waiting and Start Testing ASAP!

We have all heard that testers must keep pace with developers to deliver software faster. However, most testers continue to test at the UI level – which is constantly changing, so testers have to wait, and that impacts the ability to meet business demands for faster software releases. It becomes a cycle that testers have a hard time escaping. Testers want to be able to test earlier, reduce risk, and identify defects sooner – all to satisfy the customer. API testing is the perfect way to supplement traditional UI testing, keep pace with development, and deliver better quality at scale!  API testing can help you test earlier, faster, and more efficiently! And now, we have the data to show you the benefits of API testing including how much time is spent on UI testing alone, how much (or should I say little) time is spend on unit and API testing, and how much coverage is achieved.  We will be premiering the results of our recent survey on API testing in a webinar with Paraso
Your Next PC? The Personal Cloud, of Course Since the introduction of the personal computer, we all like to longingly think about what our next PC will have. Will it be lighter? Will it have better graphics? Will it be faster? And the biggest question of all, do we really need all of the latest and greatest features. All of these are questions we ponder when a new operating system is released, or when our current PC just decides to quit functioning (usually at the most inopportune of times). Well, what will your next PC be? No, it is not your next Personal Computer, it is your Personal Cloud! That’s right, the next PC you invest in may well be a Personal Cloud. The Apple iPad is just the beginning of this move from the Personal Computer to the Personal Cloud. With the iPad, Apple has hit a grand slam, scored a hattrick, a touchdown, or any other superlative sports metaphor you can conjure up. The iPad is the next step in the computing revolution. If you think Steve Jobs, the Roark of t