Try 10 focused APM PFQ questions on Project Life Cycles, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | APM PFQ |
| Topic area | Project Life Cycles |
| Blueprint weight | 7% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Project Life Cycles for APM PFQ. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 7% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Understand Project Life Cycles
What is the main purpose of using extended life-cycle thinking in a project?
Best answer: B
What this tests: Understand Project Life Cycles
Explanation: Extended life-cycle thinking is used to look beyond the point where outputs are delivered. Its purpose is to connect those outputs with the outcomes and benefits expected after implementation or use.
An extended project life cycle does not stop at delivery of the output. It also considers what happens before and after the main delivery work, especially how the output is adopted, used, and turned into outcomes or benefits. That matters because a project can deliver its product successfully but still fail to realise the expected value.
In PFQ terms, the core idea is to maintain sight of the full journey from output to benefit realisation. This helps organisations understand whether the project is contributing to the intended business or user improvement, rather than only finishing the deliverable.
The closest distractors describe other project management concepts, not the purpose of an extended life cycle.
Extended life-cycle thinking looks beyond delivery so the project can relate what it produces to the value realised afterwards.
Topic: Understand Project Life Cycles
A council project is delivering a new online permit system. The sponsor wants the life cycle to continue beyond handover so the team can confirm shorter processing times and fewer customer complaints. Which concept best fits this need?
Best answer: B
What this tests: Understand Project Life Cycles
Explanation: An extended life cycle is used when attention must continue after delivery of the output. It helps link what the project produces, such as a new system, to later outcomes or benefits, such as faster processing and fewer complaints.
The core idea is that delivery of an output is not always the end of the project view. Extended life-cycle thinking looks beyond handover to see whether the delivered output is actually being used and whether it leads to the intended outcomes or benefits. In this scenario, the online permit system is the output, while shorter processing times and fewer customer complaints are later results. That makes an extended life cycle the best fit.
A linear, iterative, or hybrid life cycle describes how work is structured during delivery, but none of those terms mainly focus on tracing the link from delivered output to realised benefits after handover.
An extended life cycle follows the project beyond delivery so outputs can be linked to operational outcomes and benefits.
Topic: Understand Project Life Cycles
A digital service project must pass fixed approval stages for funding and deployment. During delivery, the team develops and tests features in short repeated cycles. Which life-cycle approach does this describe?
Best answer: A
What this tests: Understand Project Life Cycles
Explanation: A hybrid life cycle combines elements of different life-cycle approaches in the same project. Here, the fixed approval stages are linear, while the repeated development cycles are iterative, so the project is using a hybrid approach.
A hybrid life cycle uses features from more than one life-cycle approach within a single project. In this scenario, the project has fixed approval points for funding and deployment, which are typical of a linear approach. At the same time, the team delivers work in short repeated cycles, which is typical of an iterative approach.
Because both approaches are being used together, the life cycle is hybrid. A purely linear life cycle would not use repeated cycles during delivery, and a purely iterative life cycle would not be defined mainly by fixed stage-by-stage approvals. An extended life cycle is a different idea and does not simply mean mixing approaches.
It combines linear stage approvals with iterative development cycles, which is the defining feature of a hybrid life cycle.
Topic: Understand Project Life Cycles
A project manager reviews these delivery descriptions:
Which option contains the descriptions that match iterative life-cycle logic?
Best answer: D
What this tests: Understand Project Life Cycles
Explanation: Iterative life cycles use repeated cycles of work, learning, and feedback to refine the solution over time. Descriptions involving fixed requirements, one-time phase progression, or full design approval before build are more typical of linear life-cycle logic.
The core distinction is whether delivery is planned as a single pass through phases or as repeated cycles that allow learning and refinement. Iterative life-cycle logic expects the solution to develop over time, with feedback from earlier work shaping later work. That matches the descriptions about repeated cycles and scope evolving as the team learns more.
By contrast, linear life-cycle logic usually fixes more detail earlier and moves through phases in sequence, such as defining requirements up front or completing design before build starts. A good quick test is to ask whether the project is expected to revisit and refine the work as delivery progresses. If yes, it is more likely iterative; if no, it is more likely linear.
These descriptions show repeated development with feedback and evolving scope, which are key features of an iterative life cycle.
Topic: Understand Project Life Cycles
Why is extended life-cycle thinking used in a project?
Which option contains the correct set of statements?
Best answer: C
What this tests: Understand Project Life Cycles
Explanation: Extended life-cycle thinking goes beyond delivery of outputs. It helps connect what the project produces to the outcomes and benefits that may appear later in use or operation.
An extended life cycle looks past the point where the project hands over its outputs. Its purpose is to maintain sight of how those outputs are intended to create outcomes in operational use and eventually contribute to benefits. This is useful because many benefits are not realized at the moment of delivery; they emerge later when the organisation adopts and uses the output.
It does not replace core governance documents such as the business case, and it is not limited to iterative work. The key idea is the link from output to outcome to benefit over time.
Extended life-cycle thinking links delivered outputs to later operational outcomes and benefits, including those realized after handover.
Topic: Understand Project Life Cycles
A team develops an early version of a new internal service, reviews feedback from users, refines the solution, and then repeats the same cycle several times. Which project life cycle approach does this describe?
Best answer: A
What this tests: Understand Project Life Cycles
Explanation: This describes an iterative life cycle because the work is repeated in cycles, with each cycle used to review and improve the developing solution. The key feature is refinement based on feedback rather than completing each phase only once.
An iterative life cycle is used when a solution is developed through repeated cycles. In each cycle, the team produces something, reviews it, learns from feedback, and refines the work before repeating the process. That matches the stem exactly: development, review, and refinement happen more than once.
A linear life cycle moves through phases in sequence with much less revisiting. A hybrid life cycle combines elements of different approaches, but the stem does not describe a mix. An extended project life cycle includes activity beyond core delivery, such as benefits realisation, rather than repeated refinement during delivery.
The key clue is the repeated loop of improving the solution.
It uses repeated cycles of development, review, and refinement to improve the solution over time.
Topic: Understand Project Life Cycles
A project team develops an early version of a new internal service, reviews feedback, and then repeats planning, development and review several times before final release. Which project life cycle does this describe?
Best answer: B
What this tests: Understand Project Life Cycles
Explanation: This describes an iterative life cycle because the work is done in repeated cycles, with feedback used to refine the next cycle. The key clue is the recurring pattern of plan, develop and review before final release.
An iterative life cycle develops the solution through repeated cycles instead of completing all work once in a fixed sequence. In the scenario, the team creates an early version, gathers feedback, and then repeats planning, development and review. That repeating loop is the main sign of iteration at PFQ level.
A linear life cycle usually progresses through phases mainly once and in order. A hybrid life cycle combines linear and iterative features, so there would need to be evidence of both approaches. An extended life cycle goes beyond project delivery into later use, operation or retirement. The key takeaway is that repeated refinement points to an iterative life cycle.
It uses repeated cycles of planning, developing and reviewing, rather than one pass through fixed phases.
Topic: Understand Project Life Cycles
A project uses overall linear planning and governance, but the product is developed in short iterative cycles. Which term best describes this life cycle?
Best answer: D
What this tests: Understand Project Life Cycles
Explanation: This is a hybrid life cycle because it mixes two approaches in one project. The planning and governance are linear, while the delivery work is iterative.
A hybrid life cycle is used when a project combines features from both linear and iterative approaches. In this question, the project has overall linear planning and governance, which suggests predefined stages or controls, but it also develops the product through short iterative cycles. That combination is the key sign of a hybrid life cycle.
A purely linear life cycle would mainly progress through sequential phases. A purely iterative life cycle would rely on repeated cycles throughout the work. An extended project life cycle is broader, covering activity before and after the core delivery life cycle rather than mixing linear and iterative delivery features.
The main clue is the deliberate use of both linear and iterative ways of working.
A hybrid life cycle combines linear planning or control features with iterative development features in the same project.
Topic: Understand Project Life Cycles
What is the main benefit of using an iterative life cycle rather than a linear life cycle?
Best answer: B
What this tests: Understand Project Life Cycles
Explanation: An iterative life cycle is used so the project can develop the output in repeated cycles and improve it using feedback. That contrasts with a linear life cycle, where phases are normally completed in sequence with much less repetition.
The key feature of an iterative life cycle is that work is repeated and refined over time. Feedback from earlier versions helps shape later versions, so the solution can evolve as understanding improves. In contrast, a linear life cycle usually progresses through phases in a set sequence, with each phase largely completed before the next begins.
This means the main benefit of an iterative life cycle is learning and improving through repeated feedback loops, not simply moving in order. The closest distractor describes a linear sequence, which is the opposite pattern.
An iterative life cycle allows work to be revisited and improved as feedback is gained during repeated cycles.
Topic: Understand Project Life Cycles
Which option states the phases of a typical linear project life cycle?
Best answer: C
What this tests: Understand Project Life Cycles
Explanation: A typical linear project life cycle in APM PFQ moves through concept, definition, development, and then handover and closure. The other options mix in activities or terms that are not the standard phase set.
A linear project life cycle is a sequence of distinct phases completed in order. At PFQ level, the typical phases are concept, definition, development, and handover and closure. These phases describe how the project moves from an initial idea, through clarification and delivery, to final transfer and close-out.
Options that include terms such as iteration, time boxing, risk response, or quality control are using project methods or management activities rather than life cycle phases. The key point is to recognise the named phase structure of a typical linear life cycle, not the tools or processes used within it.
A typical linear project life cycle progresses through concept, definition, development, then handover and closure.
Use the APM PFQ Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Use the full PM Mastery practice page above for the latest review links and practice route.