PPM Projects
PPM Projects are the core execution units within ProBeya's portfolio management. Each project tracks methodology, lifecycle phase, health status, GxP classification, and stakeholder assignments. Projects support full CRUD operations with lifecycle transition validation and automated health computation.
Overview
Transformation programs consist of multiple interdependent projects. ProBeya's PPM project management provides structured governance with validated lifecycle transitions, automated health indicators derived from schedule variance, and stakeholder management with role-based assignments. Every project is scoped to an organization and can be linked to one or more portfolios.
Getting Started
- Navigate to PPM > Projects and click New Project.
- Enter the project name, select a methodology, and set the project type.
- Optionally assign a sponsor and project manager.
- The system auto-generates a URL-safe slug from the project name.
- Add stakeholders and begin building the WBS.
How It Works
Project Creation
When creating a project, the system auto-generates a slug from the name (lowercase, alphanumeric, hyphenated, max 100 characters). Optional foreign key fields (sponsor, project manager) accept empty strings gracefully by converting them to null.
Methodologies
Each project is associated with one methodology:
- PMBOK7 -- PMI's standard for project management
- PM2 -- European Commission's methodology
- P3Express -- Lightweight, practical approach
- Custom -- Organization-specific methodology
Project Types
Projects are categorized by purpose:
development-- New product or system developmentimprovement-- Process or capability improvementcompliance-- Regulatory requirement implementationinfrastructure-- IT or facilities infrastructureresearch-- Exploratory or R&D work
GxP Classification
For regulated industries, each project carries a GxP classification: gxp, non_gxp, or partial_gxp. This classification drives documentation requirements and gate review rigor.
Lifecycle Phase Transitions
Projects move through lifecycle phases with validated transitions. The system prevents invalid phase jumps -- for example, a project cannot skip from initiation directly to closure. If an invalid transition is attempted, the API returns a clear error message indicating the current and requested phases.
Health Status Computation
The computeHealth procedure automatically calculates a project's health status based on schedule variance:
- Green -- completion is within 5% of expected progress and risk rating is below 50
- Amber -- completion is within 15% of expected and risk is below 75
- Red -- significant schedule slippage or high risk rating
- Not started -- no actual start date recorded
The algorithm compares elapsed time against planned duration and weights the result against the project's risk rating.
Filtering and Sorting
The project list supports filtering by:
- Status:
active,on_hold,cancelled,completed - Methodology, health status, project type
- Project manager, GxP classification
- Free-text search across name and slug
Results can be sorted by name, creation date, priority, completion percentage, or health status, with configurable direction.
Deletion Behavior
Projects with stakeholders are soft-deleted (status set to cancelled). Projects with no related data are hard-deleted. This ensures referential integrity while allowing cleanup of unused projects.
Stakeholder Management
Each project supports a list of stakeholders with role assignments. Stakeholders are linked to user accounts and ordered by role. The system provides full CRUD for stakeholders:
- Add -- Assign a user with a role
- Update -- Change role or details
- Remove -- Detach a stakeholder
- List -- View all stakeholders with user details
Configuration
| Setting | Description |
|---|---|
| Methodology options | PMBOK7, PM2, P3Express, Custom |
| Health thresholds | -5% (green), -15% (amber), else red |
| Risk rating weight | Combined with schedule variance |
| Pagination | Default 50, max 100 per page |
Permissions
| Action | Required Role |
|---|---|
| Create project | PMO or Admin |
| Edit project | Project Manager, PMO, or Admin |
| Delete project | PMO or Admin |
| Compute health | Project Manager, PMO, or Admin |
| Manage stakeholders | Project Manager or Admin |
Tips & Best Practices
Run computeHealth regularly (or automate it) to keep the portfolio dashboard accurate. Health status feeds into portfolio-level KPIs.
Use the GxP classification consistently across all projects. This drives downstream behavior in gate reviews and documentation requirements.
Soft-deleted (cancelled) projects remain in the database and count toward reporting. Use the status filter to exclude them from active views.
Related Features
- WBS -- Build the work breakdown structure for each project
- Budgets & Costs -- Financial planning per project
- Risks -- Risk register linked to each project
- Gates -- Stage-gate governance for project lifecycle