Agile Zone is brought to you in partnership with:

Julian has a proven track record in enhancing the software development capability of large and complex IT organisations. He is a regular speaker at industry conferences and travels globally to support his clients by providing training, mentoring and change management services. Most recently Julian has been working to expand the use of Agile practices within large and complex, public and private organisations, specifically in the promotion and adoption Disciplined Agile Delivery. Julian is a DZone MVB and is not an employee of DZone and has posted 6 posts at DZone. You can read more from them at their website. View Full User Profile

'Just do it' vs. Agile

05.27.2010
| 2481 views |
  • submit to reddit

There are many misconceptions in the software industry about Agile development, and a typical example became a hot topic of discussion for one of my client's project teams this week.
One member of the team suggested that "Just do it", or JFDI as it's sometimes called, is an appropriate mantra for Agile principles.
I immediately disagreed...

Whenever I have heard any manager address a project team and tell them to "Just do it", I know that it's unlikely to be a successful endeavour, and it almost certainly won't be Agile.

When said by the manager, "Just do it" typically means:
- the team is told the scope of what they must deliver and by when
- the manager is not working with, or listening to, the team
- the team is given a detailed and overly-optimistic plan
- the customer is not engaged with the team
- the team members work in isolation to only deliver their tasks
- and the manager measures daily progress by the effort spent

This is obviously going to result in some bad team behaviours and poor results where:
- the team abandons a disciplined approach and starts hacking
- the team no longer takes ownership for the solution
- the team's morale is lost and productivity drops
- reduced collaboration results in poor communication
- individuals blindly follow a given plan
- and the manager is surprised at the end of the planning period when the "team" fails

So please, don't encourage your software project teams, or let yourself be told, to "Just do it".
Get smart and "get" Agile.

Julian Holmes

UPMentors.com
References
Published at DZone with permission of Julian Holmes, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Tags:

Comments

Reid Atherton replied on Thu, 2010/05/27 - 1:54pm

Totally agree with you! "Agile" doesn't mean to stop doing analysis. Avoiding the "big design up front" doesn't mean to throw maintainability concerns to the winds. Frequent releases of working code doesn't mean guessing what the need is and then throwing your guesses over the wall repeatedly.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.