Estimations & Cost Roll‑Ups in Requirements Management: A Complete Guide Using OpenRose

 

Estimations are the backbone of effective requirements management and project planning. Without them, teams struggle to understand scope, sponsors cannot make informed funding decisions, and delivery teams cannot plan realistically. OpenRose introduces a modern, integrated approach to estimation that eliminates spreadsheets, manual calculations, and fragmented data sources. This blog post walks through the full set of capabilities demonstrated in the video, showing how OpenRose transforms estimation into a transparent, scalable, and decision‑ready process.

Why Estimation Matters in Requirements Management

Estimation is not just a number — it is a decision‑making instrument. In requirements engineering, estimation helps teams understand the size, complexity, and feasibility of what they are trying to deliver. When captured early and refined continuously, estimations allow organisations to evaluate whether a project is viable, whether scope needs to be adjusted, and whether the required resources exist.

“Estimation is very important within requirements management… It helps teams plan realistically and avoid surprises at the later part of the project.”

From a project management perspective, estimation is the foundation for budgeting, resource allocation, risk assessment, and timeline forecasting. Without accurate estimations, even the most well‑defined requirements can lead to unrealistic expectations and eventual project failure. Estimation also plays a crucial role in stakeholder communication, giving sponsors and business owners a clear understanding of what they are approving — and what trade‑offs may be required.

OpenRose brings estimation directly into the requirements hierarchy, ensuring that every requirement — from the smallest task to the largest programme objective — contributes to a single source of truth. This eliminates the need for spreadsheets and manual roll‑ups, reducing errors and improving estimation efficiency.

HS2 UK Demo Project: A Real‑World Example

To demonstrate estimation roll‑ups, the above referenced video uses the UK’s HS2 high‑speed rail programme as a sample dataset. This is a perfect example because HS2 is a large, complex, multi‑year programme involving thousands of requirements, dozens of contractors, and billions in public funding. Requirements were generated across categories such as:

• Business proposal & objectives
• Regulatory & compliance
• Construction & engineering
• Digital & system integration
• Operational readiness

Each category contains deeper layers, demonstrating how requirements engineering structures information into a hierarchical model. For example:

“Within the scope and success criteria we also have KPIs and performance metrics… and within that we have readiness reporting and governance.”

This hierarchical structure is essential for traceability, impact analysis, and cost aggregation. It allows project sponsors to understand not only what is being delivered, but how each requirement contributes to the overall programme.

The HS2 example is especially relevant given recent news about cost overruns and scope reductions.
This highlights the importance of transparent estimation, baseline tracking, and continuous cost monitoring — all of which OpenRose supports natively.

How Roll‑Up Estimation Works

Roll‑up estimation is one of the most impactful features in OpenRose. It ensures that estimation values captured at the lowest level automatically aggregate upward through the hierarchy. This mirrors real‑world project structure:

• Small tasks → contribute to
• Larger tasks → contribute to
• Features → contribute to
• Entire project

“OpenRose automatically adds up the estimation values of child requirements and displays the total at every parent level.”

This automation is essential for estimation efficiency. In traditional tools, teams often rely on spreadsheets or manual calculations, which are error‑prone and difficult to maintain. With OpenRose, roll‑ups are real‑time, accurate, and fully traceable.

From a project management perspective, roll‑ups provide immediate visibility into how changes at the requirement level affect the overall project. If a requirement is added, removed, or updated, the impact is instantly reflected at every parent level. This is invaluable for scope management, cost control, and sponsor communication.

In the referenced video, it shows us a concrete example and this demonstrates how OpenRose keeps the hierarchy consistent and trustworthy.

Requirement Create, Update, and Delete Events

Requirements evolve constantly — they are created, refined, updated and sometimes removed. Each of these events affects the project’s estimation profile. OpenRose ensures that roll‑ups remain accurate even as requirements change.

When a requirement is:

• Created → its estimation is added to its parent
• Updated → roll‑ups adjust instantly
• Deleted → parent totals decrease accordingly

This is essential for change management. In many organisations, estimation drift occurs because teams forget to update spreadsheets or because changes are made in one system but not another. OpenRose eliminates this risk by ensuring that estimation values are always synchronised with the requirements themselves.

For stakeholders and sponsors, this means they always see the current, accurate cost picture, not outdated or partial information.

Moving and Copying Requirements

Large projects often involve reorganising requirements — moving them between categories, restructuring hierarchies, or copying them for reuse. In traditional tools, this can break estimation logic or require manual recalculation.

OpenRose handles this seamlessly:

• When a requirement is moved, its estimation moves with it
• Parent totals update instantly
• No manual intervention is required

This is particularly useful in agile environments, where requirements may shift between epics, features, or releases. It also supports reuse strategies, allowing teams to copy requirement sets without losing estimation integrity.

Manually Triggering Entire Project Roll‑Ups

Although roll‑ups are automatic, OpenRose also provides a manual trigger for full recalculation. This is useful when:

• Large imports occur
• Bulk edits are made
• You want to validate the entire hierarchy

Manual roll‑ups give project managers confidence that the entire estimation structure is consistent. This is especially important before major governance events such as:

• Steering committee reviews
• Funding approvals
• Release planning sessions
• Baseline creation

Estimation and Baselining

Baselines capture a snapshot of your project at a point in time — including estimation values. This is essential for:

• Tracking cost drift
• Comparing planned vs. actual
• Supporting audits and governance
• Communicating with sponsors

OpenRose supports:

• Viewing estimation values inside baselines
• Comparing baseline estimations with current values
• Tracking changes over time

For project sponsors and business owners, baselines provide a frozen reference point that helps them understand how scope and cost have evolved. This is critical for maintaining trust and transparency.

Importing and Exporting Estimation Data

OpenRose ensures that estimation values are preserved during:

• JSON exports
• JSON imports
• Excel/CSV‑based workflows

This is essential for organisations that integrate OpenRose with:

• Financial systems
• PMO dashboards
• BI tools
• External reporting systems

This makes OpenRose interoperable with enterprise‑scale workflows and ensures that estimation data remains consistent across systems.

Mermaid Diagrams with Estimations

One of the most visually powerful features is the ability to generate Mermaid flowcharts that include estimation values. These diagrams can show:

• Requirement titles
• Estimation values
• Roll‑up totals
• Baseline values

This is perfect for stakeholder communication, especially when using the “tip of the iceberg” approach — showing high‑level items to management while keeping detailed requirements accessible in OpenRose.

These diagrams help sponsors quickly understand:

• What the major cost drivers are
• How requirements relate to each other
• Where the largest investments are concentrated

Mermaid Diagrams from Baselines

You can also generate Mermaid diagrams from baseline data, allowing you to visualise:

• Original estimates
• Approved scope
• Historical snapshots

This is ideal for comparing planned vs. actual cost evolution and for presenting historical context during governance reviews.

Estimations in JSON Data Views

OpenRose exposes estimation values in JSON views, enabling:

• API integrations
• Automation
• Custom dashboards
• External analytics

This makes OpenRose suitable for enterprise‑scale workflows where estimation data needs to flow into:

• Portfolio management systems
• Cost modelling tools
• Reporting pipelines

Orphan Items (No Estimation Support)

Orphan items — requirements with no parent — do not participate in roll‑ups. This ensures that the estimation hierarchy remains clean and meaningful.

This prevents accidental inflation of project totals and ensures that only properly structured requirements contribute to cost calculations.

Conclusions

Having integrated estimation management within OpenRose Requirements Management has lots of advantages.

• No spreadsheets
• No manual calculations
• Real‑time roll‑ups
• Baseline support
• Visual diagrams
• JSON integration

OpenRose provides a complete, modern approach to estimation within requirements management — suitable for everything from small personal projects to national‑scale programmes like HS2. It strengthens stakeholder communication, improves estimation accuracy, and gives sponsors the clarity they need to make informed funding decisions.

OpenRose, a free and open-source requirements management application / tool. For more information, visit 

https://github.com/openrose