LeadingAgile is Now LiminalArc. Read the Full Announcement

Move beyond isolated AI experiments to build scalable, domain-driven systems with AI-ready architectures.

Enhance valuation and accelerate ROI through due diligence, tech migrations, and strategic restructuring.

Control cloud costs, streamline data, and focus investments on high-value, scalable solutions.

Streamline operations and improve decision-making by aligning your ERP systems with how your business actually works.

Reduce risk and increase resilience by closing the security gaps hiding in your architecture and workflows.

Optimize operations, restructure teams, and modernize technology to maximize the value of digital investments.

Deliver mission-critical software in production-ready increments that create measurable value early.

Reduce risk and complexity with every cycle, turning legacy systems into platforms that can evolve.

The belief that shaped us — and how it evolved into LiminalArc, the natural next step in our journey.

Our team of over 100 experts spans the nation, from consultants and technical architects to product specialists.

We are looking to hire mature, pragmatic consultants who are deeply passionate about meaningful change.

The Role of High-Level Estimates

Mike Cottmeyer Chief Executive Officer
Reading: The Role of High-Level Estimates

high level estimateOne of the first things I like to do with my clients, is help them identify their major investment themes, and how those investment themes support their vision for the product. Said another way, we work together to identify the major epics they want to build, and then we talk about how those epics are going to add value for their customers, when making a high level estimate.

After we identify the epics, we’ll have a conversation about each one… we’ll talk about the architecture and other technical implications. We’ll talk about the acceptance criteria and how that maps to what they want to accomplish. We’ll dive a little deeper and talk about the major features and stories that might comprise that epic.

Next I’ll ask them for a high level estimate for the epic… just back of the envelope stuff… how big do they think it is? If the team had nothing else to do, how many sprints might the epic take to complete? What I want is a non-binding, rough idea of how much effort the team thinks it will take to complete the work.

This is an interesting exercise for a couple of reasons. First… you can very quickly see that the team has an overwhelming amount of work they are being asked to consider. The sum total almost always doubles, triples, or even quadruples the team’s actual capacity. Second… if you prioritize the epics, you can pretty easily get a rough idea of what is going to make the cut and what isn’t.

The value in the high level estimate has nothing to do with the actual size of the epic… it should be a focusing tool to help us quickly zoom in on our most pressing priorities.  I don’t know about you, but I have yet to meet a customer that can’t figure out what they’d like to build… most struggle to figure out what they are going to have to leave out.

High-level estimates are not about making a commitment, they are really about setting and managing expectations around what is realistically possible.  Once we’ve dealt with our highest priorities first… if there is extra capacity, we can deal with the other stuff we couldn’t get to the first time around.

Next Lean Software & Systems Conference... Call for Papers & Registration Open

Comment (1)

  1. http://tinyurl.com/primread24502
    Reply

    Your own post, “The Role of High-Level Estimates | LeadingAgile” was indeed worthy of commenting
    here! Simply just wanted to state you did a fantastic work.
    Thanks a lot ,Dorothy

    Reply

Leave a comment

Your email address will not be published. Required fields are marked *

×