Project Management

Please login or join to subscribe to this thread

Can someone explain this statement

linkedin twitter facebook  
avatar
Tam Nguyen Annandale, Va, United States
Can someone explain this statement " Beyond the potentially misleading name, there are few more tricky aspects of the Validate Scope process. First, it can be done at the end of each project phase in the project life cycle ( to get formal acceptance of the phase deliverable along the way ) and at other points throughout the project as part of monitoring and controlling ( to get formal acceptance of any deliverable that require approval in the middle of the phase or project)"
Sort By:
avatar
Hatem Haffar Project Manager| Schweitzer Engineering Laboratories Pulman, Wa, United States
It is saying that the name "validate scope" have a misleading name, because everyone think is it a process to ensure a scope is valid. But actually it used in two phases of the project.
It can be used in the middle of the project to get acceptance of a deliverable, or at the end of the project to get acceptance of the scope or the project as a whole.
Hope I explained it well.
...
1 reply by Tam Nguyen
Jun 24, 2017 8:05 PM
Tam Nguyen
...
Thanks Hatem so much
avatar
Paras Dua Ghaziabad, Uttar Pradesh, India
This is the easiest way to remember it.. Validate Scope happens right after each quality check and you get an approval on the work right after you validate scope..
In other words, team works on a task, Quality team checks it for any issues, as a PM you Validate Scope of the Quality Approved Work Package / Task / Deliverable and then post an update / delivery to the client for their sign off.. they again validate scope and do UAT at their end, you get an approval / completion of the task / package / deliverable.. Hope this helps clarify in simple words..
...
1 reply by Tam Nguyen
Jun 24, 2017 8:06 PM
Tam Nguyen
...
Great explanation! Thanks Paras
avatar
Tam Nguyen Annandale, Va, United States
Jun 20, 2017 10:30 AM
Replying to Hatem Haffar
...
It is saying that the name "validate scope" have a misleading name, because everyone think is it a process to ensure a scope is valid. But actually it used in two phases of the project.
It can be used in the middle of the project to get acceptance of a deliverable, or at the end of the project to get acceptance of the scope or the project as a whole.
Hope I explained it well.
Thanks Hatem so much
avatar
Tam Nguyen Annandale, Va, United States
Jun 20, 2017 3:46 PM
Replying to Paras Dua
...
This is the easiest way to remember it.. Validate Scope happens right after each quality check and you get an approval on the work right after you validate scope..
In other words, team works on a task, Quality team checks it for any issues, as a PM you Validate Scope of the Quality Approved Work Package / Task / Deliverable and then post an update / delivery to the client for their sign off.. they again validate scope and do UAT at their end, you get an approval / completion of the task / package / deliverable.. Hope this helps clarify in simple words..
Great explanation! Thanks Paras

Please login or join to reply

Content ID:
ADVERTISEMENTS
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