This post was originally published on this site
Does this sound familiar? You are starting a new project, and the first thing the project manager wants to do during the kick-off call is to review the project scope with the team. Next, your team works with the Implementation team to provide requirements, and now the project team wants to verify your requirements against your project scope again.
What gives? This repetition is starting to remind you of being at the doctors. They keep asking you to confirm your date of birth to match it to your chart. Double checking means you don’t have your appendix removed instead of your tonsils. I think we all agree that is an important check.
You will be ready for a successful HCM implementation when everyone agrees on the defined scope. According to one study by the Project Management Institute (PMI), 52% of projects experienced scope creep or uncontrolled changes. These numbers alone should motivate project team members to want to participate in this process.
So, what is the scope review process? This process is a collaborative step to ensure that the scope accurately reflects the mutual understanding between you, the client, and the project team. This review provides a detailed picture of
