Project Management

Please login or join to subscribe to this thread

What does your change management process look like?

linkedin twitter facebook   Change Management   Information Technology   Scrum  
avatar
Karrie Dash Sykesville, Md, United States
If a client requests a product scope change, what are the steps you take during the change process?

Example: client wants to add a new feature to a website

How do you look for negative effects a change might have on the product?
How do you determine if the change is still within the project's originally planned time or cost?
Which stakeholders or team members do you communicate with about the change during the decision process?
Do you have the client sign any documents agreeing to the changes and the effects it may have?
Which documents do you update once the change has been approved?
Sort By:
< 1 2 >
avatar
MANSOUR THABET ALQUBATY System Controller| Teleyemen Sana'A, N/A, Yemen
change management process consist of:-
a-Identify(what do you want to change?)
b-Document (document the change via change request form)
c- Review (do the impact & approve/reject the change)
d-Track(if there is an approval by CCB then implement the change)

Adding a new feature to a web-side ( I do not like word of feature it might be gold platen -let say a new function and not a gold platen) because gold-platen is not recommended for project(s).

To avoid of negative effects ( we should avoid the scope creep)
we should do a constraint triangle (balance) or let say ( a competent constraints).

How to determine if the change is still within project planned tile and cost is again by mainly constraint triangle ( plus measuring the performance against planned(EVM) but believe me no single answers can be mentioned here.

stakeholders to be communicated might be the team-sponsor-PM and CCB -customers
(any stakeholder).

Yes, sign of who request the change (at change request form).

Project management plan should be updated and some project documents should be updated (mainly change log).

I am sure most of participants will contribute more and more about their practices for answering your questions.

BR,
Mansour
...
1 reply by Atif Qureshi
Aug 31, 2018 6:38 AM
Atif Qureshi
...
I agree with Mansour, Its actually gold platting which is never good for project management.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Karrie -

This and many other considerations related to project change need to be defined in your project's Change Management Plan. This plan could be customized per project within organizational policies & standards.

Even with the same portfolio, it's unlikely that two projects will follow exactly the same change management process as this (like all other PM practices) should be tailored to fit the project...

Ciao!

Kiron
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Agree with Kiron, the process is outlined in the Change Management Plan. The bigger the organization or PMO, the more likely there will be a template or standard to follow.
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
I too agree with Kiron's input. Change Management Plan should be very well defined and every change should go through the proper process and through the CCB.

The answer to your question includes all the Change Management Plan Components.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
What you stated is a product change not a project change. But indeed the product change could impact creating a project change. Our way of thinking and behave is: all related to product/service/result to be created drives all related to project. The product/service/result is business analysis domain while project/program/portfolio is project management domain. Both roles working together to create all related to change impact and with all that on hand there is a group of people that decided about to do or not to do the change.
avatar
Atif Qureshi Outreach Manager| Ultahost Karachi, Pakistan
Aug 30, 2018 3:07 PM
Replying to MANSOUR THABET ALQUBATY
...
change management process consist of:-
a-Identify(what do you want to change?)
b-Document (document the change via change request form)
c- Review (do the impact & approve/reject the change)
d-Track(if there is an approval by CCB then implement the change)

Adding a new feature to a web-side ( I do not like word of feature it might be gold platen -let say a new function and not a gold platen) because gold-platen is not recommended for project(s).

To avoid of negative effects ( we should avoid the scope creep)
we should do a constraint triangle (balance) or let say ( a competent constraints).

How to determine if the change is still within project planned tile and cost is again by mainly constraint triangle ( plus measuring the performance against planned(EVM) but believe me no single answers can be mentioned here.

stakeholders to be communicated might be the team-sponsor-PM and CCB -customers
(any stakeholder).

Yes, sign of who request the change (at change request form).

Project management plan should be updated and some project documents should be updated (mainly change log).

I am sure most of participants will contribute more and more about their practices for answering your questions.

BR,
Mansour
I agree with Mansour, Its actually gold platting which is never good for project management.
avatar
Tamer Zeyad Sadiq Assistant Cost Manager| Turner & Townsend Riyadh, Ar Riyad, Saudi Arabia
Change request procedures are already mentioned in integration management in Rita book!!!
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Great inputs above.

The CM plan is structured within the organization. From identification and impact analysis, a decision on approval can be made - e.g. willing to accept additional cost or descope from original ask.
avatar
Joseph Prem Anand Program Manager| Deutsche Bank AG Cary, Nc, United States
Managing change and managing risk are probably the twin barrels of project management. Having said that, in recent years, most of the IT projects under my remit have embraced agile and have made the product owner(s) part of the rituals, negating the need for a formal change form or approval process. The projects still use jama, jira or similar tools to document and discuss the change.
avatar
Mohammed Abdullah Ali Ahmed Construction Supervisor| Petroenergy E&P Co. Ltd. Sudan
I think it is normally as PM you will receive any kind of change request, just you have to follow your change management carefully, make your internal evaluation first with risk assessment before go to CCB.
then simply convey the impact to your customer for final decision.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

Where lipstick is concerned, the important thing is not color, but to accept God's final word on where your lips end.

- Jerry Seinfeld

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters