At the end of a design stage, a steering committee reviews technical feasibility, expected benefits and unresolved risks before allowing further investment. Which project selection and control mechanism is illustrated?

The scenario describes a formal review process that occurs at a specific point ("at the end of a design stage") in the project lifecycle. The purpose of this review is to assess the project's viability (technical feasibility, benefits, risks) and make a decision about continuing with further investment. This acts as a control point.

The key elements are:

• "users request significant changes after reviewing an early working version": This indicates a feedback loop and an adaptive approach to requirements.
• "The project team reprioritises the backlog": This is a core practice in agile methodologies, where a backlog of features and tasks is continuously managed and re-ordered based on feedback and changing priorities.
• "incorporates the changes into the next iteration": This signifies an iterative development process, where work is done in short cycles (iterations) and changes can be integrated frequently.

• a. Traditional predictive planning: This approach, often associated with the Waterfall model, emphasizes upfront, detailed planning and fixed requirements. Changes are typically managed through a formal change control process and are generally discouraged or costly once development is underway. The scenario's description of frequent changes, backlog reprioritization, and iterative integration is contrary to traditional predictive planning.

The described approach is characteristic of Agile or Iterative project management methodologies, which embrace change and continuous feedback. Since option 'a' is "Traditional predictive planning," it is incorrect. The correct answer would be an option related to agile or iterative development.

The correct option is not a. Traditional predictive planning. The approach being applied is an Agile or Iterative approach.