How a Delivery Plan Works
This section explains how the planned data from the Delivery Plans are consumed based on the worklogs and work rates and how the users can track the service progress/consumption from them.
Understanding the Data Hierarchy
Before going through the Delivery Plans functionality, it is important to know how the system handles the overall information. Although the Delivery Plan is the key entity, there are other entities that surround it and which are important to obtain meaningful information related to services consumption and comparison between planned and executed. The diagram below exemplifies this structure:
Processing the Delivery Plans
Please, refer to the Create a Delivery Plan section for detailed information.
When a delivery plan is created for a customer, the system will use the issues or worklogs added against its accounts to track progress/consumption, depending on the billing model defined (hours or fixed-price).
Billing Model | Behavior |
---|---|
Hours |
|
Fixed-Price |
|
The system only starts counting issues, rates or worklogs when the respective delivery plan status is changed from DRAFT to ACTIVE.