Register now or log in to join your professional community.
A. First Scope Verification, then Scope Control B. First Scope Control, then Scope Verification C. There is not enough information to decide D. Both happen simultaneously
Answer: CExplanation: Sometimes Scope Verification happens before Scope Control, and sometimes it happens afterwards -- and sometimes it happens both before AND afterwards. That actually makes a lot of sense when you look at what those two processes do, and how they interact with each other. You always perform some Scope Verification activities at the end of your project, because you need to verify that the last deliverable produced includes all of the work laid out for it in the Scope Statement. Most projects will almost certainly have gone through Scope Control before then. So it might seem like Scope Control always happens before Scope Verification. But you don't just perform Scope Verification at the end -- you actually do it after every deliverable is created, to make sure that all the work for that deliverable was done. Not only that, but sometimes Scope Verification fails because your team didn't do all of the work that was needed -- that's why Requested Changes are an output of Scope Verification. And if those changes include scope changes, then your project will end up going through Scope Control again -- possibly for the first time in the project, if this is the first scope change you've had to make. So Scope Control can happen before Scope Verification, but it can also happen afterward as well. That's why there's no prescribed order for those two processes: they can happen in any order.
