How the inheritance between requirements, tasks, and deliverables works.

You are managing a project based on a Waterfall model. You define a project and a project plan in Oracle Project Portfolio Management with tasks and subtasks applicable to each of the phases of the project: Initiation, Discovery, Design, Build, Test, and Deploy. As a project manager, you want to define deliverables for your project requirements that are elucidated during the Discovery phase of your project. You now want to understand how the inheritance between requirements, tasks, and deliverables works.
Identify the two correct statements in this respect.
A. A deliverable associated with a requirement is not automatically associated with the tasks created for that requirement.
B. You associate a deliverable with a task independent of associating a requirement with a task.
C. The association of a deliverable with a task is dependent on associating a requirement with a task.
D. A deliverable associated with a requirement is automatically associated with the tasks created for that requirement.

Download Printable PDF. VALID exam to help you PASS.

One thought on “How the inheritance between requirements, tasks, and deliverables works.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.