Waterfall Project Management Case Study

1 Comparison of the waterfall and agile approach and its impact on the project success Traditional waterfall project management has been used for many years. However, the projects which are based on waterfall methodologies often face a dilemma of time delay or over budget. As a result, stakeholders are often disappointed about the fact that the time delay, in one way or another, will affect their benefits. To make matters worse, in some cases, the quality of the project will deteriorate because the team follows an ineffective waterfall process. For example, the customer says that they want you to build the software ‘KAILE’, but when the project has almost been completed and the team has already started to set the plan for their holidays,

Firstly, the Adobe system, an agile building tool, was introduced to the company in 2012. The new tool could help the team to add new modules on the already existing software without the compromising its function, which is shown in Figure 3, and more importantly, the team did not need to start the process from the beginning as they normally had done in the past ten years. Figure 3. The new agile building tool (Casey and Matt M 2013).

Secondly, a hybrid team was created to work in the same place. This facilitated the communication between team members from two different teams---development team and marketing team, and helped them save a lot of time compared with using e-mails to communicate with each other. As a result, a 300% increase had been seen in productivity. More importantly, it allowed the company to spend more time on setting the strategy for the future, and communicating with their customers (Casey and Matt M 2013).

The success of this case is mainly because the company has recognized that delivering working software to their customers by using the agile approach is the key to keep them thriving in the future industry, and this can be achieved by working together and collaborating with their