Project Management – Processes & Features

Purpose

Project Processes define how projects are structured, executed, and governed within the Project Management module.

A process acts as a blueprint that determines:

The project methodology (Waterfall, Agile, Hybrid)
Which features are available during project execution
How work items behave
What KPIs, summaries, and dashboards are shown

By configuring processes centrally, organizations ensure consistency, scalability, and alignment with delivery standards.

Access Path

Control Center → Project Management → Process

This area is part of Project Management parametrization and is typically managed by administrators or PMO roles.

Process Landing Page

The Process landing page lists all available project processes.

For each process, users can see:

Process Name
Methodology (Agile, Waterfall, Hybrid)
Company (Defines whether the process is tenant-wide or company-specific.)

Available actions include:

Add a new project process
Open an existing process
Refresh the list
Include deleted processes
Export process data
Customize visible columns

This page provides a centralized overview of all delivery models supported by the organization.

What Is a Project Process?

A Project Process defines the operational rules of a project, including:

How work is planned and tracked
Which project tabs are available
How progress, costs, and risks are calculated
Which work item types and statuses are allowed
Whether Agile elements such as sprints and backlogs are enabled

Once assigned to a project, the process controls the entire project lifecycle.

Creating a Project Process

Select Add Project Process to create a new one.

Core Fields

Name
Unique identifier for the process (e.g., Hybrid – Architecture Studio).
Methodology
Defines the high-level delivery approach:
- Waterfall
- Agile
- Hybrid
Company
Defines whether the process is tenant-wide or company-specific.

After saving, the process can be fully configured through detailed tabs.

Process Configuration Tabs

Each process is configured using four main tabs:

Process
Features
Summary
Sprint Events
Work Item Types

Together, these define how projects behave operationally and visually.

Process Tab

The Process tab defines the identity and core behavior of the process.

Key elements include:

Process name
Assigned company
Methodology
Risk impact scoring model

This tab establishes the foundation for all other configurations.

Features Tab

The Features tab controls which functional capabilities are available in projects using this process.

Work Item Visualization

Tree view
Timeline (Gantt)
Board (Kanban)
Calendar

Planning & Control

Baselines (planning snapshots)
Work item inheritance (parent–child rollups)
Associate services with work items
Hide service cost (for controlled visibility)

Governance & Financials

Risks
Stakeholders
Commercials
Milestones
Billing Plan (with notification lead time)

Agile Capabilities

Sprints
Backlogs

Enabling or disabling features directly affects which tabs and tools appear inside projects.

Summary Tab

The Summary tab defines which KPIs, charts, and analytical widgets are available in the project Summary screen.

Available summaries include:

Resource effort breakdown
Effort deviation
Margin summary (with upper and lower thresholds)
Progress summary
Progress trend
Expenses summary
Work item deadlines
Work distribution summary
Upcoming unclosed risks
Burndown and burnup charts
Revenue recognition
Budget consumption

Each toggle controls visibility of a specific insight, allowing dashboards to match the methodology and governance level.

Sprint Events Tab

The Sprint Events tab is available for Agile and Hybrid methodologies.

It defines:

Sprint iteration length
Working days
Daily meeting schedule
Sprint planning sessions
Sprint review sessions
Retrospective sessions

Each event can be:

Enabled or disabled
Scheduled on specific days
Configured with a fixed duration

This ensures Agile ceremonies are standardized across projects.

Work Item Types Tab

The Work Item Types tab defines:

Which work item types are allowed
Which statuses are available for each type

Examples include:

Phase
Task
Subtask
Issue

Each type has its own lifecycle, ensuring consistency in execution and reporting.

This configuration directly affects:

Work item creation
Progress tracking
Status-based KPIs
Board and timeline behavior

How Processes Are Used in Projects

When creating a project, selecting a process determines:

Which tabs are visible
How work is structured
Which KPIs are calculated
Whether Agile or Waterfall controls apply

Once a project is created, the process cannot be changed lightly, as it defines structural behavior.

Best Practices

Create standardized processes for common delivery models
Limit the number of active processes to avoid complexity
Enable only features that are truly needed
Align summary KPIs with governance requirements
Test processes with pilot projects before broad rollout

What’s Next

After configuring project processes, teams typically move on to:

Creating projects using the defined processes
Structuring work items and milestones
Managing sprints and backlogs
Tracking progress, risks, and financials

Project Management – Projects (Overview)
Project Management – Create a Project
Project Management – Manage Project Information
Project Management – Work Items
Project Management – Manage Sprints
Project Management – Manage Backlogs
Project Management – Milestones
Project Management – Billing Plan
Project Management – Track Project Progress & KPIs

Project Management – Processes & Features