Purpose
The Project Process defines how projects are structured, configured, and managed within the Project Management module.
It acts as a reusable blueprint that determines:
- The project methodology
- The features available within the project
- The information displayed in the project summary
- The available Work Item views and behaviours
- The Work Item Types and their permitted statuses
- The configuration of Sprint Events
By creating standardized Project Processes, organizations can apply consistent delivery methods and governance rules across multiple projects while supporting different methodologies, such as Waterfall, Agile, and Hybrid.
Access Path
Control Center → Project Management → Process
From this area, authorized users can:
- View existing Project Processes
- Create a new Project Process
- Review or edit an existing configuration
- Define the features available in projects
- Configure Project Summary components
- Define Work Item behaviour, types, and statuses
- Configure Sprint Events
- Delete a Project Process
What Is a Project Process?
A Project Process is a predefined set of parameters applied to a project.
When a Project Process is selected during project creation, its configuration determines which features and management options are available in that project.
This includes:
-
Project functionality, such as risks, milestones, billing, and resource management
-
Project Summary charts, tables, and KPIs
-
Work Item views, sourcing rules, inheritance, and service settings
-
Permitted Work Item Types and statuses
-
Sprint events, schedules, and expected durations
Each Project Process can therefore be adapted to a particular delivery methodology, business area, or type of project.
Process Landing Page
The Process landing page displays the Project Processes currently configured in the system.

Each record contains:
| Column | Description |
|---|---|
| Name | Name used to identify the Project Process. |
| Methodology | Delivery methodology associated with the process: Agile, Waterfall, or Hybrid. |
| Company | Defines the company to which the Project Process belongs and where it can be applied. A tenant-wide process can be used across all companies. |
To open an existing process, select the View icon next to its name.
Available Actions
| Action | Description |
|---|---|
| Add Project Process | Creates a new Project Process. |
| Refresh | Reloads the list to display the latest information. |
| Include Deleted | Determines whether deleted Project Processes are included in the list. |
| Export | Exports the information displayed on the landing page. |
| Columns | Selects which columns are displayed in the list. |
| Filter and Sort | Filters or reorganizes the records using the available column controls. |
Creating a Project Process
To create a Project Process:
-
Select Add Project Process from the landing page.

-
Complete the initial process information.
-
Select Save or Save and New.
Initial Process Information
| Field | Description |
|---|---|
| Name | Required name used to identify the Project Process. Use a name that clearly reflects its purpose, business area, or methodology. |
| Methodology | Defines the delivery approach used by the process. The available options are Agile, Waterfall, and Hybrid. |
| Company | Defines whether the process is available tenant-wide or associated with a specific company. |
Save Options
| Action | Description |
|---|---|
| Save | Creates the Project Process and closes the creation window. |
| Save and New | Creates the Project Process and opens a new form, allowing another process to be added immediately. |
| Cancel | Closes the form without creating the Project Process. |
After the process has been created, open it from the landing page to complete its parameterisation.
Parameterising a Project Process
The Project Process Details window contains the complete process configuration.
The settings are organized into the following tabs:
-
Process
-
Summary
-
Project
-
Work Items
-
Work Item Types
-
Sprint Events
Select Edit to make changes to the current configuration. Once editing is enabled, update the required fields and activate or deactivate the relevant options.
An enabled toggle indicates that the corresponding feature or setting will be available in projects using this process.
1. Process
The Process tab contains the general information and governance settings of the Project Process.

| Field | Description |
|---|---|
| Name | Name used to identify the Project Process. |
| Company | Company to which the process belongs. A process may also be configured as tenant-wide. |
| Methodology | Delivery methodology associated with the process: Agile, Waterfall, or Hybrid. |
| Impact Score | Risk matrix used to calculate or assess the impact of project risks. |
| Proposal Allowed Status | Defines which proposal statuses are eligible for importing a proposal into a project. Selecting Any allows proposals regardless of their current status. |
These settings establish the process identity and the general rules applied to projects that use it.
2. Summary
The Summary tab determines which charts, tables, indicators, and performance summaries appear in the project’s Summary view.

Only the components enabled in this tab are made available in projects using the process.
| Summary Component | Description |
|---|---|
| Resource Effort Breakdown | Displays a chart summarizing estimated, allocated, and spent effort by resource. |
| Effort Deviation | Displays a chart comparing project effort and highlighting deviations. |
| Margin Summary | Displays cards containing the project’s Base, Target, and Actual margins. |
| Margin Status Upper Bound | Defines the upper threshold used to determine the status of the project margin. |
| Margin Status Lower Bound | Defines the lower threshold used to determine the status of the project margin. |
| Progress Summary | Displays charts summarizing overall progress and progress by type. |
| Progress Trend | Compares ideal overall progress with actual progress over time. |
| Expenses Summary | Displays charts summarizing overall project expenses and expenses by category. |
| Work Item Deadlines | Displays overdue Work Items and Work Items approaching their deadlines. |
| Work Distribution Summary | Displays the distribution of Work Items by resource, type, and status. |
| Upcoming Unclosed Risks | Displays the most significant upcoming risks that remain open. The Risks feature must also be enabled. |
| Burndown Chart | Compares the total workload with the work remaining over time. |
| Burnup Chart | Compares the total workload with the work completed over time. |
| Revenue Recognition | Displays revenue earned on a monthly basis. The Commercials feature must also be enabled. |
| Budget Consumption | Compares the project budget with estimated, allocated, and actual consumption in currency and hours. The Commercials feature must also be enabled. |
Some Summary components depend on features configured in the Project tab. Enabling a Summary component without enabling its required feature may prevent the relevant information from being displayed.
3. Project
The Project tab controls the functional areas available within projects created from the process.

| Feature | Description |
|---|---|
| Risks | Enables the identification, evaluation, and management of project threats and opportunities. |
| Stakeholders | Enables the management of internal and external people or groups involved in or affected by the project. |
| Commercials | Enables commercial information used to support project monitoring and decision-making. |
| Milestones | Enables the creation and monitoring of key project checkpoints and deliverables. |
| Milestone Notification Lead Time | Defines how many days in advance milestone notifications should be generated. |
| Billing Plan | Enables the management of the project’s billing plan and financial milestones. |
| Billing Plan Notification Lead Time | Defines how many days in advance billing-related notifications should be generated. |
| Sprints | Enables Work Items to be organized and assigned to Sprints. |
| Backlogs | Enables Work Items to be managed and prioritized in the project backlog. |
| Link With Cost Center | Automatically creates a Cost Center when a new project is created and permanently links it to that project. The Cost Center is then automatically selected for transactions, allocations, and related entries. |
| Resource Manager | Provides access to the Resource Manager tab, where project resource information can be viewed and configured. |
| Show Project Costs | Enables the configuration of project cost items, such as taxis, hotels, and other project-related expenses. |
The features enabled here directly determine which management areas users can access within the project.
4. Work Items
The Work Items tab defines how Work Items can be visualized and managed within projects using the process.

Work Item Views
| Setting | Description |
|---|---|
| Work Items – Tree | Enables the hierarchical Tree view for Work Items. |
| Work Items – Timeline | Enables the Gantt-style Timeline view for Work Items. |
| Work Items – Board | Enables the Kanban Board view for Work Items. |
| Work Items – Calendar | Enables Work Items to be displayed in a Calendar view. |
Multiple views can be enabled, allowing users to manage the same Work Items from different perspectives.
Work Item Behaviour
| Setting | Description |
|---|---|
| Sourcing | Enables users to be sourced according to criteria defined in the Work Items. |
| Baseline | Enables snapshots of Work Item planning to be stored and compared over time. |
| Associate Service with Work Item | Allows predefined services to be linked to Work Items and their associated costs to be calculated. |
| Work Items’ Inheritance | Allows parent Work Items to inherit dates, resources, and effort from their child items. This is particularly useful for Waterfall processes. |
| Hide Service Cost | Hides the unit cost of a service from users. |
| Disable Work Item User Selection | Prevents users from being selected manually in Work Item assignments. This can be used when assignments should only be completed through Sourcing. |
| Allow Sell Price Modification | Allows users to change an assignment’s margin and discount. When disabled, values are taken from the associated service or, for assignments imported from a proposal, from the values defined in that proposal. |
The options selected in this tab should reflect how the organization intends to plan, assign, price, and monitor project work.
5. Work Item Types
The Work Item Types tab determines which types of Work Items can be used and which statuses are available for each type.

For each row, configure:
| Field | Description |
|---|---|
| Type | Work Item category available in projects using the process, such as Phase, Task, or Issue. |
| Statuses | Statuses that users can assign to the selected Work Item Type. |
For example:
| Type | Possible Statuses |
|---|---|
| Phase | New, In Progress, Closed |
| Task | New, In Progress, Closed |
| Issues | New, In Progress, Closed |
This configuration ensures that each Work Item Type follows an appropriate and consistent lifecycle.
Only the Work Item Types and statuses configured in this tab are available in projects associated with the process.
6. Sprint Events
The Sprint Events tab defines the recurring events used to organize and manage Sprint-based work.

The available events are:
| Sprint Event | Description |
|---|---|
| Iterations | Defines the recurring development, review, and improvement cycle. The recommended maximum iteration duration is four weeks. |
| Daily Meeting | Defines the brief recurring meeting used to synchronize progress, plans, and blockers. |
| Planning | Defines when the team plans and prioritizes the work for a specific Sprint. |
| Review | Defines when completed work is presented or demonstrated to stakeholders. |
| Retrospective | Defines when the team reflects on the previous Sprint, identifies improvements, and optimizes its workflow. |
Configuring a Sprint Event
For each event:
-
Use the toggle to enable or disable it.
-
Select the day or days on which it should occur.
-
Enter its expected duration or recurrence value.
-
Confirm the corresponding unit, such as:
-
wk – Weeks
-
h – Hours
-
m – Minutes
-
The selected days are highlighted in the interface.
The Sprint Events configuration provides teams with a standardized schedule whenever the Project Process is used.
Editing an Existing Project Process
To update a Project Process:
- Open the Process landing page.
- Select the View icon next to the required process.
- Navigate to the tab containing the setting that needs to be updated.
- Select Edit.
- Update the fields, toggles, statuses, or event settings.
- Save the changes.
Changes to a Project Process may affect the functionality and options available to projects using that process. Existing project data and dependencies should therefore be considered before modifying an active process.
Deleting a Project Process
To delete a Project Process:
- Open the required process.
- Select Delete at the bottom of the Project Process Details window.
- Confirm the action when prompted.
Deleted processes can be displayed on the landing page by enabling Include Deleted.
Before deleting a process, confirm whether it is already associated with existing projects.
How Project Processes Are Applied
When a Project Process is assigned to a project, its configuration controls:
- The methodology followed by the project
- The project features and tabs available to users
- The Summary charts, KPIs, and tables displayed
- The available Work Item views
- Work Item sourcing, inheritance, service, and pricing behaviour
- The Work Item Types and statuses that can be used
- Sprint Events and their standard schedules
The Project Process should therefore be fully parameterised before it is assigned to new projects.
Best Practices
- Create separate processes for delivery models that require different functionality.
- Use clear process names that identify the methodology, business area, or intended purpose.
- Enable only the project features required by the delivery model.
- Ensure Summary components have their dependent Project features enabled.
- Align Work Item Types and statuses with the organization’s actual workflows.
- Use Work Item inheritance where hierarchical planning is required.
- Configure Sprint Events consistently for Agile and Hybrid processes.
- Review active process configurations before changing or deleting them.
- Test a new Project Process with a sample project before making it widely available.
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
Help Center