10 Good Reasons To Do Agile Development

10 Good Reasons To Do Agile
Development
by Kelly Waters, 11 June 2007 | Agile Adoption, Agile Project Management
Here are 10 good reasons to apply agile development principles and practices…
1. Revenue
The iterative nature of agile development means features are delivered incrementally,
enabling some benefits to be realized early as the product continues to develop.
2. Speed-to-market
Research suggests about 80% of all market leaders were first to market. As well as the
higher revenue from incremental delivery, agile development philosophy also supports
the notion of early and regular releases, and ‘perpetual beta’.
3. Quality
A key principle of agile development is that testing is integrated throughout the lifecycle,
enabling regular inspection of the working product as it develops. This allows the
product owner to make adjustments if necessary and gives the product team early sight
of any quality issues.
4. Visibility
Agile development principles encourage active ‘user’ involvement throughout the
product’s development and a very cooperative collaborative approach. This provides
excellent visibility for key stakeholders, both of the project’s progress and of the product
itself, which in turn helps to ensure that expectations are effectively managed.
5. Risk Management
Small incremental releases made visible to the product owner and product team through
its development help to identify any issues early and make it easier to respond to
change. The clear visibility in agile development helps to ensure that any necessary
decisions can be taken at the earliest possible opportunity, while there’s still time to
make a material difference to the outcome.
6. Flexibility / Agility
In traditional development projects, we write a big spec up-front and then tell business
owners how expensive it is to change anything, particularly as the project goes on. In
fear of scope creep and a never-ending project, we resist changes and put people
through a change control committee to keep them to the essential minimum. Agile
development principles are different. In agile development, change is accepted. In fact,
it’s expected. Because the one thing that’s certain in life is change. Instead
the timescale is fixed and requirements emerge and evolve as the product is developed.
Of course for this to work, it’s imperative to have an actively involved stakeholder who
understands this concept and makes the necessary trade-off decisions, trading existing
scope for new.
7. Cost Control
The above approach of fixed timescales and evolving requirements enables a fixed
budget. The scope of the product and its features are variable, rather than the cost.
8. Business Engagement/Customer Satisfaction

The active involvement of a user representative and/or product owner, the high
visibility of the product and progress, and the flexibility to change when change is
needed, create much better business engagement and customer satisfaction. This is an
important benefit that can create much more positive and enduring working
relationships.
9. Right Product
Above all other points, the ability for agile development requirements to emerge and
evolve, and the ability to embrace change (with the appropriate trade-offs), the team
build the right product. It’s all too common in more traditional projects to deliver a
“successful” project in IT terms and find that the product is not what was expected,
needed or hoped for. In agile development, the emphasis is absolutely on building the
right product.
10. More Enjoyable!

The active involvement, cooperation and collaboration make agile development teams a
much more enjoyable place for most people. Instead of big specs, we discuss
requirements in workshops. Instead of lengthy status reports, we collaborate around a
task-board discussing progress. Instead of long project plans and change management
committees, we discuss what’s right for the product and project and the team is
empowered to make decisions. In my experience this makes it a much more rewarding
approach for everyone. In turn this helps to create highly motivated, high performance
teams that are highly cooperative.
Implications of embracing agile development principles

But there are implications. There’s no such thing as a free lunch! And there’s no magic
bullet for software development. Sorry, no, you can’t just drink the cool aid :-) In
exchange for all these benefits, you do get less predictability, software and humans are
still difficult, you can’t blame someone else if things don’t go right, and it generally
requires much more commitment and effort from everyone involved – i.e. teamwork is
even more important.
Nevertheless, the advantages of agile development are really compelling.
Kelly.
- See more at: http://www.allaboutagile.com/10-good-reasons-to-do-agile-
development/#sthash.zJ1NjLl0.dpuf

10 Good Reasons To Do Agile Development

Uploaded by

Copyright:

Available Formats

10 Good Reasons To Do Agile Development

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10 Good Reasons To Do Agile Development

Uploaded by

Copyright:

Available Formats

10 Good Reasons To Do Agile

8. Business Engagement/Customer Satisfaction

10. More Enjoyable!

Implications of embracing agile development principles

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.