A hybrid project approach blends predictive and adaptive methods, using structured planning alongside iterative delivery. It plans what can be planned and leaves room to adapt to changing requirements through iterations and feedback loops. This lets stakeholders see forecasts and still respond to real-world changes. For instance, you might detail the overall project schedule and budget, but run development in short sprints with regular reviews. That blend captures how hybrid works. The options that propose only predictive methods, reject change, or are identical to a predictive approach don’t reflect this combination.

The main idea behind a work breakdown structure is to map the project by turning the total scope into a structured set of deliverables. It represents the final product and all its components broken down into smaller, more manageable pieces. Each level adds detail, ending with work packages that can be clearly estimated, assigned, and tracked. Because it focuses on what will be produced rather than when or how it will be done, a WBS ensures nothing essential is left out and that every deliverable and sub-deliverable is accounted for. So, the WBS should capture all deliverables and their sub-deliverables, forming a hierarchy that defines the scope in terms of outcomes, not activities. This clarity makes planning, budgeting, and assignment straightforward, and it provides a stable basis for further planning like scheduling and resource allocation. A schedule chart, risks list, and a stakeholder communications plan serve different purposes: the schedule shows timing and milestones; the risks list identifies uncertainties and mitigation steps; the communications plan outlines who needs what information and how.

In project management, the formal acceptance of completed deliverables comes from the person who will use or receive the product—the customer or their designated representative. They define the acceptance criteria and decide whether a deliverable meets them, then sign off if it does. The project manager coordinates this verification, ensuring the deliverable is ready for acceptance, but does not unilaterally decide acceptance. Internal managers may check compliance with standards, but they aren’t the final sign-off authority for customer-delivered work. The project sponsor, while a key governance role responsible for funding and benefits, typically does not have the final say on each individual deliverable’s acceptance. Therefore, the one who does not have final authority on verifying deliverables is the project sponsor.

A risk register is a living document that captures identified risks along with who owns them, their characteristics (such as probability and impact), and the planned responses. It is kept up to date throughout the project so the team can monitor risk exposure, assign accountability, and adjust mitigation or contingency plans as conditions change. This centralized tool supports proactive decision-making and helps allocate resources to address risks before they materialize, keeping stakeholders informed about what could affect the project and how those risks are being managed. It isn’t a static list, nor is it simply a budget sheet. It isn’t a template for resolving issues or a log of stakeholder communications. Those other artifacts serve different purposes, while the risk register specifically focuses on identifying, owning, and responding to risks to keep the project on track.