According to the PMBOK Guide, an agile approach is based on delivering value in small increments and iterations, rather than in one large deliverable at the end of the project1. This allows the project team to incorporate feedback, changes, and learning into the product or service, and to reduce rework and dissatisfaction2. Therefore, the project manager should adopt an incremental cycle of delivering value to the customer, and align the project objectives and scope with the customer needs and expectations. The other options are incorrect because:
A. Decreasing the scope of the portfolio and sending new solutions to the customer is not an agile strategy, but a reactive one. It may imply that the project team is not able to deliver the agreed scope, or that they are not collaborating with the customer to understand their requirements and preferences.
B. Delivering a schedule with the portfolio timeline and delivery to the customer is not an agile strategy, but a predictive one. It may imply that the project team is following a rigid and fixed plan, rather than responding to changes and uncertainties in the project environment.
D. Preparing deliveries with more details to satisfy the customer is not an agile strategy, but a waterfall one. It may imply that the project team is focusing on documentation and specifications, rather than on working products and solutions. References:
1: PMBOK Guide, 6th edition, Chapter 1, Section 1.2.3, page 7
2: PMBOK Guide, 6th edition, Chapter 3, Section 3.8, page 52
: Agile Practice Guide, Chapter 2, Section 2.1.1, page 13
: Agile Practice Guide, Chapter 2, Section 2.2, page 14
