Getting Started: Estimations Overview

Here’s an overview of using estimations within the Proceve software. This article provides a comprehensive overview of how our software handles estimation in project management, focusing on improving project success through accurate and consistent resource and time management.

Importance of Estimation

Estimation is a crucial element in project management, directly impacting a project’s success. Inadequate estimation and resource management are the second biggest cause of project failure.

At Proceve, we have developed a robust estimation framework designed to manage resources effectively and improve accuracy across all project stages.

Common Estimation Approaches

Story Points, T-shirt Sizes, and Complexity Measures

In project management, common estimation methods include:

  • Story Points: Used primarily in Agile frameworks to estimate the effort or time required.
  • T-shirt Sizes: A simple method for categorizing tasks by size (e.g., Small, Medium, Large).
  • Complexity Measures: Assessing the complexity of tasks, which often correlates with time and effort.

These methods aim to translate into person-hours, forming the basis for project estimation.

Mapping Person-Hours to Estimates

Translating Person-Hours into Story Points

In practice, when estimating using methods like story points or T-shirt sizes, team members often subconsciously map these estimates to person-hours. For example:

  • 1 Story Point: Could represent a task requiring less than a day.
  • 2 Story Points: Task with a duration of 1, 2, or 3 days.
  • 5 Story Points: Might equate to a week’s worth of work.

Understanding this mapping is key to creating consistent and reliable estimates across projects.

Estimation Mappings in Proceve

Customizing Mappings for Different Projects

Proceve allows users to define custom estimation mappings for each project, creating consistency in how estimates are translated across teams.

The estimation mapping provides users with a low, expected, and high range set of hours. This allows users to review past performance to determine if they consistently exceed or fall short of their estimated hours, allowing them to make necessary adjustments for future estimates.

Example of an Estimation Mapping Set:
  • One Story Point = XXXSmall T-Shirt = Extremely Simply Complexity = Activity(1,2…6) Person Hours

These mappings are adjustable by each team, allowing for flexibility while maintaining project-wide consistency.

Aggregating and Calibrating Estimates

Building Estimates Hierarchically

Estimates in Proceve can be built up hierarchically, with sub-estimates contributing to the overall project estimate. This approach enables:

  • Detailed Breakdown: Identifying subtasks and applying estimates to each.
  • Aggregation: Our software combines sub-estimates to form a comprehensive project estimate.

Breakdown of Estimate Components

Structuring Estimates

In Proceve, each estimate is composed of several key components. These components ensure that your estimates are comprehensive and aligned with your project’s needs.

  • Value Sets: Includes story points, T-shirt sizes, complexity, and person-hours (person hours offer a range of Low, Expected, High)
  • Costs: Estimates include cost structures, reflecting the financial impact of the resources needed. Costs are calculated based on the time estimates, offering a range from low to high.
  • Resources: Estimates are linked to specific resource types (e.g., BA, Intern, Chief Architect), The experience level and associated costs of these resources are factored into the estimate, allowing for consistent resource allocation.

Aggregating Estimates

Combining Sub-Estimates

Proceve allows estimates to be aggregated from subtasks, providing a total estimate that includes:

  • Aggregation of tasks: Combines estimates from all subtasks and creates a sub-estimate within the top level.
  • Local Estimate: Additional estimate for unspecified or uncertain tasks.
  • Total Estimate: The sum of both aggregated and local estimates, ensuring all aspects of the task are covered.

This comprehensive approach ensures that both detailed subtasks and broader project elements are fully accounted for in the overall project estimate.

Applying Estimates Across Artifacts

Estimating Requirements, Tests, Issues, and More

Estimation in Proceve is not limited to just tasks; it extends to all project artifacts, including requirements, tests, issues and more.

This approach ensures that all aspects of a project are accounted for, leading to more accurate project planning and resource allocation.