Project Change Management: Minimize Risks. Maximize Rewards.
- from ITtoolkit.com
Considering the effort that it takes to gather
requirements, assemble a team, secure approvals, and create a
working schedule, sudden and unexpected “changes to plan” are not
always wise – and certainly not always welcome. There are times
when change is a mistake, and times when change is
essential. No matter which side any given change may be on,
change is a reality that must be
faced and controlled.
Read on to learn how it’s done.
Change is a fact of life for most every project. To begin with, projects occur over a span of time, and with the passage
of time, underlying circumstances and conditions can and do change. In addition,
projects are completed by people, and people have new ideas, recognize
mistakes and change their minds. Under these circumstances, it would
be unwise, if not impossible, to proceed without recognizing,
accepting and preparing for the possibility of change. That’s
the purpose and goal of standardized “change management”.
What is Project Change Management?
Project change management is defined by the body of concepts,
steps and strategies used to manage, control and implement “change”
within a project. Change management applies to all elements of the
project and project management process, covering the
project vision, scope and
related procedural components. Change management procedures are
sized and applied to a given project as part of the
project governance phase
and are executed as part of project oversight. The key to effective
project change management is not to prevent change, but to control
it. This is the whole point – to identify, evaluate and adopt
changes so that project results are enhanced. To that end, project
should be managed with a structured process designed to accept
positive change and avoid negative change.
Key to Success: Effective practices for project change management must incorporate
and address the two (2) primary types of change:
- Reactive Change: When changes are necessary to respond
to project problems (i.e. delays, technical failures, funding shortages,
resources issues, etc.). In all likelihood, reactive changes are not
optional as long as you wish to sustain or salvage the project. - Requested Change: When changes to project
requirements, scope, deliverables or related management plans
are requested by end-users or other project participants. These
changes can arise from new ideas, new information, or new
perspectives, and usually are requested by
project customers (i.e. your
end-users). In any event, requested changes are usually
discretionary, and therefore, are difficult to control. While
certain changes can enhance and improve a project, if left
uncontrolled, excessive change
can lead to multiple, varied problems. Excessive project
changes can overwhelm a project to the point where original
benefits are lost, and the project can no longer be completed as
expected. The trick to change control is to continually balance
change requests against original project goals, ensuring
enhanced value, without diminishing schedules and results.
Learn to Fast Track
When it comes to managing, you need more than one approach
to be consistently successful. The way you manage when surrounding conditions are good, is not
the way you manage when time is running short, resources are stretched thin and people aren’t
working together. That’s what fast tracking is for – and we can teach you how it’s done.
Learn More
Manage Change: Be On Time, Be On Budget
In order to properly “control” changes for any given project, appropriate
boundaries must be set that will both establish and limit the types of
changes to be considered. Obviously, if a change is required to
keep a project going, that change must be accepted. But if change is discretionary,
that change must be weighed against existing project conditions and
established boundaries. Taking a standardized approach, it takes
just five (5) analytical variables to set realistic,
flexible boundaries for managing project change:
- Value and Priority. If a project is very visible
and important, you may need to set high limits for discretionary changes
to avoid unwarranted risks. - Timing. If the change request arrives at an early
stage in the project, that change can probably be absorbed, but if the
project is more than 50% complete, that same change may actually interfere
with timely completion. - Cost. Project changes can increase (or decrease)
project costs. In order to properly manage changes, you should set limits
on change related costs, so that your budget is appropriately maintained.
In addition, for large projects, separate change budgets (also known
as a contingency fund) should be established to set limits for change
costs outside of the original budget. In effect, your initial budget
establishes expected costs, and your change budget controls the costs
of subsequent changes. - Impact. In order to maintain proper control of project
change, you will need toevaluate and identify “change impact” – i.e.
how will a given change affect the project as a whole or in part? Will
the change impact scope, deliverables, schedules, resources, or some
other project element? With this detailed understanding, you can set
appropriate, yet flexible boundaries as a guideline for change review
and approval.
Producing the “Change Impact Statement” (CIS)
Once change requests are processed, reviewed and approved, the corresponding
changes must be incorporated into existing project plan, vision and
scope. Depending on the specific type of change, one or more elements
of the project may be affected, and this may necessitate changes to
project plans, technical designs, resource assignments, budgets or other
project documentation. No matter how many areas of the project are affected,
changes should be properly recorded to ensure that original documents
and plans are maintained as a baseline, with changes clearly identified.
Most automated project planning tools will track changes to plan, and
will produce reports of all variations. However, as time passes, and
with multiple projects underway, these reports may not provide sufficient
“lessons learned” information as to the “whys and wherefores” of change
approval, and the related change results. That’s the point of the “Change
Impact Statement”.
The “Change Impact Statement (CIS)” is a project oversight and
review deliverable used to record change reasoning, execution and
consequences. To serve it’s intended purpose, the “statement”
deliverable should accomplish all of the following:
- The CIS should describe the defining characteristics of the
proposed “change”
considering the type, scope, characteristics and potential impact.
(Change decisions should be based on the “define,
align and approve” paradigm). - The CIS should provide a detailed explanation of the reasoning behind
change approval including a brief summary of the approval process, description
of anticipated benefits and related consequences for a failure to act
(if any). - The CIS should provide a detailed description of the steps and procedures
followed in implementing the related change. - The CIS should include an evaluation of change planning compared
to actual change results. - The CIS should include an evaluation of change management “lessons
learned” for use in the project review process.
CHECK OUT THE FAST TRACK PROJECT TOOLKIT.
If you’re looking for a fast, easy way to achieve project planning success, you’ll find it inside
the Fast Track Project Toolkit. This unique, informative online course gives you everything you need to become
a project leader and fast tracking expert. Here’s what you’ll learn:
-
How to plan and govern projects using strategic project fast tracking.
-
How to use strategic project fast tracking to save time and make the most of available resources.
-
How to use strategic fast tracking to overcome project constraints and limitations.
-
How to use strategic fast tracking to negotiate with stakeholders and build shared expectations.
-
How to use strategic fast tracking to become a more productive project manager and team member.
Source: Unless noted otherwise, all content is created by and/or for ITtoolkit.com
Related Articles
About Us
ITtoolkit.com staff writers have experience working for some of the largest corporations, in various positions including marketing,
systems engineering, help desk support, web and application development, and IT management.
ITtoolkit.com is part of Right Track Associates, proprietors and publishers of multiple web sites including ITtoolkit.com, Fast Track Manage, HOA Board List and more.
We started ITtoolkit.com in 2001 and have continued to grow our web site portfolio, Toolkit products, and related data services.
To learn more, visit us at Right Track Associates.
-
Planning
- Fundamentals of Disaster Recovery Planning in IT Management
- How to Motivate Your Project Team in Four (4) Simple, Strategic Steps
- Project Proposals: Means and Methods for Project Selection
- Requirements Analysis: Business Needs Drive IT Projects
- Technology Standards: The Basis for Acceptable Use Policy
Policy
-
Practices
- Asset or Untapped Resource? The Value of Institutional Knowledge in IT
- IT Management Audits: Ensuring the Benefits of Sustained Compliance
- Common Sense Practices for Reducing Project Risk
Projects
- Avoid, Accept or Mitigate? Three Options to Control Project Risk
- Budgeting to Fund the Project Scope and Expected Work Effort
- Critical Path Analysis: Techniques for Project Scheduling
- Key Fundamentals of Quality Management in the IT Project
- Easy Ways to Identify and Analyze Probable Project Risks
- Project Success Criteria: Realistic Expectations for Optimal Results
- Deliverables Testing: Validating Form, Function and Success
- Using the Work Breakdown Structure (WBS) for Project Planning
-
Resources
- How to Motivate Your Project Team in Four (4) Simple, Strategic Steps
- How to Organize Project Teams for On Time, On Budget Results
- Committees, Cooperation and a Working Code of Conduct
- Using Project Job Descriptions and Profiles to Staff the Project Team
- 12 Key Questions to Evaluate Project Team Readiness
- Project Responsibilities Framework: Defining Stakeholder Roles
- Easy Steps for Evaluating Project Team Performance
Services
-
Skills
- How to Manage Staff Burnout in IT Projects and Service Operations
- Can’t Find the Time? That’s O.K. Learn How to Make It!
Strategy
- What’s the Cost of Quality in IT Projects? (Hint: High, But Worth It)
- Making I.T. Work: Overcoming Barriers to Office Productivity
- Understanding the Role of the Project Sponsor and Mentor
- Coping with Troubled Projects: Time for Rescue or Graceful Exit?
- Creating Opportunities for Value Added IT Management
I.T. Service Planning
Start For Free
If you’d like to learn how to quickly plan I.T. service strategies designed
to meet every goal for technology service alignment, service quality and end-user service satisfaction,
the I.T. Service Strategy Toolkit is the right course for you. Brought to you by the publishers
of ITtoolkit.com, this self-paced course is easy, engaging and actionable, giving you both how-to
lessons and take-action tools.
Start for free now!.
Committee Management
Start For Free
If you’d like to learn how to form and operate successful committees, destined to be
more productive and less prone to conflict, the Project Committee Toolkit is the right
training course for you. Brought to you by the publishers
of ITtoolkit.com, this easy course gives you both the lessons and the tools you need
to be a better committee leader and organizer.
Start for free now!.
Project Management
Start For Free
If you’d like to learn how to how to streamline project management activities
to get work done in less time, using the resources you have, then the
Fast Track Toolkit online course is what you need. Brought to you by
the publishers of ITtoolkit.com, you’ll learn how to ‘fast track’ every
stage of the project management process, from pre-project planning to the
post-project review.
Start for free now!.