Please login or join to subscribe to this thread
Your process for handling scope changes should be documented in your Scope Management Plan.
The way we handle scope changes is through our CAB - Change Advisory Board. All changes need to go through the CAB. They will determine whether the change needs to be incorporated in the project now (in the case where the project cannot be successful without the change) and will the change effect the schedule or cost, or will the change be delayed to a later Sprint or Phase.
Obvious answer: following the defined project change mangement process.
First of all Thanks for your time. A CAB process is indeed nowadays used by several enterprises around the world. I have seen enterprises hosting a CAB meeting once a week, but not only to discuss changes for projects but also to discuss changes on the infrastructure . What is funny about CAB meetings is that in large enterprises where there are many teams, presenting or trying to get their changes approved most of the times, the 9 times out of 10 the changes are approved on the fly...approved next, approved next.
So now after few years of seeing this behavior i seem think that CAB is mostly a waste of process and time.
But yes your answer is totally valid. Thanks Dinah, have a wonderful day
You have a good point too, and sure enough if the proper change management process have been defined during the build of the charter...or another words at the beginning of the project. This action will definitely avoid misunderstandings with the clients and/or the stakeholders or projects sponsors.
Thanks Sergio for your input.
Scope changes need to be discussed with Customer, Project Sponsor and relevant stakeholders. Changes to be documented and necessary approvals to be taken.
It may so happen with scope change some of the already agreed requirements can be dropped. use of MoSCoW method helps.
Change Control Board (CCB) manages all changes, approve, reject, delay, document,..etc. and updates in change log for motoring status. After that, they will update the project management plans and documents. All processes are mentioned in PMBOK!!!!!
Best to have a set of guidelines in place with practice and consistency. Also, based on the agreed-upon scope definition (and what is not in scope), as well as how defined in the SOW.
Agile approach accommodes best for changing customer requirements and priorities. I would suggest to consider iterative delivery / iterative charging as per agile approach in the future.
Thank you sir for your time. While I have the PMBOK with me, I am looking for actual experiences in the field and for different opinions, rather than a reading it from the book. I do appreciate your time.
Please login or join to reply