Deliverable table is a tool/method to plan, control and verify that all contract and project obligation to the customer are met and executed.
The method is to put together a table (see example below) that outlines all the project’s obligations in terms of “things to deliver” to the customer.
Basically, there are four (4) types of deliverables which are:
- Hardware (HW): All tools, machinery and other durable equipment, physical components of computer and other “touchable” items
- Software (SW): This includes system operating information, diagnostic computerized tools, Built In Test (BIT) program etc’
- Document: All range of documentation to be handed over to the customer like manuals, QA reports, Certificates, graduation cards, financial reports etc’
- Activity/service: This could be training courses, to conduct a ceremony etc’
The deliverables are mainly embedded in the SOW and un the Technical Specification (TS) but also in the Contract there may be some requirement for Deliverables and in any other document which is part of the project paper work. The deliverables are not always outstanding and direct, one should read carefully all the project documentation and identify within the deliverables. In some cases, the customer will in advance provide a deliverable table to the provider, this ofcaurse makes the sorting job easier…
Now, a table is set as in the example below.
On the left hand side of the table the deliverables are listed one by one with its serial number for identification. Next the source of the deliverable is embedded and the number of deliverables (quantity) to be provided. Most importantly is to write down the due date to deliver according the contract.
As the project goes on, on regular bases (once a week, once a month…) the table needs to be addressed to see if any deliverable is due and to make sure there are no delays in delivery.
