The project aimed to develop and launch a new mobile application for a tech startup, with a team consisting of developers, designers, testers, and business analysts. The project manager chose the traditional waterfall approach, which follows a sequential progression of project phases. However, the project manager encountered some issues as mentioned below:

1. Inflexibility and Limited Adaptability:

• Modifications to design and functional requirements led to delays and increased costs.
• The linear nature of the waterfall approach hindered easy incorporation of changes.

1. Lack of Stakeholder Collaboration:

• Limited stakeholder involvement until the testing phase.
• Lack of collaboration and understanding between the development team and stakeholders.
• Misalignment between stakeholder expectations and the final product.

1. Late Discovery of Defects:

• Testing conducted at the end of the development phase.
• Late detection of defects, making it difficult and costly to rectify them.
• Inadequate testing of functionalities due to time constraints, potentially compromising quality.

1. Limited Progress Visibility

• Lack of transparency and visibility into project progress.
• Difficulty in identifying and addressing bottlenecks or issues in a timely manner.

 

Briefly describe how Agile Project Management could bring a massive change to the business processes and resolve the major pitfalls of the waterfall approach