Voke releases Research Report on Agile Realities

In an interesting report former Voke has released a new report on Agile.

Among the findings:

  • Out of over 200 survey participants, we received only four detailed comments describing success with Agile.
  • Overwhelmingly, 40% of participants that use Agile did not identify a benefit.
  • Survey participants report that developers use the guise of Agile to avoid planning and to avoid creating documentation required for future maintenance.
  • Be aware that the Agile movement might very well just be either a developer rebellion against unwanted tasks and schedules or just an opportunity to sell Agile services including certification and training.
  • We received some unprecedented scathing and shocking comments about the level of competence, professionalism, and attitudes of some members of the Agile movement.


Sounds like what I’ve been saying over a decade now?


About postagilist

Architect, Manager, Developer, Musician, Post-Agile thought leader
This entry was posted in Uncategorized and tagged , , , , . Bookmark the permalink.

10 Responses to Voke releases Research Report on Agile Realities

  1. I think the report mis-represents Agile. Many (although I agree not all) organisations take a disciplined approach to Agile including continuous integration and testing, business value assessment and governance. Many organisations are getting significant benefits from Agile (http://blog.standishgroup.com/pmresearch). See also http://www.indigoblue.co.uk/blog/alternative-realities.

    • PostAgilist says:

      I don’t see anything in the links your posted to support your opinions in that area.

      However since you sell “Agile Services”, which is exactly what this report is demonstrating, that Agile is nothing but a platform for the monetization of placebo, it’s not surprising that you and the rest of the “industry” might disagree with it.


  2. Joe says:

    Every criticism of agile (or scrum or any methodology) is met with the accusation that Agile is being misrepresented. However, the contrary claims are contradictory and indicate that NOBODY knows what successful Agile actually is.

    My experience is even more fundamental than the criticisms outlined by PostAgilist; it is used by engineers and managers in order avoid responsibility. Agile quite deliberately makes all failures the fault of someone, or something, else. This is echoed by Agility apologists.

    I have never seen Agile succeed or come close to doing so. I’ve never spoken first hand with someone who has succeeded with Agile (they often say the word, but when quizzed, what they did was certainly not Agile by any stretch of the imagination save “sprints”, which rarely are.) All the success stories are third hand and highly anecdotal–they have all the hallmarks of urban legend.

  3. Interested Observer says:

    So, now that you’ve made it clear that waterfall is a myth, and Agile only exists to sell services, would you care to describe what you believe to be the “right way”?

  4. Pingback: New PM Articles for the Week of July 16 – 22 | The Practicing IT Project Manager

  5. asf says:

    That report makes it sound as if it was always developers who want to move to some full blown agile methodology.

    Management in our company wanted to move to full scrum and developers did not liked it. It basically amounted to weird combination of micromanagement and lack of management responsibility. No one was responsible to bigger than half day task and everybody talked into every small design decision (including people not having experience with given module and manager not doing coding last years). Every single small thing was questioned by somebody, but at the same time no one was responsible for the whole product.

    It took few months until people learned not to say anything that could be questioned during stand ups. They reported numbers of bugs that have been fixed and nothing else. Not much useful.

    We have never been done on time, mainly because unpleasant tasks have never been done. If you wanted to have them done on time, then you had to do them by yourself. But then you have found yourself doing only those unpleasant tasks, so volunteers gave up on them pretty soon.

    If was either write the documentation for the whole project or have the documentation unfinished. Well, I’m fine with writing documentation, I’m not fine with spending all my working time by writing documentation only. If I’m the only one writing the documentation, then the result is as if there would be none.

    • PostAgilist says:

      Thanks for sharing your experience.

      It sounds like mgmt imposed agile on the team, with less than stellar results.

      It seemed like you were building up to a point — is there one? I know many posters are not native english speakers and that is more than fine but I just want to make sure that we are understanding your point here.


Leave a Reply

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

WordPress.com Logo

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

Google photo

You are commenting using your Google 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 )

Connecting to %s