Project Management Process

Introduction

The purpose of the management process is to establish a clear strategy for achieving project objectives, with a well-defined scope, budget, and quality attributes.

 According to Agile methodology, it uses the time-boxed iterative model in order to achieve continuous delivery, which guarantees the delivery and builds a strong relationship with the customers.

There were many lifecycle models between agile, with pros and cons for each, which will be discussed in the following sections.

1. Waterfall Model

• Sequential & rigid.
  
  

• Phases: Requirements → Design → Implementation → Testing → Deployment → Maintenance.

• Drawback: No customer feedback till the end; high risk of failure if early assumptions are wrong.
  
  

2. V-Model (Verification & Validation)

• Extension of Waterfall with early test planning.

• Each dev phase has a corresponding test phase.

• Drawback: Same rigidity; assumes clear, fixed requirements.
  
  

3. Spiral Model

• Risk-driven & iterative.

• Combines design and prototyping in cycles ("spirals").

• Incrementally increase the scope vertically and horizontally, by adding new features, and accept enhancements on existing ones

• Drawback: Complex to manage; expensive for small projects.
  
  

4. Incremental Model

• Delivers in small functional pieces.

• Each increment adds features.

• Drawback: Requires good planning to avoid integration issues.

5. RAD (Rapid Application Development)

• Prototyping + user feedback.

• Emphasizes rapid delivery.

• Drawback: Poor scalability & documentation.