3 Advantages of “Deliverables” in Project Server

No Comments

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. Read More