10 - Change Control & Governance Flashcards
What are the three objectives of Change Control?
- Plan for Change
- Design for Change
- Build for Change
What is Change Control?
A process which ensures that changes on a project are introduced in a controlled and coordinated manner
What are the advantages of Change Control?
- No surprises
- Fosters better relationship with business
- Establishes an audit trail
- Highlights the need/availability of resources
- Realigns the team focus as needed
What are the risks to a project if Change Control is not implemented?
- ‘Must have’ changes may not be implemented
- Scope can be drastically impacted
- Timelines can be compromised
- Expectations can be misinterpreted and/or misaligned
Should the Change Control process be implemented early and communicated effectively?
Yes - do it in advance. Gets everyone bought in early.
What are some key characteristics of a the Change Control process?
- When will it be initiated?
- How will it be tracked?
- What the approval process is?
- Who will participate on the approval team?
Describe the four Change Management Best Practices
- Capture the Changes
- Classify & Prioritize
- Assess the impact
- Integrate into the Plan as appropriate
Describe the Iceberg approach to Change Control
Determine where the Change Control item fits based on risk, priority and business value;
- If it replaces an item in scope, evaluate:
- Which of the lowest priority items in scope will be shifted to future release or
- Which of the Sliver parameters will change (timeline, resources, and so on) to accommodate the addition
Below the waterline is an indicator of next release capabilities
Above the waterline is an indicator of in scope capabilities
When a change to the project parameters is needed (scope, resources, timeline)
- Ensure only two of the three are in control of business
- Final factor must be a result of the model being validated
When does Governance occur?
Throughout the lifecycle
What is Governance?
Regularly scheduled meetings with key stakeholders to
- review risk,
resolve issues - montior plan and budget
Why is governance important?
- Provides bi-directional escalation paths for quick issue identification and resolutions
- Forces all parties to be in sync
- Reduces risk
Who should participate in Governance (at a minimum)?
- Project Sponsor
- Project Manager
- Leadership from IT, business and QA
When should Governance be performed?
At a minium bi-weekly for 30 minutes
What are the objectives of Governance?
Ensure
- The business benefit is delivered
- Project scope, time and budget are controlled
- Risk identification and mitigation plans presented and accepted
- Review project to plan schedule, hours and budget
What is the general purpose of Governance?
Outlines the minimal standards by which projects should be managed which include
- Executive Project Steering Committee
- Project Status Reports
- Project meetings
- Issue resolution
- Change control
