If you create Microsoft Project schedules, you are familiar with creating tasks and [how tasks are used](http://blog.advisicon.com/2010/01/27/best-practice-include-project-management-tasks-in-your-project-schedule/ “Best Practice: Include Project Management Tasks in your Project Schedule | Advisicon Blog”) to [represent activities](http://blog.advisicon.com/2008/12/29/best-practices-in-writing-task-names-for-pwa-users/ “Best Practices in Writing Task Names for PWA Users | Advisicon Blog”) that [must be completed](http://blog.advisicon.com/2009/11/25/project-scheduling-best-practice-build-your-project-management-tasks-into-your-project-schedule/ “Project Scheduling Best Practice: Build Your Project Management Tasks into Your Project Schedule | Advisicon Blog”) to [accomplish the goals](http://blog.advisicon.com/2008/11/25/how-many-resources-does-it-take-to-change-a-light-bulb/ “How Many Resources Does It Take to Change a Light Bulb? | Advisicon Blog”) of [your project](http://blog.advisicon.com/2008/12/10/how-to-change-the-assignment-owner-on-tasks/ “How To change the Assignment Owner on Tasks”). Many times tasks follow the PMI guidelines of representing deliverables. According to a [PMBOK Guide](http://www.pmi.org/en/PMBOK-Guide-and-Standards/Standards-Library-of-PMI-Global-Standards.aspx “Library of PMI Global Standards”) by the [Project Management Institute](http://www.pmi.org “PMI website”), a deliverable is a “verifiable work product.” I have seen a variety of schedules represent deliverables different ways including Summary tasks, Detail tasks, or Milestones. Often when people learn that there is a feature called “deliverables” they wonder how that differs from tasks in the schedule.
## Three Advantages of the Deliverables Feature
1. **Relevant info for stakeholders and team members**. Provides the ability to use Project Server to manage a complete schedule, but offer a list of alternate tasks that are managed separately and visible to individuals that you do not want to have access to the entire schedule.
For example, you may want your internal team to see the entire schedule; but the external customer or vendor should only see a predefined, limited list of tasks.
2. **Track non-task, project related items**. Provides a way to keep track of things that are related to your project but don’t directly belong as a task in your schedule.
For example, a financial report that you create about your project that goes to an internal accounting person to be used to create a report for the PMO director.
3. **Identify external project drivers**. Provides a way to list tasks that could be drivers to another (external) project. _This happens to be my favorite use of the deliverables feature and the one that most people do not know about._
It is an excellent way to illustrate project-to-project links without worrying about tasks shifting in external projects. That’s what happens in a traditional project-to-project task link.
## How to Access Deliverables
In both Project Server 2007 and 2010 you can access the deliverables feature through the related Project Site.
In this next illustration, notice that the tasks in the schedule are not altered, but the deliverable (indicated with an arrow below) is visually available for a project manager to compare how an external project’s task might affect a task in the current schedule he or she is managing.
## Summing Up
To summarize, the deliverables feature can be used instead of tasks in the schedule to represent a separate/independent list of project tasks, to capture non-project tasks/deliverables, and finally to represent tasks from external projects.
For training classes held onsite, deliverables can be added as part of our tailored training agenda for each customer. For more details, see our [available training course options](http://advisicon.com/training.htm “Train your organization with the expert instructors at Advisicon”).
*[PMO]: Project Management Organization or Project Management Office
*[PMI]: Project Management Institute