The CTO at Universal Containers is complaining to the software development managers that he has...

The correct selection is C, D. Scrum improves visibility through its value of openness, while Kanban explicitly visualizes work items and workflow states. Both directly address team-work status transparency; runtime DevOps monitoring is useful but does not substitute for visible development work management in this scenario. From a planning perspective, the architect must reduce uncertainty before execution by defining ownership, governance, environment purpose, prioritization, and measurable acceptance criteria. Decisions should be repeatable and visible across teams so delivery capacity, risk, and stakeholder expectations remain aligned throughout the lifecycle. The rejected options do not resolve the planning problem at its source; they either add process overhead or make assumptions that leave ownership and delivery risk unclear. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (C. Scrum, because openness is one of the five core Scrum values.; D. Kanban, because one of its basic elements is to make everything visible, creating consistent transparency of work items.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Planning — governance; agile planning; environment strategy; backlog prioritization; sandbox strategy; stakeholder alignment.