The project manager should use an iterative approach for both the requirements analysis and delivery phases of the project. An iterative approach involves breaking down the project scope into smaller increments and delivering them in cycles, with feedback and validation from the client at each cycle. This approach is suitable for projects with clear requirements, but also allows for flexibility and adaptation to changing needs and expectations. The client's request to see a demo of the work completed every two weeks indicates that they value frequent and incremental delivery of value, which is consistent with an iterative approach. Agile is not the best option for this project, as agile is more suitable for projects with high uncertainty and complexity, where the requirements are not clear or stable, and the client is actively involved in the project collaboration.
Predictive is not the best option for this project, as predictive is more suitable for projects with low uncertainty and complexity, where the requirements are well-defined and fixed, and the client is not interested in frequent changes or feedback. References:
* A Guide to the Project Management Body of Knowledge (PMBOKGuide) - Seventh Edition, Chapter
2: Value Delivery System, Section 2.2: Project Delivery Approaches, Section 2.3: Project Life Cycle
* Agile Practice Guide, Chapter 2: Life Cycle Selection, Section 2.1: Introduction, Section 2.2:
Implementing Agile: Creating an Agile Environment
* Professional in Business Analysis (PMI-PBA)Handbook, Section 2.3: Domains and Tasks, Domain 2:
* Planning, Task 1: Plan Business Analysis Approach
* Professional in Business Analysis (PMI-PBA)Examination Content Outline, Domain 2: Planning, Task 1: Plan Business Analysis Approach