|
Such
a management model is referred to as “Waterfall
Model” since the Progress flows from the top (first phase)
to the bottom (last
phase), like a waterfall. This model has its origins in the
Construction sector
& Manufacturing Sector.
The
same management approach of
“Waterfall
Model” was subsequently adopted for Software sector also. But it was soon
realized that a different approach needs to be developed for management
of
software projects due to inherent differences in nature of
Construction/Manufacturing Projects vis-à-vis Software Projects.
Construction/Manufacturing
Projects vis-à-vis
Software Projects:
Events/activities/tools for
execution in a Traditional project
management are fairly
predictable. For example,
in a
construction project for a bridge, the Project Manager needs to
determine
requirements (functional/aesthetic/design/budget etc) , conduct
investigations/tests, design and plan,
execute the construction work of bridge & then close the work after
its
successful completion.
The
underlying
requirement for such
Traditional projects is that requirements have to be firmed up in
advance.
Because, once a particular phase has
been completed you can’t revisit the
phase. For example, having constructed the bridge piers you can
not now change the
foundations or the span arrangement. Naturally, the client has to
communicate
his firm requirements & the contractor has to accordingly plan,
design,
execute & deliver the project within the agreed budget & time
frame.
Software Projects are significantly
different
from Traditional Projects in many respects; a few of such difference are:-
- If
is often impossible to specify all the
requirements in advance.
- Activities/Tools/Processes involved
in
carrying out the project are not that
predictable. Quite often, iterative
method is required to be adopted.
- You
may be required to revisit the phase
that
you have already completed.
- Such
projects are more sensitive to
technological changes/developments. May be, you are required to
introduce a new
feature midway in your project to keep pace with your
competitor who has just launched a
product with that feature.
- You
may require more
interaction/discussions
with your client to understand their requirements.
Thus
there was a need to adopt a
different
management model for Software Projects which would be more dynamic,
interactive, flexible, adaptive throughout the lifecycle of project
&
collaborative. Concept of
Agile Project Management evolved to cater for these
requirements.
|
