Tuesday, April 3, 2012

Defining Deliverable Outputs


A "deliverable," in project management, is an object (tangible or intangible) created by a project for delivery to an internal or external client. A deliverable might be a report, video, document, system upgrade, process change, any other product or service or piece thereof. Activities (work) are connected with deliverables.

Creating a deliverable is a process. What is needed to produce the deliverable are its inputs. What the deliverable produces--what it is created to do (functions, forms, work) are its outputs.

While most of us are good at naming or listing deliverables, we are not as good at defining their outputs.  Without well defined outputs, deliverables can not be tested or integrated well and that invariably leads to rolling out a poor solution to the client.

Defining deliverable outputs is a key step toward transitioning projects that meet expectations.

Posted by: William W. (Woody) Williams

No comments: