The Top 5 Deterents to Agile

The beauty of Agile is the fact that its just about a few principles. – which we also summarized in a few words. Everything else is under your control. And on your way from classic waterfall practices to adopting those principles, you are likely to encounter some serious blockers. I’m attempting to list out the top 5 along with the Agile principles that they block.

1. Large teams

Blocks: Velocity, Working together

Scales of Agile (Courtesy: ebizq.net)
Scales of Agile (Courtesy: ebizq.net)

It is uncommon to have a cross-functional team of teams with 30-50 folks working on the same product. While the Agile deliverable is a few days of work, large teams working on a single release will generate a huge deliverable that is more coupled, has wider impact and demands extensive testing.

2. Fixed-scope planning

Blocks: Working software, Simplicity, Accepting change

Courtesy: 352inc.com

Teams that have a fixed-scope mental block start off by committing a scope for the next release, and then estimate a future release date. Since estimates are often incorrect, the release is delayed to deliver the committed scope – which is just not Agile. Forget about changing requirements, folks won’t even drop a few stories or acceptance criteria at the very end, to meet the committed date (time-box) – at the cost of breaking the promise of a few features. Even worse, that you won’t see anything working until the release is out.

3. Test-automation

Blocks: Environment, Customer Satisfaction

Courtesy: testdroid.com
Courtesy: testdroid.com

I don’t think this point needs any elaboration. Haven’t we all been part of releases where the QA effort exceeds Development just because a feature touches multiple modules? Dependency highlighting tools can help, but a comprehensive test suite (first for the services, then for the UI) can really speed up releases.

4. Team maturity, mindset & leader’s trust

Blocks: Motivated individuals, Self-organization, Reflection

Agile is a lot about the mindset. It demands a mature, responsible team that can be trusted to self-organize. The organization also needs to trust the team and in return provide an environment conducive to learning & improvising all the time. If the SCRUM Reflection ceremony turns in to a court marshal,  folks are never going to be motivated to work, let alone achieve excellence.

5. Tools

Blocks: Excellence

Courtesy: hubspot.net
Courtesy: hubspot.net

This is truly debatable. I’ve contested, but could not convince. Everyone agrees that you can’t manage user stories in a TXT file, code through versioned folders, or test manually. Yet, we fail to accept the importance of tools to being Agile. I do not have preference for any, but I feel there has to be some lean Agile stack that lets smaller teams easily fork & merge code, mark acceptance criteria done (than whole stories) and validate a build in seconds.

Open for discussion.

6 thoughts on “The Top 5 Deterents to Agile”

  1. Pingback: Quora
  2. Pingback: Quora
  3. Pingback: Quora
  4. Pingback: Quora
  5. I would agree you probably need some version management tool and automated test suite (looks as much a basic tools than a compiler or a makefile)… But what’s wrong with TXT file and why do you say you can’t use it to store user stories ? OK, I would probably prefer a handful of postits sticked on the wall, but if no wall where available TXT file would certainly do. It’s even easy to put on the repository and share and synchronize it with the team. It’s also easy to parse and can easily be used to draw burndown charts or compute velocity if we want to. Certainly much much better than say a Word Processor document.

    On the other hand some Web Based tools may be too much to manage stories and be as much of a hindrance than a help (problems we can have with sophisticated ticket management software is that we can easily accumulate things in it: obsolete User Stories should be dropped, not doing it is a problem).

    1. Thanks for sharing your thoughts Chris.
      US in TXT was just a metaphor for a workable, vanilla tool (in contrast to the nirvana software)
      Since you brought it up, we use formatting, color-highlighting, inline wire frames & sometimes comments to red-line complex stories and would really miss this in TXT – unless everyone learned mark-down syntax

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.