I wanted to create this picture to show you clearly the transition of deliverable to final product, service or result within the project management context.
- Deliverables are created as part of the "Direct and Manage Project Execution" process. As you would expect, the deliverables are outputs of the Execution process group.
- The deliverable, thus created during project execution, is fed as input to the "Perform Quality Control" process in Monitoring & Controlling process group. Necessary quality control checks are carried out to ensure that the deliverable meet the requirements. At the end of the process, we get the Validated deliverable as an output.
- The validated deliverable is sent as an input to the "Verify Scope" process. Here, the client/ customer inspects the deliverable and accepts them. As such, the output of this process is the accepted deliverable. The major difference between "Perform Quality Control" and "Verify Scope" is that generally quality control is performed internally within the performing organization while verify scope is performed with the client/ customer. They may be done sequentially or sometimes concurrently.
- Finally, the accepted deliverable is sent as an input to the "Close project or phase" process in the Closing process group; and the output is Final product, service or result transition. This refers to the acceptance of the final product, service, or result and the turnover of the product to the organization. This usually requires a formal sign-off to indicate that the product is accepted by the customer.
Hope the above picture helps you to remember the flow of deliverables better. What do you think? Please leave your comments.
This is a great diagram. A few iterative activities for Change Request will show a complete picture.
ReplyKishore
Thanks Kishore. I will look into it.