Anti-Patterns of Change Control


CCB should include the same members as those that managed the   requirements baseline stream for the project (including the application   owner).


Applications (3 applications contribute to the release

Release manager (assuming there is someone assigned to manage the incoming pieces from the different applications), application owners, project managers and key project personnel. Typically, the members of this CCB should include the same members as those that managed the requirements baseline stream for the projects and application.



The next time you are in a position to establish a CCB, consider using this approach and examples above. Identifying the items that need to be managed and the workplace level in which the items live may help you identify the best choice of key members for a CCB who can most effectively assess the impact of a change and are empowered to make a change. Also, if you are working on a CCB that is having a difficult time implementing or managing change, consider the composition of the group and determine if the appropriate personnel are on the CCB.

Change management will always be challenging. It will never be easy at any of the levels mentioned above. However, including the appropriate level of personnel on the CCB may provide one-step forward into more effectively managing change.


About the author

Mario  Moreira's picture Mario Moreira

Mario Moreira is a Columnist for the CM Journal, a writer for the Agile Journal, an Author, an Agile and CM expert for CA, and has worked in the CM field since 1986 and in the Agile field since 1998. He has experience with numerous CM technologies and processes and has implemented CM on over 150 applications/products, which include establishing global SCM infrastructures. He is a certified ScrumMaster in the Agile arena having implemented Scrum and XP practices. He holds an MA in Mass Communication with an emphasis on communication technologies. Mario also brings years of Project Management, Software Quality Assurance, Requirement Management, facilitation, and team building skills and experience. Mario is the author of a new book entitled “Adapting Configuration Management for Agile Teams” (via Wiley Publishing). It provides an Agile Primer and a CM Primer, and how to adapt CM practices for Agile Teams. Mario is also the author of the CM book entitled, “Software Configuration Management Implementation Roadmap.” It includes step-by-step guidance for implementing SCM at the organization, application, and project level with numerous examples. Also consider visiting Mario’s blog on CM for Agile and Agile adoption at

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!