Project Tracking

The Project Tracking module supports the structured intake, planning, execution, and control of work across initiatives of any size. It enables organizations to capture proposed work, formally manage approved projects, plan delivery using backlogs and iterations, and execute work through categorized work items aligned to defined roles and resource assignments.

Using the Module

The project lifecycle typically begins when work is proposed through Project Requests, which represent intake records capturing initial business need, justification, high-level scope, and evaluation prior to formal project approval. Requests can document proposed project names and descriptions, reference organization initiatives providing strategic alignment, specify requesting organization units and requesters, track request dates and priorities, estimate proposed budgets and timelines, reference supporting documentation, and progress through review and approval workflows before transitioning to formal projects.

When a project request is approved, a Project can be created to serve as the primary delivery record for the defined body of work. Projects can document project codes, names, and descriptions, reference parent projects for hierarchical program structures, link to organization initiatives and legal authorities, specify project sponsors, business owners, and project managers, assign owning organization units and delivery organizations, track approved budgets, planned effort, and cost actuals, define baseline and actual start and end dates, monitor project status, health, and completion percentage, capture assumptions, constraints, and success criteria, reference project charters and supporting documentation, and link to agreements or contracts governing the work.

To support project execution, Project Roles can be defined to represent standardized roles used within projects such as Project Manager, Business Lead, Technical Lead, Developer, Tester, or Subject Matter Expert. Roles can support consistent staffing structures and reporting. Project Resource Assignments can then be created to assign persons or resources to projects, specifying the assigned role, allocation percentage, assignment start and end dates, planned effort hours, and optional assignment to specific work items or phases.

Projects can organize work through Project Backlogs, which represent planning containers that group and prioritize future work items before assignment to execution phases. Backlogs can be categorized by backlog type such as product backlog, sprint backlog, release backlog, or feature backlog, track backlog status and ownership, and link to specific iterations when work is pulled into execution. Project Iterations can represent defined timeboxes or execution cycles within a project such as sprints, phases, or increments. Iterations can specify iteration names and numbers, define start and end dates, link to parent backlogs, establish hierarchical relationships for nested iterations, track iteration goals and completion status, and organize work items scheduled for completion during the period.

Work execution can be managed through Project Work Item Types, which define categories of work items such as Epic, Feature, User Story, Task, Defect, or Change Request. Work item types can control classification, reporting, and workflow behavior. Project Work Items can then be created to represent core execution records for units of work within the project. Work items can reference their work item type, specify titles and descriptions, track work item status and priority, assign to persons or teams, estimate and record effort hours, define parent-child relationships for hierarchical decomposition, link to project backlogs and iterations, reference associated milestones, attach supporting documentation, and connect to risk items when work involves identified risks.

Projects can establish timeline checkpoints through Project Milestones, which represent significant events or delivery dates such as key deliverables, approvals, or completion markers. Milestones can document milestone names and descriptions, specify planned and actual dates, track milestone status and achievement, link to deliverable work items, establish hierarchical milestone relationships, and reference supporting documentation. When approved project baselines require modification, Project Change Requests can be created to formally propose changes to scope, schedule, cost, deliverables, or other baseline elements. Change requests can document change descriptions and justifications, assess impact on scope, schedule, and budget, track review and approval status, specify implementation dates, and reference supporting impact analysis documentation. This integrated approach enables organizations to manage IT implementations, policy initiatives, construction projects, product development, operational improvements, research programs, or any structured body of work requiring visibility, accountability, and controlled delivery from initiation through completion.

graph TD
  appbase_Agreement(Agreement)
  appbase_Document(Document)
  appbase_LegalAuthority(Legal Authority)
  appbase_OrganizationInitiative(Organization Initiative)
  appbase_Project(Project)
  appbase_ProjectBacklog(Project Backlog)
  appbase_ProjectChangeRequest(Project Change Request)
  appbase_ProjectIteration(Project Iteration)
  appbase_ProjectMilestone(Project Milestone)
  appbase_ProjectRequest(Project Request)
  appbase_ProjectResourceAssignment(Project Resource Assignment)
  appbase_ProjectRole(Project Role)
  appbase_ProjectWorkItem(Project Work Item)
  appbase_ProjectWorkItemType(Project Work Item Type)
  appbase_RiskItem(Risk Item)
  appbase_Project --> appbase_Agreement
  appbase_Project --> appbase_Document
  appbase_Project --> appbase_Document
  appbase_ProjectChangeRequest --> appbase_Document
  appbase_ProjectMilestone --> appbase_Document
  appbase_ProjectRequest --> appbase_Document
  appbase_ProjectWorkItem --> appbase_Document
  appbase_Project --> appbase_LegalAuthority
  appbase_Project --> appbase_OrganizationInitiative
  appbase_ProjectRequest --> appbase_OrganizationInitiative
  appbase_Project --> appbase_Project
  appbase_ProjectBacklog --> appbase_Project
  appbase_ProjectChangeRequest --> appbase_Project
  appbase_ProjectIteration --> appbase_Project
  appbase_ProjectMilestone --> appbase_Project
  appbase_ProjectRequest --> appbase_Project
  appbase_ProjectResourceAssignment --> appbase_Project
  appbase_ProjectWorkItem --> appbase_Project
  appbase_ProjectWorkItem --> appbase_ProjectBacklog
  appbase_ProjectBacklog --> appbase_ProjectIteration
  appbase_ProjectIteration --> appbase_ProjectIteration
  appbase_ProjectWorkItem --> appbase_ProjectIteration
  appbase_ProjectMilestone --> appbase_ProjectMilestone
  appbase_Project --> appbase_ProjectRequest
  appbase_ProjectResourceAssignment --> appbase_ProjectRole
  appbase_ProjectMilestone --> appbase_ProjectWorkItem
  appbase_ProjectWorkItem --> appbase_ProjectWorkItem
  appbase_ProjectWorkItem --> appbase_ProjectWorkItemType
  appbase_ProjectWorkItem --> appbase_RiskItem

The Project Tracking module supports the structured intake, planning, execution, and control of work across initiatives of any size. It enables organizations to capture proposed work through Project Requests, formally manage approved Projects, plan delivery using Backlogs and Iterations, and execute work through categorized Work Items aligned to defined Roles and Resource Assignments. Milestones provide timeline checkpoints, while Change Requests ensure formal governance over scope, schedule, and cost adjustments. This module can be used for IT system implementations, policy initiatives, construction efforts, product development, operational improvements, research programs, or any structured body of work requiring visibility, accountability, and controlled delivery from initiation through completion.

Tables

Project Request

Represents an intake record used to propose or initiate a new project. Captures initial business need, justification, high-level scope, and evaluation prior to formal project approval.

Project

Represents the primary delivery record for a defined body of work with scope, objectives, schedule, ownership, and overall status. Serves as the parent container for backlog items, iterations, milestones, resources, and change requests.

Project Role

Represents standardized roles used within projects (e.g., Project Manager, Business Lead, Technical Lead). Supports consistent staffing structures and reporting.

Project Resource Assignment

Represents the assignment of a person or resource to a project (and optionally to specific work items), including role, allocation percentage, and assignment duration.

Project Backlog

Represents a planning container that groups and prioritizes future work items for a project. Used to manage the queue of pending work before assignment to an iteration or execution phase.

Project Iteration

Represents a defined timebox or execution cycle within a project (e.g., sprint, phase, increment). Used to organize and track work items scheduled for completion during that period.

Project Work Item Type

Represents the configuration table defining categories of work items (e.g., Epic, Feature, Task, Defect). Controls classification, reporting, and workflow behavior for Project Work Items.

Project Work Item

Represents the core execution record for a unit of work within a project. May represent an epic, feature, task, defect, or other work category as defined by its type.

Project Milestone

Represents a significant event or checkpoint within a project timeline. Represents key delivery dates, approvals, or completion markers used for progress tracking and reporting.

Project Change Request

Represents a formal proposal to modify approved project scope, schedule, cost, deliverables, or other baseline elements. Tracks impact analysis, review, approval decision, and implementation status.

Note: All data shown in screenshots is fictitious and for demonstration purposes only.

Use the pac data CLI command or the Configuration Migration tool to import sample data into your environment.

No guides are available for this solution yet.