Categories: New to Project Management
You may think that a change control board (CCB) has to be some official project governing body, but it's not so.
A CCB can be a small group of project team members who are willing to review and approve or reject change requests. Even if your projects are small, it's better to have some semblance of a CCB than to have none at all.
A CCB can help you manage the myriad changes that will come your way as a project kicks off. Your sponsors, stakeholders and project delivery team may all have agreed on scope, cost and schedule -- but it's inevitable that something will change before the project closes.
Those changes come in many shapes and will impact your project positively and/or negatively. A CCB helps you figure out which changes are acceptable to undertake, which aren't and which can be shelved.
Instead of shunning change or accepting every idea without examination, use the CCB to determine the best course of action for the project.
There will be times when members of your project delivery team have great ideas for the project, for example. After all, they're right in the mix during the execution phase and can clearly see where things could be improved. If you always shoot those ideas down, you will create strife between yourself and your team.
You may find no one comes to you with great ideas anymore. Part of a CCB's job is to listen to all ideas, carefully consider the merits, and explain to the project team (or stakeholder or sponsor) why an idea was approved, rejected or held until more favorable conditions arise to implement it.
A CCB can be more than just a repository for tracking changes and a governance tool. A CCB can show team members and stakeholders that their ideas are worthwhile and innovative, and can help foster those ideas that most positively impact a project.
What kind of CCB do you use? What do you have them help you with?
See more posts from Taralyn.
See more posts for new project managers.