Project Management – Process

Project Management – Process

Purpose

The Process defines how projects are structured, executed, and governed within the Project Management module.
It acts as the blueprint that determines the project methodology, enabled features, work item structure, reporting capabilities, and overall behavior of a project throughout its lifecycle.

By using Processes, organizations ensure consistency, governance, and methodological alignment across projects while still allowing flexibility for different delivery models such as Waterfall, Agile, or Hybrid.

Access Path

Control center → Project Management → Process

From this area, authorized users can:

• View existing project processes
• Create new processes
• Configure features, summaries, and work item rules
• Maintain standardized delivery models across the organization

What Is a Project Process?

A Project Process is a predefined configuration that defines:

• The methodology (Waterfall, Agile, Hybrid)
• Which project features are available
• How work items are structured and tracked
• Which KPIs, dashboards, and summaries are displayed
• How risks, billing, milestones, sprints, and resources are managed

Every project must be associated with one process, and this selection directly controls what users can see and do inside the project.

Process Landing Page

The Process landing page displays all available project processes.

Key information includes:

• Process Name
• Methodology (Agile, Waterfall, Hybrid)
• Visibility of active and deleted processes

Available actions:

• Add a new project process
• Open and review an existing process
• Export the list
• Filter and sort by attributes
• Include or exclude deleted processes

This page is typically managed by administrators or PMO roles.

Creating a Project Process

To create a new process, select Add Project Process.

Core Fields

• Name (required)
  Descriptive name of the process (e.g., Hybrid – Architecture Studio).

• Methodology (required)
  Defines the high-level delivery model:

  • Waterfall

  • Agile

  • Hybrid

• Company
  Defines whether the process is tenant-wide or company-specific.

Once saved, the process becomes available for selection during project creation.

Project Process Configuration

Opening a process displays the Project Process Details, organized into four main areas.

1. Process (General Settings)

This section defines the core identity and risk configuration of the process:

• Process name
• Company scope
• Methodology
• Impact Score model used for risk evaluation

These settings establish the foundation for how risks and governance are applied in projects using this process.

2. Features

The Features tab controls which functional areas are enabled inside projects created with this process.

Examples of configurable features include:

• Work Items

  • Tree view

  • Timeline (Gantt)

  • Board (Kanban)

  • Calendar view

• Resource Management

  • Resource Manager

  • Sourcing

  • Effort inheritance (typical for Waterfall)

• Project Controls

  • Baselines

  • Milestones

  • Risks

  • Stakeholders

  • Commercials

  • Billing Plan

  • Sprints

Each feature can be enabled or disabled independently, allowing processes to be tailored for different delivery needs.

Some features include additional parameters, such as:

• Notification lead times (e.g., for billing or milestones)

3. Summary

The Summary tab defines which dashboards, charts, and KPIs are displayed in the project’s Summary view.

Available summaries include:

• Margin summary (base, target, actual)
• Progress summary and trends
• Resource effort breakdown
• Budget consumption
• Revenue recognition
• Work item deadlines
• Upcoming unclosed risks
• Burnup and burndown charts

These summaries provide real-time insight into project health and performance.
Only enabled summaries appear in projects using this process.

4. Work Item Types

The Work Item Types tab defines:

• Which work item types are allowed (e.g., Phase, Task, Custom types)
• Which statuses are available for each type

For example:

• Phases: New → In Progress → Done
• Tasks: New → In Progress → Blocked → Done

This configuration ensures:

• Consistent workflows
• Clear progress tracking
• Methodology-aligned execution

Only the defined work item types and statuses can be used in projects associated with this process.

How Processes Are Used in Projects

When creating a project, selecting a process automatically:

• Enables the configured features and tabs
• Defines available work item structures
• Controls billing, risks, milestones, and resource management
• Activates specific dashboards and KPIs
• Applies governance and reporting rules

Once a project is created, changing the process is typically restricted, as it would impact structure and data integrity.

Best Practices

• Design processes before creating projects
• Use separate processes for different methodologies or business units
• Keep processes standardized but minimal
• Enable only the features that are truly required
• Align work item types with real delivery practices
• Review summary dashboards to ensure meaningful KPIs

Related Articles

Project Management – Projects (Overview)
Project Management – Create a Project
Project Management – Manage Project Information
Project Management – Work Items
Project Management – Milestones
Project Management – Billing Plan
Project Management – Risks
Project Management – Commercials