PMP Practice Questions #73
You are the project manager for a software development project, currently in the process of sequencing activities. Given the complex nature of the project, there are several dependencies you must consider. In the context of this project, you need to correctly identify whether a dependency is mandatory or discretionary.
Which of the following scenarios best exemplifies a discretionary dependency?
A. Coding Completion Before Integration Testing: The plan is to start integration testing after the completion of all coding activities.
B. Finalizing the Contract with a Vendor Before Starting Work: The project schedule includes finalizing the vendor contract before commencing any related work
C. Compliance Audit Before Product Launch: The product launch is contingent on completing a compliance audit to meet regulatory standards.
D. Client Approval of Prototype Before Full-Scale Development: The team has set a policy to wait for explicit client approval on the prototype before proceeding to full-scale development.
Analysis:
In this software development project, as the project manager, you are tasked with sequencing activities and determining the nature of dependencies, specifically identifying if they are mandatory or discretionary. Understanding the difference between these two types of dependencies is crucial for accurate scheduling and effective project management.
Analysis of Options:
Option A: Coding Completion Before Integration Testing: The plan is to start integration testing after the completion of all coding activities. This option involves starting integration testing only after all coding activities are complete. Typically, integration testing depends on the completion of coding; thus, this appears to be a mandatory dependency, as the testing cannot proceed without the coding being finalized.
Option B: Finalizing the Contract with a Vendor Before Starting Work: The project schedule includes finalizing the vendor contract before commencing any related work. Finalizing a vendor contract before commencing any related work generally reflects a mandatory dependency. Contracts often outline the scope, terms, and conditions of work, making it essential to finalize them before any work begins to ensure clarity and compliance.
Option C: Compliance Audit Before Product Launch: The product launch is contingent on completing a compliance audit to meet regulatory standards. Conducting a compliance audit before the product launch, especially to meet regulatory standards, is typically a mandatory dependency. Regulatory compliance is often a legal requirement, making the audit an essential prerequisite for product launch.
Option D: Client Approval of Prototype Before Full-Scale Development: The team has set a policy to wait for explicit client approval on the prototype before proceeding to full-scale development. Waiting for client approval on the prototype before proceeding to full-scale development is identified as a policy set by the team. While it is a prudent practice, it is not driven by technical, contractual, or regulatory requirements. Therefore, this scenario best exemplifies a discretionary dependency. The decision to wait for approval is based on team policy rather than an inherent necessity of the project’s workflow.
Conclusion: Among the given scenarios, Option D (Client Approval of Prototype Before Full-Scale Development) is the best example of a discretionary dependency. This dependency is based on a team policy rather than a technical, legal, or contractual requirement, making it a choice rather than a necessity. The other options represent mandatory dependencies, where the subsequent activity cannot begin without completing the prior one due to inherent project requirements or external constraints. Identifying discretionary dependencies is crucial for project managers to understand where flexibility exists in the project schedule and where it does not.
PMP Exam Content Outline Mapping
| Domain | Task |
|---|---|
| Process | Task 6: Plan and manage schedule |
Topics Covered
- Predictive Scheduling
- Dependency Management
