When a major U.S. city's Department of Finance engaged Lighthouse to conduct an independent verification and validation assessment, they expected us to confirm what their internal team already suspected: that the project was running a few weeks behind. What we found in 30 days changed the conversation entirely.

The Assessment Structure

Lighthouse was given access to project documentation, test environments, source code, and the vendor team. Over 30 days, we applied our assessment methodology — function point analysis across all five dimensions: Quality, Effort, Schedule, Cost, and Culture.

What emerged was not a picture of a struggling project. It was a picture of a project whose risks were invisible to everyone inside it.

What Was Actually Hidden

• Test script defect density measured at approximately 10x the accepted industry standard — meaning the automated testing suite itself was unreliable
• Schedule analysis showed the project was 7+ weeks behind pace against function point benchmarks, despite positive internal reporting
• A single subject-matter expert held critical undocumented knowledge with no succession plan in place
• Script execution times had ballooned from 3–4 hours to 12+ hours — a leading indicator of test suite fragility

What Leaders Did With the Data

The 91 findings — including 58 formal weaknesses — were delivered in a board-ready report with severity ratings and prioritized remediation paths. The department used the findings to restructure vendor accountability, address the knowledge risk, and reset the project timeline with a defensible basis.

That is what independent assessment produces: not more status reporting, but the data leaders need to make decisions with confidence.

The conversation about software delivery risk almost always ends up in the wrong room. It goes to the engineering lead, the QA director, the scrum master. Business leaders receive a summary — typically a color-coded status report that shows green until something turns catastrophically red.

The Accountability Gap

Today, even companies that do not consider themselves software companies rely on software to operate, compete, and grow. Products include embedded software, customer portals, and mobile applications. Operations depend on custom systems, ERP platforms, and outsourced development partners.

But many organizations were not built to manage software delivery at this level of complexity. As a result, business and technology leaders are often accountable for critical outcomes — product launches, revenue timelines, regulatory compliance — without a clear view of whether the work is truly on track.

What the Iceberg Conceals

The visible portion of a software project — the sprint velocity charts, the test pass rates, the milestone dashboards — tells an incomplete story. What is hidden below the waterline is where risk accumulates: requirement gaps, fragile test suites, knowledge dependencies, vendor accountability gaps, and schedule estimates disconnected from actual function point velocity.

Problems don't appear overnight. They build over months of optimistic reporting. By the time they surface, they affect revenue timing, budget allocation, customer commitments, and strategic planning.

What Independent Visibility Changes

• Leaders can move from reacting to missed deadlines to proactively managing delivery risk
• Vendor and contractor accountability becomes measurable, not just asserted
• Board-level decisions about technology investment are grounded in evidence, not projections
• The business planning cycle becomes more predictable because delivery becomes more predictable

Software delivery is not an IT concern. It is a business outcome — and business leaders deserve the objective data to manage it as one.