ITS PRO Project Ontology

Owned by Former user (Deleted)
Last updated: Aug 29, 2019 by Mojgan AminiVersion comment
2 min read

These are the must-have components of a good project plan:

  1. CHARTER: States the objectives of the project and key stakeholders.

  2. OBJECTS: The tangible and concrete deliverables needed to complete the project. They are described using a noun, are clear and understandable by the clients, and are a commonly repeatable item. They are things like a requirements document, one function of a software product, a reusable API, or a single server instance.

  3. MILESTONES: The key points in time that sponsors care about, the highest-level accomplishments towards the end goal. Example: Project Requirements Complete and Delivered, Online Reports Tested, Product Deployed and Operational.

  4. TASKS: The action required to produce the deliverable. Tasks are described using a verb and include specific details like who is responsible for the work, how long it will take, and when it will be done. Examples of specific tasks: Modify firewall on vlan 121 to allow ssh traffic, Send scope document draft to project team for review and feedback.

Here’s an example of what an Object and its associated tasks could look like:

Object

Task

Object

Task

Scope Document for Data Center Migration project

Document all systems and services that need to be migrated by asking the subject matter expert (SME)



Create initial scope document draft



Send scope document draft to project team for review and feedback



Review and integrate feedback



Send scope document to Sr. Leadership team to review and sign-off



Publish final version of scope document

To get a better understanding of the ITS Project Ontology, watch this short introduction video, courtesy of Kal: 8-minute Project Ontology video

Recommended Approach for the Project

When either entering or evaluating projects and their ontology, this is the recommend order of thought:

  1. Project charter: Obtain and understand the purpose and value of the project

  2. Object list: Define all deliverables in easy-to-undertand terms

  3. Task list: Determine specifically what needs to be done to deliver the objects, meet the project goals.

  4. Staff list: Identify project team members, their roles in the project

  5. Milestone list: Identify the key points in the project that are important to stakeholder/clients.

When preparing a project plan, first ensure the charter is assembled and then enumerate an object list for the project without any regard for tasks, etc. It should be a simple list of just objects, clearly worded, and their assigned Object Types, nothing else.

The next step is to determines what phases will be needed for the project in a simple and separate list.

Then the project team list should be determined, along with their roles. They represent who will enter time on the project and what roles each person will take.

Finally, the task list is assembled, combining (and assigning each to a task):

  • The staff list

  • The milestone list

  • The object list

  • The phases

The idea behind this recommended, step-by-step approach is to illustrate that breaking down the project into clear parts is the essence of good project management.

Resources: