BYRITIKA RATTAN (Roll No. 16) NAVNEET KAUR (Roll No.
FAILURES IN IT PROJECTS
Definition Waterfall model layout Features of waterfall model Advantages of waterfall model Disadvantages of waterfall model
IT failure stats California DMV project Reasons for failure of DMV project Other examples Lessons learnt from failures
Analysis. Testing and Maintenance. Construction. Initiation.
. often used in software development process.The WATERFALL MODEL is a sequential design process. in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception. Design.
It can be implemented for any size project. Every stage has to be done separately at the right time so you cannot jump stages. Documentation is produced at every stage of a waterfall model allowing people to understand what has been done.
. Testing is done at every stage.y y y y y
The waterfall model is so named because it employees a 'top down' approach A waterfall model is easy to follow.
As everything is documented a new team member can easily understand what's to be done. Implementers have to follow the design accurately
.A waterfall model helps find problems earlier on which can cost a business less than if it was found later on. Requirements will be set and these wouldn't be changed.
Many believe it is impossible to make one stage of the projects life cycle perfect. Difficult to estimate time and cost for each stage of the development process.
. Constant testing of the design is needed.If requirements may change the Waterfall model may not work.
62% of organizations experienced IT projects that failed to meet their schedules 49% suffered from budget overruns 47% had higher-thanexpected maintenance costs 41% failed to deliver the expected business value and ROI
the project was cancelled
.In 1987. Objective: strategically position the DMV data processing environment to rapidly respond to change By 1993. after spending $45 mn. the California Department of Motor Vehicle (DMV) Revitalize their drivers license and registration process.
According to DMV special report.." No monetary payback Not supported by executive management No user involvement Poor planning Poor design infrastructure Unclear objectives No support from information management staff
... but the DMV technical community was never truly confident in its viability.The phasing was changed several times.
Organization/ Country Or go DM
Cost overrun 14
o a tomat man al an a er ase ork License A lication Mitigation Project (LAMP) a rus a erless share settlement system
Lon on Stock Exchange
Each major software must be investigated. reported and shared Success Potential chart should be used by IT managers Smaller time frames Each software component should have clear and precise statement and set of objectives Make projects simpler