PM Project Management

Based on the latest RuoyiPlus backend architecture, 16 DOs / 15 Controllers, menu ID starting at 2500, building a digital project management and team collaboration system


1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus PM centers around three core pillars—Full Project Lifecycle Management, Multi-Project Collaborative Scheduling, and Project Permission and Audit—to deliver enterprise-level enhancement, achieving a complete project management loop from initiation to closure.

1.2 Module Scale

MetricValue
Data Objects (DO)16
Controllers15
Menu ID Start2500
Maven Moduleyudao-module-pm

1.3 Core Data Tables

Table NameDescription
pm_projectProject Management
pm_taskTask Management
pm_warningAlert Management
pm_costCost Management
pm_affiliatedSub-Project Management
pm_track_projectProject Tracking
pm_labelLabel Management
pm_project_memberProject Members
graph TB subgraph "RuoYiPlus PM Enhanced Architecture" subgraph "Project Layer" A1[Project Initiation] A2[Project Planning] A3[Project Execution] A4[Project Monitoring] A5[Project Closure] end subgraph "Capability Layer" B1[WBS Work Breakdown] B2[Gantt Chart] B3[Milestone Management] B4[Resource Scheduling] B5[Risk Management] end subgraph "Collaboration Layer" C1[Task Collaboration] C2[Timesheet Management] C3[Document Management] C4[Communication Collaboration] end subgraph "Control Layer" D1[Project Permissions] D2[Data Isolation] D3[Operation Audit] D4[Compliance Reports] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3 D3 --> D4

1.4 Capability Comparison

DimensionYudao Native CapabilityRuoYiPlus PM Enhanced
Project ManagementBasic project informationFull lifecycle management
Task ManagementSimple tasksWBS decomposition + dependency relationships
Progress ControlNoneGantt chart + milestones + critical path
Resource ManagementNoneResource scheduling + timesheet management
Risk ManagementNoneRisk identification + response strategies
Data AnalysisNoneProject health score + efficiency analysis
Permission ControlBasic permissionsProject-level data permissions
Audit ComplianceSimple logsFull-chain project audit

2. Full Project Lifecycle Management

2.1 Lifecycle Phases

graph LR A[Initiation Phase] --> B[Planning Phase] B --> C[Execution Phase] C --> D[Monitoring Phase] D --> E[Closure Phase] A --> A1[Requirements Analysis] A --> A2[Feasibility Assessment] A --> A3[Project Initiation Approval] B --> B1[WBS Decomposition] B --> B2[Schedule Planning] B --> B3[Resource Planning] B --> B4[Risk Planning] C --> C1[Task Assignment] C --> C2[Task Execution] C --> C3[Timesheet Reporting] C --> C4[Progress Reporting] D --> D1[Progress Monitoring] D --> D2[Deviation Analysis] D --> D3[Change Management] D --> D4[Risk Alert] E --> E1[Acceptance Review] E --> E2[Lessons Learned] E --> E3[Project Archiving]

2.2 Project Data Permissions

The PM system implements data permission control based on projects and roles, ensuring strict isolation of project data by organizational structure.

Permission LevelScopeDescription
Project MemberParticipating projectsCan only view and participate in assigned projects
Project ManagerResponsible projectsCan manage all project data, including task assignment and progress adjustment
Department ManagerDepartment projectsCan view progress and resources of all department projects
PMOAll projectsCan view all project data and perform portfolio analysis
// PM Data Permission Example
@DataPermission(scope = "project")
public class ProjectServiceImpl {
    // Project managers can manage all data of their projects
    // Automatically filter tasks, timesheets, documents by project
}

// Project Member Permission
@DataPermission(roles = {"project_member"})
public class TaskServiceImpl {
    // Project members can only view their own tasks
    // Automatically filter by task assignee
}

2.3 Project Operation Audit

All key project operations record complete audit logs, supporting project process traceability.

graph TB subgraph "Audit Event Collection" A1[Project Initiation] A2[Plan Change] A3[Task Assignment] A4[Progress Adjustment] A5[Milestone Change] A6[Project Closure] end subgraph "Audit Processing" B1[Change Comparison] B2[Risk Scoring] B3[Rule Matching] end subgraph "Audit Storage" C1[Operation Logs] C2[Change History] C3[Blockchain Notarization] end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 A6 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 B3 --> C2 B3 --> C3
Audit ItemDescriptionRetention Period
Project InitiationRecords initiator, initiation time, project objectivesPermanent
Plan ChangeRecords before/after comparison, change reasonProject lifecycle + 3 years
Task AssignmentRecords assigner, assignee, assignment timeProject lifecycle + 3 years
Progress AdjustmentRecords before/after duration, adjustment reasonProject lifecycle + 3 years
Milestone ChangeRecords change content, approverPermanent
Project ClosureRecords closure time, acceptance resultsPermanent

3. WBS Work Breakdown and Task Management

3.1 WBS Breakdown Structure

graph TB subgraph "WBS Work Breakdown" A[Project] --> B[Phase 1] A --> C[Phase 2] A --> D[Phase 3] B --> B1[Task 1.1] B --> B2[Task 1.2] B --> B3[Task 1.3] C --> C1[Task 2.1] C --> C2[Task 2.2] D --> D1[Task 3.1] D --> D2[Task 3.2] D --> D3[Task 3.3] B1 --> B1a[Sub-task 1.1.1] B1 --> B1b[Sub-task 1.1.2] end

3.2 Task Management

CapabilityDescription
Task CreationTask definition, priority, duration estimation
Task AssignmentIntelligent assignment by skill/load
Task DependenciesFS/FF/SS/SF dependency relationships
Sub-tasksMulti-level sub-task decomposition
Task BoardKanban view, list view
Task RemindersDue reminders, overdue alerts

3.3 Task Status Flow

graph LR A[To Do] --> B[In Progress] B --> C[Pending Acceptance] C --> D[Completed] B --> E[Blocked] E --> B C --> F[Acceptance Failed] F --> B D --> G[Closed]

4. Progress Control

4.1 Gantt Chart

gantt title Project Progress Gantt Chart Example dateFormat YYYY-MM-DD section Requirements Phase Requirements Analysis :a1, 2024-01-01, 15d Requirements Review :a2, after a1, 5d section Design Phase High-Level Design :b1, after a2, 10d Detailed Design :b2, after b1, 15d Design Review :b3, after b2, 5d section Development Phase Coding :c1, after b3, 30d Unit Testing :c2, after c1, 10d section Testing Phase Integration Testing :d1, after c2, 15d Acceptance Testing :d2, after d1, 10d section Go-Live Phase Deployment :e1, after d2, 5d

4.2 Milestone Management

graph LR A[Milestone 1: Requirements Confirmed] --> B[Milestone 2: Design Complete] B --> C[Milestone 3: Development Complete] C --> D[Milestone 4: Testing Passed] D --> E[Milestone 5: Official Launch] A -.-> A1[Plan: 01-20] B -.-> B1[Plan: 02-15] C -.-> C1[Plan: 03-30] D -.-> D1[Plan: 04-20] E -.-> E1[Plan: 05-01]
CapabilityDescription
Milestone SettingKey node definition and marking
Progress TrackingReal-time milestone completion tracking
Deviation AlertAutomatic alert for milestone delays
Change ManagementMilestone changes require approval workflow

4.3 Critical Path Analysis

graph TB A[Task A: 10d] --> C[Task C: 15d] C --> E[Task E: 10d] A --> D[Task D: 5d] D --> F[Task F: 8d] F --> E B[Task B: 20d] --> E style A fill:none style C fill:none style E fill:none style B fill:none

Critical path: B -> E = 30 days (minimum project duration)


5. Resource and Timesheet Management

5.1 Resource Scheduling

graph TB subgraph "Resource Scheduling" A[Resource Demand] --> B{Resource Matching} B --> C[Skill Matching] B --> D[Load Assessment] B --> E[Availability Check] C --> F[Resource Allocation] D --> F E --> F F --> G[Conflict Detection] G --> H{Conflict?} H -->|Yes| I[Resource Coordination] H -->|No| J[Confirm Allocation] I --> J end

5.2 Timesheet Management

CapabilityDescription
Timesheet ReportingReport daily hours by task
Timesheet ApprovalTimesheet approval workflow
Timesheet StatisticsIndividual/team/project timesheet statistics
Timesheet AnalysisUtilization rate, overtime analysis
Cost AccountingLabor cost accounting based on timesheets
pm:
  timesheet:
    rules:
      daily-max: 24h          # Maximum daily hours
      weekly-max: 60h         # Maximum weekly hours
      approval-required: true  # Approval required
      overtime-threshold: 8h   # Overtime threshold
    cost:
      hourly-rate: 200         # Default hourly rate
      overtime-multiplier: 1.5 # Overtime multiplier

6. Risk Management

6.1 Risk Management Process

graph TB subgraph "Risk Management" A[Risk Identification] --> B[Risk Assessment] B --> C[Risk Classification] C --> D[Response Strategy] D --> E[Risk Monitoring] E --> F{Risk Occurred?} F -->|Yes| G[Emergency Response] F -->|No| E G --> H[Risk Closure] end

6.2 Risk Classification

Risk LevelImpactOccurrence ProbabilityResponse Requirement
Critical RiskProject haltedHigh probabilityImmediate response plan
High RiskSevere delayRelatively high probabilityResponse plan within 3 days
Medium RiskPartial impactMedium probabilityPreventive measures within 1 week
Low RiskMinor impactLow probabilityContinuous monitoring

7. Project Data Analysis

7.1 Project Health Score

graph TB subgraph "Project Health Assessment" A[Schedule Deviation] --> E[Health Score] B[Cost Deviation] --> E C[Quality Metrics] --> E D[Risk Status] --> E E --> F{Health Level} F -->|>=90| G[Green - Healthy] F -->|70-89| H[Yellow - Attention] F -->|<70| I[Red - Alert] end

7.2 Analysis Dimensions

Analysis DimensionMetrics
Progress AnalysisPlanned completion rate, milestone achievement rate, schedule deviation rate
Resource AnalysisResource utilization rate, timesheet distribution, load balance
Cost AnalysisBudget execution rate, labor cost, deviation analysis
Quality AnalysisDefect density, rework rate, acceptance pass rate
Efficiency AnalysisTask completion efficiency, team collaboration efficiency

8. Multi-Project Management (PMO)

8.1 PMO View

graph TB subgraph "PMO Multi-Project Management" subgraph "Project Portfolio" A1[Strategic Project A] A2[Strategic Project B] A3[Regular Project C] A4[Regular Project D] end subgraph "Resource Pool" B1[Development Resource Pool] B2[Testing Resource Pool] B3[Design Resource Pool] end subgraph "PMO Control" C1[Project Priority] C2[Resource Coordination] C3[Portfolio Analysis] C4[Health Monitoring] end end A1 --> C1 A2 --> C1 A3 --> C2 A4 --> C2 C1 --> C3 C2 --> C3 C3 --> C4

8.2 PMO Permissions

Permission LevelScopeDescription
PMO DirectorAll projectsCan view all project data and adjust project priorities
PMO SpecialistDesignated project portfolioCan view designated portfolio data
Resource ManagerResource poolCan manage resource allocation but cannot view project business data

9. Technical Architecture

graph TB subgraph "yudao-module-pm-plus" subgraph "pm-biz" A1[project - Project Management] A2[wbs - WBS Decomposition] A3[task - Task Management] A4[schedule - Schedule Management] A5[milestone - Milestone Management] A6[resource - Resource Management] A7[timesheet - Timesheet Management] A8[risk - Risk Management] A9[document - Document Management] A10[analytics - Data Analysis] end subgraph "Permissions and Audit" B1[permission - Permission Control] B2[audit - Audit Logs] B3[compliance - Compliance Reports] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> B2 A5 --> B2 A6 --> B1 A7 --> B2 A8 --> B3

10. Business Value

Value PointDescription
Progress ControlGantt chart, milestones, critical path analysis
Resource OptimizationIntelligent scheduling, load balancing, timesheet management
Risk Pre-ControlRisk identification, alert mechanism, emergency response
Efficient CollaborationTask collaboration, document sharing, communication collaboration
Data-DrivenProject health score, efficiency analysis, decision support
Compliance and TraceabilityProject-level permissions, full-chain audit, change traceability
docs