Feature introduction

Project reports (including weekly reports and milestone reports) automatically generate multi-dimensional analyses of progress, cost, and quality. This helps teams grasp project health in real time, predict risks, and optimize decision-making efficiency.

These reports introduce Earned Value Management (EVM), a standard project management methodology used primarily for monitoring project costs and schedules. EVM is a management technique that integrates resource planning with scheduling, technical costs, and schedule requirements. Within this framework, all work is planned, budgeted, and scheduled according to the earned value over specific time periods, thereby forming a baseline for measuring cost and schedule performance.

Usage scenarios

• Project schedule retrospectives: Generate weekly reports to display task completion status and blocked task lists. Quickly identify iteration bottlenecks (such as insufficient testing environments) and drive the team to optimize collaboration workflows.
• Project health assessments: Evaluate team efficiency by analyzing multi-period SPI and SV trends (for example, an average SPI > 1.1 indicates progress is ahead of schedule). Identify long-term inefficiencies (such as excessively long story review times) and formulate improvement plans.
• Automated alerts: Configure alerts triggered when the SV exceeds 5% to remind Project Managers to intervene and adjust schedules. This shortens issue response times and prevents deviation accumulation.
• Cost control reporting: Export CPI data (for example, CPI = 0.95) to explain the current budget consumption efficiency and overspending risks to stakeholders. This facilitates resource reallocation (such as pausing the development of non-critical stories) to ensure the achievement of core goals.

I. Project reports and milestone reports

You can view the project's weekly progress report under Project > Dashboard.

图1

You can also view project progress on a weekly basis under Project > Report.

图2

If you set a specific phase as a milestone under Project > Plan > Set Phase, you can view its corresponding milestone report.

图3

图4

II. EVM in Waterfall projects

In Sanplex Premium's Waterfall projects, the Project > Report > Milestone Report section utilizes EVM concepts and data.

图5

1. EVM concepts

• PV (Planned Value): The authorized budget assigned to scheduled work up to a given point in time. It represents how much work is planned to be completed.
• EV (Earned Value): The measure of work performed expressed in terms of the budget authorized for that work up to a given point in time. It represents how much work has actually been completed.
• AC (Actual Cost): The realized cost incurred for the work performed on an activity during a specific time period. It represents how much money has actually been spent.
• SPI (Schedule Performance Index): The ratio of actual work completed to the planned work. Formula: SPI = EV / PV.
• CPI (Cost Performance Index): The efficiency of the spent budget, indicating how much value is earned for every unit of currency spent. Formula: CPI = EV / AC.
• SV (Schedule Variance): The difference between the actual progress and the planned progress at a specific point in time. Formula: SV = EV - PV.
• CV (Cost Variance): The difference between the actual cost incurred and the planned cost at a specific point in time. Formula: CV = EV - AC.

2. Calculation formulas

You can hover your mouse over the right side of the corresponding EVM information on the page to display tooltips explaining the EVM rules.

图6

Taking the project weekly progress report as an example:

2.1 PV (Planned Value)

Calculation method:

• If the task's estimated start and end dates fall entirely within the current week, the system accumulates the total estimated hours.
• If the task's estimated start and end dates are both before the current week, it accumulates the total estimated hours.
• If the estimated start date is before the current week, and the end date is within the current week, it accumulates the total estimated hours.
• If the estimated start date is within the current week, and the end date is after the current week, it accumulates: (Estimated Hours / Task Duration in Days) * Number of overlapping days within the week.
• If the estimated start date equals the start of the current week, and the end date is after the current week, it accumulates: (Estimated Hours / Task Duration in Days) * Number of overlapping days within the week.
• If the estimated start date is before the current week, and the end date equals the end of the current week, it accumulates the total estimated hours.
• If the estimated start date is before the current week, and the end date is after the current week, it accumulates: (Estimated Hours / Task Duration in Days) * Number of overlapping days within the week.

Statistical scope:

• The week starts on Monday at 00:00:00. The end date is determined based on working days and holidays.
• To avoid duplicate counting, the system only includes sub-tasks and excludes parent tasks.
• Excludes deleted tasks.
• Excludes canceled tasks.
• Excludes deleted tasks within an execution.
• If a task lacks an estimated start date, it defaults to the planned start date of its parent phase.
• If a task lacks an estimated end date, it defaults to the planned end date of its parent phase.
• The calculation formulas strictly operate based on working days.

2.2 EV (Earned Value)

Calculation method:

• For tasks with a "Finished" status, it accumulates the total estimated hours.
• For tasks closed with a "Finished" reason, it accumulates the total estimated hours.
• For tasks in progress or suspended, it accumulates: Estimated Hours * Completion Percentage.

Statistical scope:

• Includes tasks with non-zero consumed hours before the end date of the current week.
• To avoid duplicate counting, the system only includes sub-tasks and excludes parent tasks.
• Excludes deleted tasks.
• Excludes canceled tasks.
• Excludes deleted tasks within an execution.
• Completion Percentage = Consumed Hours / (Consumed Hours + Left Hours).

2.3 AC (Actual Cost)

Calculation method:

• Accumulates all consumed hours before the end date of the current week.

Statistical scope:

• Includes consumed hours from tasks, stories, bugs, test cases, builds, test requests, issues, risks, documents, and reviews.
• To avoid duplicate counting, the system only includes sub-tasks and excludes parent tasks.
• Includes consumed hours from deleted tasks, stories, bugs, test cases, builds, test requests, issues, risks, documents, and reviews.
• Includes consumed hours from deleted executions' tasks, stories, bugs, test cases, builds, test requests, and documents.
• Includes consumed hours from canceled tasks, issues, and risks.

2.4 SV(%) (Schedule Variance)

Calculation formula: SV(%) = -1 * (1 - (EV / PV))%

2.5 CV(%) (Cost Variance)

Calculation formula: CV(%) = -1 * (1 - (EV / AC))%

III. Related settings

You can configure the estimation unit, unit labor cost, daily working hours, and working days per week by navigating to Admin > Model Configuration > General > Estimation.

图7

You can configure detailed expense subjects by navigating to Admin > Model Configuration > General > Expense Subjects.

图8

After setting budgets for programs and projects, you can define the exact budget amount during project creation and editing.

图9

You can perform workload estimations, duration estimations, and cost estimations by navigating to Project > Estimation.

图10

图11

图12

You can set metric ranges, target control limits, and prompt messages for project schedule performance, schedule variance, cost performance, and cost variance by navigating to Admin > Feature Configuration > Metrics > Range Prompts.

图13