Transformidable Advisory · Project Governance

Independent verification and validation (IV&V) for ERP and major technology programs

On a large technology program, the people reporting on progress are usually the people responsible for it: the project team, the implementation partner, the software vendor. Boards, executives, and funders accountable for a multi-year program need a view that doesn't depend on them.

IV&V provides it: an independent assessment of whether the program is being built right, whether it's building the right thing, and whether what leadership is told matches what is actually happening.

When organizations bring in IV&V

  • Before major commitments: at funding decisions, vendor selection, or contract signature.
  • When a funder, legislature, or policy requires it, as is common for large public-sector and higher education systems.
  • Before go-live, to give leadership an independent read on readiness.
  • When status reports stay green but something feels wrong.
  • After a missed milestone, a key departure, or a change of implementation partner.

What IV&V looks at

  1. Governance and decision-making: whether decisions are made by the right people, on time, with the right information.
  2. Scope and requirements: whether what’s being built traces back to what the organization needs.
  3. Schedule and budget realism: whether the plan is achievable, or only reportable.
  4. Vendor and partner performance: delivery against contract and commitments.
  5. Data conversion, testing, and cutover: where most go-lives are actually won or lost.
  6. Organizational readiness: whether the people who will use the system are ready to.
  7. Risk and issue management: whether known risks are owned, tracked, and acted on.
  8. Reporting: whether what reaches executives and the board reflects reality.

Independence is the point

IV&V only works if it is independent of the people delivering the program. Transformidable does not sell or implement the systems we assess, and works alongside your existing vendors and partners rather than competing with them (independence policy). Our IV&V reports to the program’s sponsor, steering committee, or board, not to the project team being assessed.

Troubled project recovery

Sometimes the question isn’t whether a program might fail, but what to do now that it’s in trouble.

Signs a project is failing

  • Status was green for months, then suddenly red.
  • Go-live dates move, but scope and budget don’t.
  • Testing time is being cut to protect the date.
  • Change orders keep arriving, and no one can say what they add up to.
  • Decisions escalate, and nothing comes back.
  • Key people on your side, or the partner’s, are leaving.

How recovery works

  1. An independent assessment of the true state: schedule, budget, quality, readiness, and the relationship with the partner.
  2. A reset of governance: who decides what, and how fast.
  3. An honest re-baseline of scope, schedule, and cost.
  4. A clear decision for leadership: continue, pause, restructure, or stop, with the evidence for each.
  5. Reporting the board can rely on from that point forward.

For higher education ERP and student system implementations

Finance, HR, and student information system replacements are among the largest and riskiest programs a university undertakes. They touch every office, run for years, and are often watched closely by trustees and state oversight. IV&V gives presidents, CFOs, and governing boards an independent view throughout, not just at the end.

Experience behind the assessment

Our IV&V and recovery work is led by Dr. Jerri Bland, who has spent more than 25 years in enterprise technology leadership, including as Deputy CIO at Columbia University and as Associate Vice Chancellor for Enterprise Applications at UNC–Chapel Hill, where she led a $42M+ implementation portfolio. She also leads Transformidable’s research on why technology programs succeed or fail. See the Case Files.

Questions

What is IV&V?

Independent verification and validation (IV&V) is an independent assessment of a technology program. Verification asks whether the system is being built correctly; validation asks whether it's the right system for the organization's needs. "Independent" means the assessor is separate from the team, vendor, and partner delivering the work.

How is IV&V different from quality assurance or a PMO?

Quality assurance and a project management office are part of delivering the program, and they report within it. IV&V stands outside the program and reports to the people accountable for it: sponsors, steering committees, boards, and funders.

When should IV&V start?

As early as possible, ideally at planning or vendor selection. Problems found early are far cheaper to fix than problems found at go-live. IV&V can still start mid-program, and often does when concerns surface.

Who should IV&V report to?

To the executive sponsor, steering committee, or board, not to the project team or implementation partner being assessed.

Can IV&V help a project that's already in trouble?

Yes. An independent assessment is usually the first step in recovery: it establishes the true state of the program so leadership can decide whether to continue, restructure, or stop.

Concerned about a program, or about to start one?

Tell us where it stands. We'll tell you honestly whether independent oversight would help, and what it would look at first.