Unable to isolate VB Studio changes with branching and promoting into another environment

Summary:

My organization is in the process of implementing Redwood for various modules. We are in a VB Studio environment with releases by different developers, at different phases of the lifecycle.  We are struggling however understanding exactly how to keep the changes within each local branch completely segregated from one another particularly when we are trying to merge our changes into the main branch, and deploying our own local branch changes to another environment (like UAT or Production) without impacting other developer's work. I have not been able to determine a specific way to implement a change that doesn't