Projects are used to organize a specific activity. They can control the use of resources and associated costs, so they are used appropriately in order to successfully achieve the project's goals. Related projects can be organized into campaigns. Small items of work, typically performed by a single person, can be defined as tasks for a project.
Notice that the project acts as an anchor for collections of resources that the project is using. Since it is a Referenceable, it can have links to external URLs, such as the project home page, project plan or APIs as well as images (see 0015 Linked Media Types in Area 0).
The project entity represents a single project. It inherits from Referenceable and includes attributes for defining the timeframe for the project and its status.
The Campaign classification describes a collection of related projects that are working towards a common goal. Often this goal is a complex transformation that needs actions from independent teams. The definition of the campaign helps to identify the role of the different projects in achieving the common goal, and providing the umbrella for coordinating specific activities as needed.
A campaign classification is typically attached to either:
- a Collection entity whose members are the related projects.
- a Project entity where the related projects are linked by the ProjectHierarchy relationship.
The Task classification is attached to a Project entity to indicate that this entity represents a small piece of work that is typically assigned to a single person (identified via the ProjectTeam relationship). Such a task is linked to a parent project via the ProjectHierarchy relationship.
The PersonalProject classification is attached to a Project entity to indicate that this entity represents an informal project that has been created by single person (identified via the ProjectTeam relationship) to help organize a part of their work. These projects are typically not linked to into a project hierarchy. They may be linked to other project entities via the ProjectDependency relationship.
Personal projects do not typically have a Project Manager assigned.
Projects can be broken down into smaller projects that can be executed by different teams on different timelines with different project manager(s) and a specific slice of the budget. The projects that are broken down in this way are linked together using the ProjectHierarchy relationship.
A project that needs the results of another project to complete its work can be linked to that project via the ProjectDependency relationship.
The ProjectTeam relationship links a project to the Actors that will perform the work defined by the project.
The ProjectManagement relationship links a project to the PersonRole entity that will coordinate and track the efforts of the project team. The role in turn links to the individual(s) appointed to perform the role.
- ProjectScope relationship is deprecated in favour of the more generic AssignmentScope. The description attribute of the AssignmentScope relationship should be used instead of the scopeDescription in the ProjectScope relationship; the scopeDescription attribute has been deprecated.
- status attribute on Project is deprecated in favour of the more specific projectStatus attribute, which makes it easier to align with an appropriate valid value set.
Raise an issue or comment below