Project+ IT Change Control Board Basics

1. What is a 'change request' in the context of project governance?

A formal proposal to modify scope, schedule, or budget

An informal email to IT staff

A complaint about project progress

A vendor invoice

Submit

4. What is the purpose of documenting change decisions in a CCB?

Create an audit trail for compliance and future reference

Waste time on paperwork

Hide decisions from stakeholders

Delay project implementation

5. Which stakeholder perspective is essential when evaluating a change request?

Business impact, technical feasibility, and resource availability

Only IT cost perspective

Only management opinion

Vendor preferences alone

6. True or False: A CCB can reject a change request if the risk outweighs the benefit.

True

False

7. What does 'configuration management' support in IT governance?

Tracking and controlling IT assets and system components

Employee scheduling

Marketing strategy

Office furniture inventory

8. A CCB review meeting should include which key activity?

Discussion of change impact, feasibility, and approval decision

Social networking only

Scheduling the next vacation

Reviewing employee performance

9. Which of the following best describes 'risk management' in CCB decisions?

Identifying and evaluating potential negative impacts of changes

Ignoring potential problems

Implementing changes without testing

Blaming users for system issues

10. True or False: Governance frameworks help align IT projects with business strategy.

True

False

11. What is the primary purpose of a Change Control Board (CCB)?

Approve or reject proposed changes to ensure minimal risk and alignment with organizational goals

Execute all system updates without stakeholder review

Document only failed changes for audit purposes

Eliminate the need for project managers

12. Which is an example of a major change that typically requires CCB approval?

Upgrading a production database system

Updating a developer's local software

Adding a single user account

Routine backup procedures

13. In IT governance, what does 'accountability' mean?

Clear assignment of responsibility for decisions and outcomes

Blaming others for failures

Avoiding documentation

Making decisions without consultation

14. What is the main benefit of using a formal change control process?

Reduces risk, maintains stability, and prevents conflicting changes

Eliminates all project delays

Increases the number of changes implemented

Removes the need for testing

15. True or False: A CCB should approve all changes, including minor bug fixes.

True

False

16. Which document formally describes what changes require CCB approval?

Change Management Plan

Employee handbook

Vendor contract list

IT equipment inventory

17. What is a baseline in IT project governance?

An approved reference point for scope, schedule, and budget

The initial project budget without any changes

A list of all team member names

The physical location of project files

18. A Change Control Board typically includes representatives from which areas?

IT, business, project management, and quality assurance

Only IT department staff

Finance and human resources exclusively

External vendors only

19. What does governance in IT project management primarily address?

Rules, policies, and structures for decision-making and accountability

The physical layout of server rooms

Employee vacation scheduling

Network bandwidth allocation only

20. Which of the following is a key responsibility of a CCB?

Assessing the impact and feasibility of proposed changes

Writing all project code and deliverables

Managing employee payroll systems

Replacing IT hardware without approval

Project+ IT Change Control Board Basics Quiz

1. What is a 'change request' in the context of project governance?

2.

What first name or nickname would you like us to use?

2. The____ is the agreed-upon version of project scope, schedule, and budget that serves as the reference for change control.

3. A project manager must communicate CCB decisions to____.

4. What is the purpose of documenting change decisions in a CCB?

5. Which stakeholder perspective is essential when evaluating a change request?

6. True or False: A CCB can reject a change request if the risk outweighs the benefit.

7. What does 'configuration management' support in IT governance?

8. A CCB review meeting should include which key activity?

9. Which of the following best describes 'risk management' in CCB decisions?

10. True or False: Governance frameworks help align IT projects with business strategy.

11. What is the primary purpose of a Change Control Board (CCB)?

12. Which is an example of a major change that typically requires CCB approval?

13. In IT governance, what does 'accountability' mean?

14. What is the main benefit of using a formal change control process?

15. True or False: A CCB should approve all changes, including minor bug fixes.

16. Which document formally describes what changes require CCB approval?

17. What is a baseline in IT project governance?

18. A Change Control Board typically includes representatives from which areas?

19. What does governance in IT project management primarily address?

20. Which of the following is a key responsibility of a CCB?