- All
- Waterfall Project Management
Powered by AI and the LinkedIn community
1
Define the CCB
Be the first to add your personal experience
2
Establish the change request process
Be the first to add your personal experience
3
Prepare for the CCB meeting
4
Conduct the CCB meeting
Be the first to add your personal experience
5
Follow up after the CCB meeting
Be the first to add your personal experience
Change requests are inevitable in any project, but they can also cause delays, conflicts, and scope creep if not managed properly. In a waterfall project, where each phase depends on the previous one, change requests need to be carefully evaluated and approved by a change control board (CCB) before they can be implemented. How do you manage CCB meetings in a waterfall project? Here are some tips to help you run effective and efficient CCB meetings.
Top experts in this article
Selected by the community from 3 contributions. Learn more
Earn a Community Top Voice badge
Add to collaborative articles to get recognized for your expertise on your profile. Learn more
- Pete Schneider Agile Coach, Certified SAFe® 6 Practice Consultant
1
1 Define the CCB
The CCB is a group of stakeholders who have the authority to review, approve, reject, or defer change requests in a waterfall project. The CCB may include the project sponsor, the project manager, the customer, and representatives from different functional areas or departments. The CCB should be defined at the beginning of the project and documented in the project charter or the project management plan. The CCB should also have clear roles and responsibilities, such as who can initiate, submit, or vote on change requests, and how often and when the CCB meetings will be held.
Help others by sharing more (125 characters min.)
2 Establish the change request process
The change request process is a set of steps and procedures that guide how change requests are identified, submitted, analyzed, evaluated, approved, implemented, and communicated in a waterfall project. This process should be aligned with the project scope, schedule, budget, quality, and risk management plans. All project stakeholders and team members should be made aware of the change request process and it should be updated as needed throughout the project. The change request process should include a form capturing the details of the proposed change, a log tracking the status and history of all requests, an analysis assessing the feasibility, viability, and desirability of each request, an evaluation comparing each request against project objectives, criteria, and constraints, an approval determining the final decision on each request, an implementation executing approved changes and updating deliverables, plans, and documents accordingly, as well as communication informing stakeholders and team members about changes and their impacts.
Help others by sharing more (125 characters min.)
3 Prepare for the CCB meeting
Before the CCB meeting, the project manager should review all the change requests that have been submitted and analyzed since the last meeting, and prepare a summary report that highlights the key information and recommendations for each change request. The project manager should also distribute the summary report and the relevant documents to the CCB members in advance, and request them to review them and prepare their questions and feedback. The project manager should also set the agenda and the objectives for the CCB meeting, and confirm the date, time, location, and attendance of the CCB members.
Help others by sharing more (125 characters min.)
- Pete Schneider Agile Coach, Certified SAFe® 6 Practice Consultant
(edited)
- Report contribution
Thanks for letting us know! You'll no longer see this contribution
The big challenge I had with a CCB at a startup was getting people to come prepared. The meetings where chaotic. Everyone wanted to start in a different place. Some people wanted to revisit the whole spec, not just the changes specified in the agenda. I had conversations I had with CCB members, the pre-meeting emails, and how I ran the meeting. I talked with people before the meeting to take a feel for proposed changes. I sent out a pre-meeting email where I recommended that some changes either be accepted/rejected without discussion, and outlined in priority order, the ones that we were going to discuss l. I ran the meeting exactly as described in the email. It took a few meetings to stick, but it made a big difference.
LikeLike
Celebrate
Support
Love
Insightful
Funny
1
Load more contributions
4 Conduct the CCB meeting
During the CCB meeting, the project manager should facilitate the discussion and decision-making process for each change request. The project manager should present the summary report and the analysis for each change request, and invite the CCB members to ask questions, share opinions, and raise concerns. The project manager should also ensure that the CCB members follow the agreed-upon criteria and procedures for evaluating and approving change requests, and that they document their decisions and rationale in the change request form and log. The project manager should also manage the time and the scope of the CCB meeting, and avoid getting into unnecessary details or debates that are not relevant to the change requests.
Help others by sharing more (125 characters min.)
5 Follow up after the CCB meeting
After the CCB meeting, the project manager should communicate the results and actions of the CCB meeting to all project stakeholders and team members, and update the project deliverables, plans, and documents accordingly. The project manager should also implement the approved changes and monitor their progress and performance, and report any issues or deviations to the CCB. The project manager should also collect feedback and lessons learned from the CCB meeting, and use them to improve the change request process and the CCB meeting effectiveness in the future.
Help others by sharing more (125 characters min.)
Waterfall Project Management
Waterfall Project Management
+ Follow
Rate this article
We created this article with the help of AI. What do you think of it?
It’s great It’s not so great
Thanks for your feedback
Your feedback is private. Like or react to bring the conversation to your network.
Tell us more
Tell us why you didn’t like this article.
If you think something in this article goes against our Professional Community Policies, please let us know.
We appreciate you letting us know. Though we’re unable to respond directly, your feedback helps us improve this experience for everyone.
If you think this goes against our Professional Community Policies, please let us know.
More articles on Waterfall Project Management
No more previous content
- How do you estimate the duration and effort of each project stage? 8 contributions
- What are the main components of a project scope statement and why are they important? 12 contributions
- How do you balance project integration management processes and project innovation? 11 contributions
- How do you manage scope creep in a waterfall project? 7 contributions
- How do you identify and prioritize the potential risks in a waterfall project? 5 contributions
- What are the pros and cons of the waterfall method? 5 contributions
- How do you define and validate the project scope with your client? 4 contributions
- How do you design effective test cases and scenarios for waterfall projects? 3 contributions
No more next content
More relevant reading
- Waterfall Project Management How do you define the scope and criteria of a change request in waterfall?
- Project Management How can you simplify project change control?
- Project Management How can you identify the impact of a change request on a project using Waterfall methodology?
- Waterfall Project Management How do you review and improve the change control process in waterfall?
Help improve contributions
Mark contributions as unhelpful if you find them irrelevant or not valuable to the article. This feedback is private to you and won’t be shared publicly.
Contribution hidden for you
This feedback is never shared publicly, we’ll use it to show better contributions to everyone.