The Next Big Thing
Posts about next generation technologies and their effect on business.

Agile development - is it right for you?

Barrier break through.pngThe other day I was talking with a team about Agile development adoption. One of the things they asked was “What’s different?” and "Is it right for us?" I sat down and jotted this list of thoughts that came to mind. No, my response isn’t the purist perspective covering all the elements of the agile manifesto, but some might find it useful:

 

Agile focus:

  • Small cycles with fast turnaround - iterative releases w/improved time to value

  • High-level of interaction with the end user/owner

  • Progress centric, where business value is measured by tested, demonstrable deliverables

  • Transparency

  • Fail early/fail often – “defects” are an opportunity for a future release

  • Priority focused, with quicker realization of business value

It requires:

  • Direct access by the agile team to business users

  • Executive sponsorship, support and expectations

  • Customer commitment/involvement – if the customer isn’t there, the work can’t get done.

  • Automated testing (you’ll be testing more often so plan to automate)

  • Projects started with the awareness and assumption that you don’t know everything about the end result

  • Define areas that cannot be compromised (e.g., security) that need to be baked in along the way

  • Agile readiness assessment before each new effort – all parties need to be ready

  • Organizational change management (there is behavior change of individuals, leaders, relationships)

  • Priority-driven development

What remains the same:

  • Scope (scope will change, but if it changes too much, it becomes a new project/sprint)

  • Requirements (still need to be documented and tested) although they are not there at the start

  • Leadership and project owners (they accept or reject results)

  • Amount of potential work to be done (there is always going to be more to do, focus on value)

  • Budgets – projects still need to live within financial constraints

  • Performance measurement (what and how you measure will be different).

  • Documentation (the documentation is richer, since it should be completed all along the way).

  • Architecture (everything still needs to work together)

  • Change control (prepare for continous change)

What needs to change:

  • Incentives, compensation for the members

  • Governance processes and approaches to release and acceptance

  • Interfaces to other groups (they need to be more flexible)

  • Coaches and agile experience (for the ‘customer’ as well as the developers)

  • Continuous engagement level of business users

  • A view to develop and implement what is needed, nothing more

Although Agile has been around for well over a decade, a solid foundation for discussion still needs to be agreed upon.

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the community guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation