Project Management – Process: Core Configuration

Project Management – Process: Core Configuration

Module

Control Center → Project Management

The Core Configuration of a Project Process defines its identity, scope, and foundational behavior.
This configuration determines how the process is recognized in the system, which methodology it follows, and how impact or risk is evaluated within projects using this process.

Every project process must have a valid core configuration before features, summaries, or work item rules can be applied.

Access Path

Control Center → Project Management → Process

1. Purpose of Core Configuration

The Core Configuration allows organizations to:

• Define standard project processes used across teams
• Control whether a process is tenant-wide or company-specific
• Assign a delivery methodology
• Link projects to impact or risk scoring models
• Establish a clear baseline for governance and reporting

This configuration acts as the anchor for all other process settings.

2. Accessing Core Configuration

From the Process landing page:

1. Navigate to Control Center → Project Management → Process

2. Select an existing process, or click Add Project Process

3. Open the Process tab (default view)

3. Core Configuration Fields

3.1 Name

Best practice:
Use clear, descriptive names (e.g., Waterfall – Company Standard, Agile – Scrum, Hybrid – Architecture Studio).

3.2 Company Scope

• Tenant-Wide: Available to all companies in the tenant
• Company-Specific: Available only within the selected company

This ensures proper governance in multi-company environments.

3.3 Methodology

Available options typically include:

• Waterfall
• Agile
• Hybrid

The selected methodology:

• Influences default feature usage
• Guides how work items are structured
• Aligns reporting and summaries with delivery style

💡Note: Methodology selection does not lock functionality; features remain configurable.

3.4 Impact Score

Impact scoring is commonly used to:

• Assess project complexity or criticality
• Support risk analysis
• Prioritize projects in the portfolio

The available values depend on configurations defined elsewhere in the Control Center.

4. Editing and Lifecycle Management

• Processes can be edited at any time by authorized users
• Changes apply to new and ongoing projects, depending on system rules
• Deleting a process may be restricted if it is already in use

💡Important:
Care should be taken when modifying tenant-wide processes, as changes may affect multiple teams.

5. Relationship with Other Process Areas

The Core Configuration works together with:

• Features – Controls project capabilities
• Summary – Defines analytics and dashboards
• Work Item Types – Controls structure and status flow

A project process is only fully operational once all areas are properly configured.

6. Recommendations

• Define a small number of standardized processes
• Use tenant-wide processes for global standards
• Use company-specific processes for specialized needs
• Align methodology choice with actual delivery practices
• Review impact scoring models regularly

Related Articles

Project Management – Process (Overview)
Project Management – Initial Setup
Project Management – Track Project Progress & KPIs
Project Management – Process: Work Item Types
Project Management – Work Items Status
Project Management – Milestones Status
Project Management – Risk  Status
Project Management – Project Creation