​​Software Project Failure – The below mentioned project failure is retrieved from the following websites – - http://www.computerweekly.com/news/2240058411/Sainsburys-writes-off-260m-as-supply-chain-IT-trouble-hits-profit - http://www.computerworld.com/article/2533563/it-project- management/it-s-biggest-project-failures----and-what-we-can-learn-from-them.html?page=3 - https://prezi.com/yxxfdjfdimlb/sainsburys-warehouse-automation-project-failure-2003-2005/ The name of the project was Sainsbury's warehouse automation launched by Sainsbury's CEO Peter Davis in year 2000. The primary motivation behind the undertaking was to completely mechanized Sainsbury's 4 principles vast stations for its store network administration, and in addition fabricating the EPOS (Electronic Point of Sale) framework. These improvements were for the most part base on Accenture's 10-year outsourcing bargain. Notwithstanding, enormous speculation of Sainsbury's didn't give back the comparing impact, considerably all the more, all the cash that Sainsbury's had contributed all came to nothing. The objectives of the project were – Build productivity and streamline operations in warehousing Enhance a standardized barcode based satisfaction framework Overhaul the principle outline based warehouse management system Build the adaptability of the system To gain the advantage over its competitors as efficiently and cost effectively as possible In July 2004 , The CEO of Sainsbury's stands down because of company's keep going poor performance. Lagging behind in implementation, therefore new systems were launched with many complications . In 2005 company claimed that the system is working as expected even though system was not functioning well .Two years later , Sainsbury declared the project was a failure resulting in total loss of more than £526m. The two main reasons for the project failure are – 1) Lack of Contingency planning Shifted to manual warehouse managing process Hired Around 3000 additional employees to manage 2) Going for the big bang approach without proper assurance about the system Rather than a regulated methodology, Sainsbury went for a kind of huge explosion and discovered that it was more awful off than before it presented the new framework The Waterfall Model – Part A The waterfall model is an exact and progressive approach to manage make Programming. It is also called as immediate progressive model as it completes a routine cycle in programming headway sorted in various stages which take after sequentially. The Waterfall model has following stages – 1) Requirement Analysis – Every single conceivable necessity of the framework to be created are captured in this stage and archived in a prerequisite determination doc. 2) System Design - The prerequisite particulars from first stage are examined in this stage and framework outline is prepared. Framework Design helps in determining equipment and framework necessities furthermore helps in characterizing general framework engineering. 3) Implementation- Consequent to accepting the framework plan reports, the work is shared into different modules and the genuine coding is initiated. The framework is produced into little coding units. These units are later coordinated in the ensuing stage. Each unit is tested for its usefulness. 4) Testing - The modules that are isolated into units are incorporated into a complete framework and tried for legitimate coordination among modules and framework acts according to the particulars. Once the testing is finished, the product item is conveyed to the client. 5) Deployment - Once the practical and non useful testing is done, the item is conveyed in the client environment or discharged into the business sector 6) Maintenance – After the system is running in the environment, problems can come up . The issues that are identified with the system are illuminated simply after arrangement of the system. The issues emerge every once in a while and should be tackled; subsequently this stage is alluded as maintenance. Part B Advantages of the Waterfall Model • It takes into consideration departmentalization and administrative control. • Simple and straightforward to use. • Easy to oversee because of the unbending nature of the model – every stage has particular deliverables and an audit procedure. • Phases are handled and finished each one in turn. • Works well for littler activities where necessities are exceptionally surely knew. • A timetable can be set with due dates for every phase of advancement and an item can continue through the improvement procedure This model is used only when the requirements are very well known, clear and fixed, this model can only be applied to short projects where there are no ambiguous requirements, , for instance it can be used for payroll computing management Part C Main Problems associated with the waterfall method are – • It doesn't take into account much reflection or modification. • Once an application is in the testing stage, it is extremely hard to backpedal and change something that was not well thoroughly considered in the idea stage. • No working programming is delivered until late during the life cycle. • High measures of danger and vulnerability. • Not a decent model for complex and article arranged ventures. • Poor model for long and progressing ventures. • Not appropriate for the projects where prerequisites are at a moderate to high danger of evolving. As there is no going back after the error has been identified later during the development of the software, therefore it id very difficult to handle big software projects. Part D Agile Methods Part A The incremental build model is a technique for programming advancement where the model is composed, actualized and tried incrementally (somewhat more is included every time) until the item is done. It includes both improvement and support. The item is characterized as completed when it fulfills the greater part of its requirements. This model joins the components of the waterfall model with the iterative logic of prototyping. (Source: Amir Gharai ,2008) Advantages of Incremental Delivery – • Generates working software quickly and early during the software life cycle. • This model is more flexible – less costly to change scope and requirements. • It is easier to test and debug during a smaller iteration. • In this model customer can respond to each built. • Lowers initial delivery cost. • Easier to manage risk because risky pieces are identified and handled during it'd iteration. Part B Why test first development helps the programmer to develop a better understanding of the requirements.