Change Process Model

The model below is a re-interpretation of Young's ideas on process applied to software developement. More specifically, concurrent software developement.

As an example, for teams to work concurrently, the process they share should include strong elements of isolation. This isolation should be based on maturity of the code line, and the current responsibility of the team.

I use this model to determine completeness of a process. That is, you can use RUP, but it isn't complete until you define how teams isolate their code in source control.

Thus I tend towards maturity based branches (developing, stabilizing, and releasing). With each branch having a defined level of visibility between teams (developers, qa, deployment/release) and external users so that dependencies and change can be managed with minimal disruption.

Isolation
  Maturity
    Development
    Assessment
    Release
 
  Responsibility
    Definition
    Implementation
    Assessment
    Deployment/Release
     
Visibility
  Protection
    Private
    Protected
    Public 

  Dependency
    None
    Limited
    Open

Communication
  Notification
    Request
    Completion
  
  Collaboration
    Definition
    Revision
    Review

Change
  Transition
    Isolation Promotion
    Visibility Promotion

  Fulfillment
    Constraints
    Completion

  Assessment
    Quantification
    Risk