How does using org development help the team at Zephyrus with their change-management challenges?

How does using org development help the team at Zephyrus with their change-management challenges?

• A. Developing programmatically ensures there are fewer changes to manage in the first place.
• B. The team can do all of their development in a single org to avoid conflicting changes to apps.
• C. Changes between team members can be merged in a controlled manner.
• D. They can use a scratch org as their version control system.

Answer: (C)

The main idea being tested is that organizing development around separate orgs allows changes from different team members to be brought together in a controlled, mergeable way. When each developer works in their own isolated org (such as a scratch org or a dedicated dev org), their changes don’t slam into someone else’s work immediately. Those changes are then captured in a shared version-controlled source of truth and integrated through a formal merge and release process. This makes it possible to reconcile differences, resolve conflicts, and verify that everything fits together before moving to a shared environment or production. It provides traceability of who changed what, when, and why, which is essential for reliable change management. The other options don’t fit this approach. Developing in a single org doesn’t prevent conflicts; it often makes them worse because everyone is modifying the same space. Treating a scratch org as a version control system misconstrues the role of scratch orgs, which are temporary development environments, not repositories. And the notion that programmatic development inherently reduces the number of changes misses the point—change management is about how to manage and merge those changes effectively, not simply making changes fewer in number.

The main idea being tested is that organizing development around separate orgs allows changes from different team members to be brought together in a controlled, mergeable way. When each developer works in their own isolated org (such as a scratch org or a dedicated dev org), their changes don’t slam into someone else’s work immediately. Those changes are then captured in a shared version-controlled source of truth and integrated through a formal merge and release process. This makes it possible to reconcile differences, resolve conflicts, and verify that everything fits together before moving to a shared environment or production. It provides traceability of who changed what, when, and why, which is essential for reliable change management.

The other options don’t fit this approach. Developing in a single org doesn’t prevent conflicts; it often makes them worse because everyone is modifying the same space. Treating a scratch org as a version control system misconstrues the role of scratch orgs, which are temporary development environments, not repositories. And the notion that programmatic development inherently reduces the number of changes misses the point—change management is about how to manage and merge those changes effectively, not simply making changes fewer in number.