Project Management - Process (Overview)

Project Management – Process (Overview)

Module

Control Center → Project Management

The Process feature within Project Management defines how projects are planned, executed, tracked, and governed across the organization.

A Project Process acts as a blueprint that determines:

• The project methodology (Waterfall, Agile, or Hybrid)
• Which capabilities are available during execution
• How work items behave and progress
• Which metrics, summaries, and controls are visible

By configuring project processes, organizations ensure consistency, governance, and alignment between project delivery, reporting, and decision-making.

Access Path

Control Center → Project Management → Process

1. Purpose of Project Processes

Project Processes allow organizations to:

• Standardize project execution across teams and departments
• Support different delivery methodologies (Agile, Waterfall, Hybrid)
• Enable or restrict specific project features
• Control how work items are structured, tracked, and reported
• Align operational execution with governance and analytics

Each project created in the system is associated with one Process, which defines its behavior throughout its lifecycle.

2. What Is a Project Process?

A Project Process is a configurable entity that combines:

• Methodology
  Defines the overall delivery approach (e.g., Waterfall, Agile, Hybrid).

• Features
  Determines which project capabilities are available (e.g., Gantt, Boards, Risks, Commercials).

• Work Item Rules
  Controls which work item types are used and which statuses apply to each type.

• Summary & Analytics
  Defines which dashboards, charts, and indicators are visible in the project.

Together, these elements form a complete operational framework for managing projects.

3. Supported Methodologies

Project Processes support multiple methodologies:

• Waterfall
  Sequential planning, strong dependency management, and hierarchical work item inheritance.

• Agile
  Iterative execution using boards, sprints, and backlogs.

• Hybrid
  Combines structured planning with agile execution elements.

The selected methodology influences which features are typically enabled, but all configurations remain fully customizable.

4. Process Configuration Areas

Each Project Process is configured through several tabs, each addressing a specific aspect of project behavior.

4.1 Process (Core Definition)

Defines the identity and scope of the process:

• Name
• Company scope (Tenant-wide or company-specific)
• Methodology
• Impact scoring model

This establishes the foundational rules for projects using this process.

4.2 Features

Controls which capabilities are available inside projects, such as:

• Work item visualizations (Tree, Timeline, Board, Calendar)
• Resource management and sourcing
• Risks, stakeholders, and milestones
• Commercials, billing plans, and budgeting
• Agile features like sprints and backlogs

Enabling or disabling features directly affects how users interact with projects.

4.3 Summary

Defines which analytical components are visible in project dashboards, including:

• Progress and effort tracking
• Financial summaries (margin, budget, revenue)
• Risk and deadline monitoring
• Work distribution and performance trends

These summaries support operational and management-level decision-making.

4.4 Work Item Types

Defines:

• Which work item types are used (e.g., Timeline, Phases, Tasks, Issues)
• Which statuses are allowed for each type
• How work progresses across different levels of the project structure

This ensures consistency between planning, execution, and reporting.

5. Usage in Projects

Once configured, a Project Process can be:

• Assigned when creating a project
• Used as a company or tenant standard
• Reused across multiple projects

All projects using the same process will share:

• The same structure
• The same feature set
• The same reporting capabilities

This guarantees predictable behavior and comparable results across the portfolio.

6. Governance and Flexibility

Project Processes balance standardization and flexibility:

• Organizations define global or company-specific standards
• Teams work within clearly defined boundaries
• Processes can evolve without impacting historical projects

This approach supports scalability, governance, and continuous improvement.

Related Articles

Project Management – Milestones Status
Project Management – Work Items Status
Project Management – Risk Status 
Project Management – Initial Setup