Which statement best reflects how phases in a project relate to each other?

Which statement best reflects how phases in a project relate to each other?

• A. Phases are completed strictly sequentially with no overlap.
• B. Phases are divisions within a project where extra control is needed to effectively manage the completion of a major deliverable, and can overlap.
• C. Phases are random groupings with no relation.
• D. There is a single phase that covers all tasks.

Answer: (B)

Phases are chunks of a project organized around delivering a major outcome, and they aren’t rigidly separate; they need extra control to ensure that the key deliverable is completed to a defined standard. Because this deliverable often spans multiple activities, the work in different phases can overlap. Overlap allows parts of the project to proceed in parallel, enabling early testing, integration, and adjustment as work progresses, which helps manage risk and improve quality. For example, in a product development effort, design work may continue while some development tasks begin on earlier features, and testing can start on components before all design work is fully complete. This kind of overlap reflects how real projects move forward: you coordinate, monitor, and adjust across phases to ensure the major deliverable comes together smoothly. The other ideas aren’t as accurate because they suggest phases are strictly sequential with no overlap, are random groupings, or that a single phase handles everything. In practice, phases are structured around deliverables and are often interdependent, requiring ongoing oversight and coordination across them.

Phases are chunks of a project organized around delivering a major outcome, and they aren’t rigidly separate; they need extra control to ensure that the key deliverable is completed to a defined standard. Because this deliverable often spans multiple activities, the work in different phases can overlap. Overlap allows parts of the project to proceed in parallel, enabling early testing, integration, and adjustment as work progresses, which helps manage risk and improve quality.

For example, in a product development effort, design work may continue while some development tasks begin on earlier features, and testing can start on components before all design work is fully complete. This kind of overlap reflects how real projects move forward: you coordinate, monitor, and adjust across phases to ensure the major deliverable comes together smoothly.

The other ideas aren’t as accurate because they suggest phases are strictly sequential with no overlap, are random groupings, or that a single phase handles everything. In practice, phases are structured around deliverables and are often interdependent, requiring ongoing oversight and coordination across them.