DURATION ESTIMATES
tasleemat asset PMO-04.03.06 template --lang en
Deliverable Summary & Governance Boundaries
Lifecycle Phase Alignment
Phase 04: Planning
Sizing Tier Requirements
Validation Contract
This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.
tasleemat validate PMO-04.03.06 ./completed_data.json
Template Markdown (Bilingual)
<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.
Section Instructions:
- Activity Duration Estimates Table: Provide comprehensive project data for all required fields in this section.
- Basis of Estimates and Assumptions: Provide comprehensive project data for all required fields in this section.
- Contingency and Reserve Analysis: Provide comprehensive project data for all required fields in this section.
-->
<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">DURATION ESTIMATES</h1>
| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |
---
## 1. Activity Duration Estimates Table
**Activity Identifier and Description:**
[ Add details... ]
**Estimation Method Applied:**
[ Add details... ]
**Estimated Effort Hours and Assigned Resources:**
[ Add details... ]
**Estimated Duration:**
[ Add details... ]
---
## 2. Basis of Estimates and Assumptions
**Historical Data and Productivity Rates:**
[ Add details... ]
**Key Estimating Assumptions:**
[ Add details... ]
---
## 3. Contingency and Reserve Analysis
**Schedule Contingency Reserve:**
[ Add details... ]
**Total Activity Duration with Contingency:**
[ Add details... ]
---
### Sign-off and Approvals
| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Lead Estimator / Technical Lead** | {{Estimator_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Planner / Scheduler** | {{Scheduler_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
---
<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
<span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
<strong>Template:</strong> DURATION ESTIMATES | <strong>Ref:</strong> PMO-04.03.06 <br>
<i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>
User Guide & Practitioner Instructions
Tasleemat Forms Guide
Project Artifact: Duration Estimates
Document Reference: PMO-04.03.06
This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Duration Estimates in alignment with the Tasleemat framework.
1. What?
A structured schedule table recording activity duration estimates, effort hours, estimation techniques, and contingency reserves.
2. Why?
Provides the mathematical time inputs required to build a realistic, achievable project schedule baseline.
3. When?
Calculated during schedule planning prior to network forward/backward pass schedule generation.
4. Who?
Created by Task Leads and Estimators, reviewed and consolidated by Project Scheduler.
Tailoring Tips
- Estimate in relative story points and velocity-based sprint horizons for agile initiatives.
- Apply three-point statistical distributions for high-uncertainty research and development tasks.
Alignment & Dependencies
1. Pre-requisites & Inputs (Upstream Dependencies)
- Mandatory:
- Work Breakdown Structure / WBS (PMO-04.02.06)
- Scope Statement (PMO-04.02.05)
- Optional / Contextual:
- Resource Requirements (PMO-04.06.02)
- Risk Register (PMO-04.08.02)
2. Downstream Dependents
- Mandatory:
- Project Schedule Baseline (PMO-04.03.08)
- Earned Value Analysis / EVA (PMO-06.05)
- Optional / Contextual:
- Release Plan (PMO-04.03.09)
- Lookahead Planning Log (PMO-04.03.10)
5. How?
To accurately and professionally complete the Duration Estimates, the responsible party
must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):
- Activity Identifier and Description: The activity code and concise work summary for each estimated activity.
- Estimation Method Applied: The specific technique used (analogous, parametric, three-point, or bottom-up).
- Estimated Effort Hours and Assigned Resources: Total calculated person-hours of effort and assigned resource quantities.
- Estimated Duration: Calculated working duration in work days or weeks required to complete the activity.
- Historical Data and Productivity Rates: Empirical reference data, productivity metrics, and historical benchmarks used.
- Key Estimating Assumptions: Foundational assumptions regarding resource availability, skill proficiencies, and work shifts.
- Schedule Contingency Reserve: Calculated contingency buffer allocated to accommodate identified activity risks.
- Total Activity Duration with Contingency: Final baseline duration inclusive of contingency buffer used in the schedule model.
6. Reference Example
A fully completed, gold-standard reference example illustrating this artifact in practice is available:
๐ Completed Example: 04_03_06_Duration_Estimates_Example.md
LLM Generation Prompt & Agent Instructions
Duration Estimates - Generation Prompt
System Instructions: This document contains instructions for generating the ยซDuration Estimatesยป. When asked to fill this template, follow the section-by-section instructions below. Refer to
parameters.mdfor project variables.Context and Definition: A quantitative schedule document detailing the quantitative assessments of the likely number of time periods required to complete each activity.
Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Work Breakdown Structure / WBS (PMO-04.02.06), Scope Statement (PMO-04.02.05) * Optional: Resource Requirements (PMO-04.06.02), Risk Register (PMO-04.08.02) * Downstream Dependents: * Mandatory: Project Schedule Baseline (PMO-04.03.08), Earned Value Analysis / EVA (PMO-06.05) * Optional: Release Plan (PMO-04.03.09), Lookahead Planning Log (PMO-04.03.10)
Activity Duration Estimates Table
Activity Identifier and Description
Instruction: The activity code and concise work summary for each estimated activity.
Generated Value: [ Add details... ]
Estimation Method Applied
Instruction: The specific technique used (analogous, parametric, three-point, or bottom-up).
Generated Value: [ Add details... ]
Estimated Effort Hours and Assigned Resources
Instruction: Total calculated person-hours of effort and assigned resource quantities.
Generated Value: [ Add details... ]
Estimated Duration
Instruction: Calculated working duration in work days or weeks required to complete the activity.
Generated Value: [ Add details... ]
Basis of Estimates and Assumptions
Historical Data and Productivity Rates
Instruction: Empirical reference data, productivity metrics, and historical benchmarks used.
Generated Value: [ Add details... ]
Key Estimating Assumptions
Instruction: Foundational assumptions regarding resource availability, skill proficiencies, and work shifts.
Generated Value: [ Add details... ]
Contingency and Reserve Analysis
Schedule Contingency Reserve
Instruction: Calculated contingency buffer allocated to accommodate identified activity risks.
Generated Value: [ Add details... ]
Total Activity Duration with Contingency
Instruction: Final baseline duration inclusive of contingency buffer used in the schedule model.
Generated Value: [ Add details... ]
Duration Estimates (Reference Example)
๐ Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (
PMO-04.03). All company names, project references, and figures are realistic fictional simulations.
Apex Global Solutions
Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01
DURATION ESTIMATES
1. Activity Duration Estimates Table
Activity Identifier and Description: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Estimation Method Applied: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Estimated Effort Hours and Assigned Resources: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Estimated Duration: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
2. Basis of Estimates and Assumptions
Historical Data and Productivity Rates: Assumptions and Constraints: * Assumptions: Subject matter experts (SMEs) are allocated at 25% dedicated capacity during Sprint cycles; external vendor API schemas remain stable. * Constraints: Hard completion deadline prior to Q4 fiscal year close; pre-approved budget limit of $3.5M USD; mandatory adherence to corporate data protection guidelines.
Key Estimating Assumptions: Assumptions and Constraints: * Assumptions: Subject matter experts (SMEs) are allocated at 25% dedicated capacity during Sprint cycles; external vendor API schemas remain stable. * Constraints: Hard completion deadline prior to Q4 fiscal year close; pre-approved budget limit of $3.5M USD; mandatory adherence to corporate data protection guidelines.
3. Contingency and Reserve Analysis
Schedule Contingency Reserve: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Total Activity Duration with Contingency: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.
Sign-off and Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Lead Estimator / Technical Lead | Approved - Estimator Name | [Electronically Signed] | 2026-03-18 |
| Project Planner / Scheduler | Ibrahim Al-Dosari, PMI-SP | [Electronically Signed] | 2026-03-18 |
| Project Manager | Faisal Al-Harbi, PMP | [Electronically Signed] | 2026-03-18 |
| --- |
Generated on: 2026-03-15 10:00 UTC, by Tasleemat
Draft 2020-12 JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://tasleemat.pmo/schemas/completed/PMO-04.03.06.schema.json",
"title": "Completed DURATION ESTIMATES Data Contract",
"description": "Additive structural schema validating completed DURATION ESTIMATES artifact data payloads (PMO-04.03.06).",
"type": "object",
"properties": {
"artifact_id": {
"type": "string",
"const": "PMO-04.03.06"
},
"metadata": {
"type": "object",
"properties": {
"project_name": {
"type": "string",
"minLength": 1
},
"project_code": {
"type": "string"
},
"date_prepared": {
"type": "string",
"format": "date"
},
"project_manager": {
"type": "string",
"minLength": 1
},
"prepared_by": {
"type": "string",
"minLength": 1
},
"version": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"draft",
"baselined",
"in_review",
"approved"
]
}
},
"required": [
"project_name",
"date_prepared",
"project_manager",
"prepared_by"
]
},
"activity_duration_estimates_table": {
"type": "object",
"properties": {
"activity_identifier_and_description": {
"type": "string",
"minLength": 1,
"description": "The activity code and concise work summary for each estimated activity."
},
"estimation_method_applied": {
"type": "string",
"minLength": 1,
"description": "The specific technique used (analogous, parametric, three-point, or bottom-up)."
},
"estimated_effort_hours_and_assigned_resources": {
"type": "string",
"minLength": 1,
"description": "Total calculated person-hours of effort and assigned resource quantities."
},
"estimated_duration": {
"type": "string",
"minLength": 1,
"description": "Calculated working duration in work days or weeks required to complete the activity."
}
},
"required": [
"activity_identifier_and_description",
"estimation_method_applied",
"estimated_effort_hours_and_assigned_resources",
"estimated_duration"
]
},
"basis_of_estimates_and_assumptions": {
"type": "object",
"properties": {
"historical_data_and_productivity_rates": {
"type": "string",
"minLength": 1,
"description": "Empirical reference data, productivity metrics, and historical benchmarks used."
},
"key_estimating_assumptions": {
"type": "string",
"minLength": 1,
"description": "Foundational assumptions regarding resource availability, skill proficiencies, and work shifts."
}
},
"required": [
"historical_data_and_productivity_rates",
"key_estimating_assumptions"
]
},
"contingency_and_reserve_analysis": {
"type": "object",
"properties": {
"schedule_contingency_reserve": {
"type": "string",
"minLength": 1,
"description": "Calculated contingency buffer allocated to accommodate identified activity risks."
},
"total_activity_duration_with_contingency": {
"type": "string",
"minLength": 1,
"description": "Final baseline duration inclusive of contingency buffer used in the schedule model."
}
},
"required": [
"schedule_contingency_reserve",
"total_activity_duration_with_contingency"
]
}
},
"required": [
"artifact_id",
"metadata",
"activity_duration_estimates_table",
"basis_of_estimates_and_assumptions",
"contingency_and_reserve_analysis"
]
}
๐ Form Field Definitions Dictionary (Legacy Specification)
{
"form_name": "DURATION ESTIMATES",
"document_reference": "PMO-04.03.06",
"_llm_instructions": "Populate the fields of 'DURATION ESTIMATES' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.03.06.",
"project_title": "",
"date_prepared": "",
"fields": {
"f01_Activity_Identifier_and_Description": {
"section": "Activity Duration Estimates Table",
"label": "Activity Identifier and Description",
"guidance": "The activity code and concise work summary for each estimated activity.",
"value": ""
},
"f02_Estimation_Method_Applied": {
"section": "Activity Duration Estimates Table",
"label": "Estimation Method Applied",
"guidance": "The specific technique used (analogous, parametric, three-point, or bottom-up).",
"value": ""
},
"f03_Estimated_Effort_Hours_and_Assigned_Resources": {
"section": "Activity Duration Estimates Table",
"label": "Estimated Effort Hours and Assigned Resources",
"guidance": "Total calculated person-hours of effort and assigned resource quantities.",
"value": ""
},
"f04_Estimated_Duration": {
"section": "Activity Duration Estimates Table",
"label": "Estimated Duration",
"guidance": "Calculated working duration in work days or weeks required to complete the activity.",
"value": ""
},
"f05_Historical_Data_and_Productivity_Rates": {
"section": "Basis of Estimates and Assumptions",
"label": "Historical Data and Productivity Rates",
"guidance": "Empirical reference data, productivity metrics, and historical benchmarks used.",
"value": ""
},
"f06_Key_Estimating_Assumptions": {
"section": "Basis of Estimates and Assumptions",
"label": "Key Estimating Assumptions",
"guidance": "Foundational assumptions regarding resource availability, skill proficiencies, and work shifts.",
"value": ""
},
"f07_Schedule_Contingency_Reserve": {
"section": "Contingency and Reserve Analysis",
"label": "Schedule Contingency Reserve",
"guidance": "Calculated contingency buffer allocated to accommodate identified activity risks.",
"value": ""
},
"f08_Total_Activity_Duration_with_Contingency": {
"section": "Contingency and Reserve Analysis",
"label": "Total Activity Duration with Contingency",
"guidance": "Final baseline duration inclusive of contingency buffer used in the schedule model.",
"value": ""
}
}
}