Risk Mitigation

Managing Expectations in Large-Scale Enterprise Projects — Part 5

By Thomas J. Smart

With a clear Definition of Done in place, teams are better equipped to align on what success looks like. The next challenge is determining how long it will take to get there.

In this article, we explore how to approach estimates and timelines in large-scale enterprise projects. It demands rigorous risk mitigation and an agile approach to align with ever-changing organisational priorities.

Clear communication about why an estimate may be higher, coupled with a well-articulated value proposition, can position a given proposal as meticulous and thorough rather than expensive.

Fixed price vs Time & Materials

Fixed price contracts offer a set cost for specified work, providing budget certainty but less flexibility. Time and Materials (T&M) contracts, conversely, bill for actual work done, offering flexibility but less predictable costs. Here’s an in-depth comparison of the two:

Fixed price

The financial risk predominantly lies with the vendor. They agree to deliver a specified scope of work for a predetermined price.

This model offers clients cost certainty and places the responsibility for cost overruns with the vendor. However, this certainty comes with its own set of risks as it only fixes the price, not the quality or other aspects of the deliverables.

Under pressure to meet fixed deadlines and budgets, vendors or individual team members may resort to cutting corners, potentially compromising the quality of the final product. This risk is further exacerbated when unexpected challenges arise or scope changes are required as new information comes to light.

Additionally, the fixed price model can lead to burnout among vendor staff, who may be required to work extensive hours to meet stringent deadlines.

Time & Materials

In contrast, the T&M model shares the financial and timeline risk evenly between the client and the vendor while placing expectations on the quality of the deliverables. In this model, clients pay for the time spent and materials used on the project.

This approach offers greater flexibility to adapt to changing requirements. However, it also requires a higher degree of collaboration and trust between the client and the vendor.

Both parties work together to agree on priorities for each sprint, with a clear understanding of how changes can impact the timeline or the amount of work that can be completed by a given deadline. The organisation can continue to engage the vendor until the project is completed or until the internal team can take over and continue delivery entirely in-house.

Other Billing Models

Alternatives to fixed-price and T&M include:

• Fixed-price-fixed-deadline approach, where the deadline is set, but the scope is flexible. This means the vendor will work on the project, including any new change requests, until the deadline.
• Retainer agreements, where clients pay a regular fee for ongoing services.
• Milestone-based pricing, where payments are made upon reaching specific project milestones.
• Fixed price coupled with very high margins and low-cost staff, which allows organisations to simply throw increasing numbers of staff at any problem until it is resolved.

How To Enhance T&M Adoption in Your Organisation?

Departments such as procurement, finance, and legal in large enterprises often struggle with the T&M model. Their discomfort stems from a perception of increased financial risk, as costs are not fixed upfront.

However, the fixed-price model only enforces cost, not the quality and other aspects, which these departments typically attempt to enforce through stringent contractual clauses and terms.

A strategic and informed approach is crucial when an internal project team considers advocating for the T&M model to their procurement and legal departments. The conversation should begin by addressing these departments’ concerns regarding T&M, primarily the perceived financial risk and lack of fixed costs.

The team should explain how the proposal mitigates these risks through shared accountability and regular checkpoints. It’s essential to present a balanced view, acknowledging the concerns while highlighting the benefits of flexibility, adaptability, and the potential for higher-quality outcomes that T&M offers.

Another key point is to discuss how T&M can mitigate risks by allowing for continuous reassessment and realignment of project goals, which is often not feasible in a fixed-price model.

It may also be helpful to describe the tiger team approach and how that will ensure accountability and quality deliverables, reducing the need for handovers and their associated risks.

For vendors, the best approach is often to have this discussion with the project team and provide them with the necessary information and support to advocate for the T&M model internally. Vendors can assist by providing case studies, risk analysis, and examples of successful T&M projects.

Using tiger teams for shared accountability

Tiger teams, a concept originating in the aerospace industry, are specialised, cross-functional teams formed to solve specific problems or address critical issues in projects. These teams are characterised by their agility, expertise, and focus on rapid problem-solving.

There are three key ways to implement tiger teams, depending on your project scenario:

Scenario: Organisation lacks available resources

The initial approach may involve the vendor starting the project independently. However, it is crucial for the organisation to at least assign a product-owner-type role from the outset. This individual will be responsible for setting priorities for each sprint, ensuring that the project remains aligned with the organisation’s objectives. Over time, the organisation should strive to find or hire suitable team members who can gradually integrate into the tiger team, thereby increasing the level of shared project accountability.

Scenario: Organisation has inexperienced resources

Again, the vendor independently starts the project. Concurrently, the organisation’s staff undergo a fast-tracked educational program, typically spanning about two weeks, to bring them up to speed on the project’s technical aspects and methodologies. Following this training period, the team members start participating in the tiger team with limited responsibilities. They can then take on additional responsibilities and tasks as their experience grows.

Scenario: Organisation has experienced resources

In this case, the focus shifts to understanding and leveraging the strengths and expertise of each team member. Responsibilities and tasks are assigned based on an assessment of the vendor and the organisation’s members. This strategic allocation of roles maximises the efficiency and effectiveness of the team. Regular communication and collaboration ensure members stay aligned and work cohesively towards their objectives.

Calculating Risk Margins in Estimates

It’s a common practice in project management to add a fixed percentage to project timelines as a risk buffer. However, this approach is fundamentally flawed and often fails to manage expectations. Applying a blanket percentage, such as the common 10% or 20%, across all projects fails to account for each project’s unique risks and challenges.

The key issue with this method is its lack of responsiveness to the specific risk profile of each project and the involved team, leading to either underestimation or overestimation of risks.

A calculated approach to risk margins involves assessing a project’s specific risk factors to generate a tailored buffer. This method improves accuracy, justifies the estimate, and boosts stakeholder confidence by aligning the risk margin with the project’s actual complexity.

For example, consider a hypothetical project to develop a new cloud-based application. After accounting for the use of untested technologies, the team’s limited experience, vague requirements, and potential regulatory changes, a risk margin of 55% is calculated.

As the fictional project progresses, various factors impact the timeline. The emerging technologies prove more challenging than anticipated, consuming additional time. However, the team adapts quickly, mitigating some of the delays. Regulatory changes do occur, but their impact is less significant than expected.

Overall, the project experiences a 50% increase in the timeline, closely aligning with the calculated risk margin of 55%. Had a fixed percentage been used, say 20%, the project would have been significantly underestimated, leading to budget overruns and strained client relations.

As a result, the calculated approach provides a more realistic buffer, allowing for better management of expectations and project delivery.

Factors influencing the risk margin

Each of the following factors should be carefully evaluated in the context of a specific project to determine their impact on the risk margin percentage. A suggested range (how much it influences the margin) has been provided next to each factor:

• Project complexity (+5% to +20%): Complex projects with critical workloads, custom development, and interdependencies increase risk. Simpler deployments of off-the-shelf products carry lower risk.
• Team experience (−5% to +15%): Skilled and experienced teams reduce risk. Meanwhile, less experienced teams increase it, especially if the client-side team lacks familiarity and requires more education and support.
• Technological novelty (0% to +25%): New or untested technologies increase unpredictability and thus risk. Familiar, proven technologies result in lower risk.
• Clarity of requirements (−5% to +25%): Clear and detailed requirements reduce uncertainty. Vague, shifting, or undefined requirements significantly raise the risk.
• Regulatory factors (0% to +15%): Regulatory compliance adds risk, especially if legal requirements are unclear or pending. Prior due diligence helps mitigate this.
• Offshore factor (0% to +10%): Cross-border projects involving different cultures and time zones carry higher risk due to communication and expectation mismatches.
• Resource reliability (−5% to +15%): Readily available and dependable resources reduce risk. Projects with constrained or unreliable resources face elevated risk.
• Technology reliability (−5% to +10%): Tools designed for the intended environment lower risk. Using unsuitable or legacy tech, like on-prem tools in cloud projects, can increase it.
• Change management (−5% to +20%): Effective change management processes and accountable owners help mitigate risk. Poorly defined or ad hoc processes amplify it.

Final Thoughts

Effective estimation and timeline management are foundational to managing expectations in large-scale projects. Choosing the right commercial model, whether fixed price or time & materials, shapes how risk is shared and how flexible the engagement can be. A calculated approach to risk margins adds transparency and credibility, helping align expectations with the project’s true complexity.

Engaging procurement and legal teams early in these decisions, especially when considering T&M models and tiger teams, builds a shared understanding of risks and responsibilities. This creates the conditions for a more adaptive and collaborative partnership.

In the next article, we’ll explore how these early decisions translate into successful project delivery and how to maintain alignment through execution.

Who is Thomas?

Thomas is a highly accomplished digital transformation leader and Fractional CTO at MISSION+. With 21+ years of experience across FinTech, telco, logistics, and cloud transformation, he excels at bridging C-level strategy with actionable execution. As a prolific author, Thomas has written multiple blogs and whitepapers in which he shares his ideas around technology, project management, and problem-solving. Feel free to discuss your large-scale project delivery headaches with Thomas by reaching out at hello@mission.plus.