The project's deliverables are the systems or programs that will be put in place once the project is completed. The scope describes what we 're going to do; the deliverables describe the specific details. There could be several deliverables in any project—it's important that the project manager enumerate each one.
For example, suppose that the project before you consists of a browser- based (thin-client) solution that utilizes two back-end servers: a database server and an application server. Your deliverables will include the following components: a browser screen that contains a predetermined number of elements, a server running the network operating system (NOS) of the client's choice with the database, and a second server running a relational database management system (RDBMS) and the same NOS as the database server. In other words, what can the sponsor expect the system to be composed of, and what will it do after the project is finished? Who will be the user of the system? The deliverables pinpoint the things that the users of the project's output will be able to utilize.
Tip Some IT Project+ exam objectives use the term client. I typically use the word customer. For the purposes of this book, you can consider these interchangeable.
It's important that the customer and the project management team are clear on what the deliverables are going to be so there's no finger-pointing at the end of the project. The elements that are going to be a part of the system, such as the screen and report mockups, for example, are a good thing to introduce at deliverables formulation time. Tip A general statement like "reports showing the accounts receivable, inventory turnover, and distributions" that says nothing about format or interface might mean one thing to you and another to your customer. Clearing up what is meant by the terms the customer uses, as opposed to what you may think the terms mean, will go a long way toward satisfactory requirements definition.
Was this article helpful?