A Project is a coordinated body of work with its own scope, participants, tasks, and deliverables. It connects the records needed to manage a development initiative and gives the team a common context for execution.
When to use it
- Use it for an initiative that needs coordinated planning and delivery.
- Use it when tasks, milestones, participants, and deliverables should be organized around the same body of work.
Key information
- Purpose: project ID, name, description, scope, and deliverables.
- Management: owner, manager, leader, budget, and priority.
- Delivery: estimated dates, due date, completion percentage, and actual dates.
Common relationships
- Project – Task connects the project to its activities.
- Milestone connects the project to important events or achievements.
- Project Members identifies the people participating in the project.
Working with this record
Define the scope before adding work. Connect relevant tasks and deliverables, identify participants, and review progress against the project’s dates and milestones. Use Subproject when a related body of work needs its own project record.
Example
Pump Redesign is a Project with tasks for the housing update and validation review. Prototype Ready is its Milestone. The participating engineers are connected as Project Members, and the project provides a shared context for their work.
Choosing the right type
Choose Project for coordinated execution. Choose Product for the offering being developed and Task for a single activity. A project can support a product without replacing the product or its engineering definition.
