Question 1
Choose 1
A consultant is implementing a Manufacturing Cloud. After the consultant concludes the discovery phase, the
customer identifies additional must-have features for the platform. Which recommendation should the
consultant make regarding these additional features?
Correct answer:
C. Create a change request and arbitrate based on other features.
Explanation
After the discovery phase, if the customer identifies additional must-have features that were not included in the original requirements, the consultant should not simply add them directly to the project scope. The appropriate approach is to create a formal change request and evaluate the new requirement against the existing scope, priorities, timeline, resources, and impact on other features. This allows the project team and customer to make a controlled decision about whether the additional feature should be included.
Why Option A Is Incorrect
A. Remove another feature from the list of requirements to account for the additional workload.
The consultant should not automatically remove an existing requirement. Each requirement should be evaluated through the change-management process before any scope or priority is changed.
Why Option B Is Incorrect
B. Add the feature in the project scope.
Adding a new feature directly to the scope without evaluating its impact can cause scope creep and affect the project's timeline, resources, and budget. A formal change request should be created first.
Why Option C Is Correct
C. Create a change request and arbitrate based on other features.
A change request provides a structured way to assess the additional feature against existing requirements. The consultant can then work with the customer and project stakeholders to prioritize the requirement and determine whether another feature needs to be deferred or removed.
Key Exam Point
When new requirements are identified after discovery, use the change-management process rather than adding them directly to scope. Create a change request and evaluate the new requirement against existing priorities and project constraints.
After the discovery phase, if the customer identifies additional must-have features that were not included in the original requirements, the consultant should not simply add them directly to the project scope. The appropriate approach is to create a formal change request and evaluate the new requirement against the existing scope, priorities, timeline, resources, and impact on other features. This allows the project team and customer to make a controlled decision about whether the additional feature should be included.
Why Option A Is Incorrect
A. Remove another feature from the list of requirements to account for the additional workload.
The consultant should not automatically remove an existing requirement. Each requirement should be evaluated through the change-management process before any scope or priority is changed.
Why Option B Is Incorrect
B. Add the feature in the project scope.
Adding a new feature directly to the scope without evaluating its impact can cause scope creep and affect the project's timeline, resources, and budget. A formal change request should be created first.
Why Option C Is Correct
C. Create a change request and arbitrate based on other features.
A change request provides a structured way to assess the additional feature against existing requirements. The consultant can then work with the customer and project stakeholders to prioritize the requirement and determine whether another feature needs to be deferred or removed.
Key Exam Point
When new requirements are identified after discovery, use the change-management process rather than adding them directly to scope. Create a change request and evaluate the new requirement against existing priorities and project constraints.