InfoBeans Logo

What are you curious about?

How a consumer goods manufacturer took a three pillar Fusion rollout from 8 months to 5

  • Consumer Goods
  • Oracle Fusion
  • QAVA
  • Oracle Fusion Cloud
  • Financials, Procurement and Supply Chain
  • North America

Starting all three workstreams from the same requirements and the same Oracle process list took three months out of the rollout and four months out of testing.

5
4
3
120

Challenge

The go live date was fixed. Functional leads spent about three weeks on each first FDD draft, and nobody could start writing tests until those were done. Configuration gaps for new business units and legal entities surfaced after SIT had already begun, so the same people were fixing setup and testing it at the same time. Testing alone was budgeted at seven months.

Why it mattered

The steering committee had already said out loud that the plan looked tight. With three pillars, 120 integrations and roughly 90 reports and 40 extensions in scope, any slip in FDDs or configuration pushed straight into a date that was not going to move.

Outcome

InfoBeans started all three workstreams from the same requirements and the same Oracle process list, so no workstream waited on another team's spreadsheet. First FDD drafts reached the functional leads in four days, and their job became reviewing and correcting rather than writing. Business unit and legal entity setup was checked before SIT rather than during it, and test coverage for all three phases came from that same baseline.

Impact

Requirements to go live took five months instead of eight, and combined testing finished in under three months against the seven budgeted. The go live date held, and the program went into cutover with time in hand rather than borrowed. Optional callout, What it caught: Reviewing a new legal entity's setup turned up a tax registration setting that did not match its country, caught before SIT rather than days in, as a transaction that would not post. The reference site runs this as a dark card between Snapshot and Result. Worth keeping if the five-fold format can take it.

A fixed go live date is a design constraint, not a risk to manage.

A fixed go live date is a design constraint, not a risk to manage.

Most programs protect the date by cutting scope late. We take the time out of the front half instead, starting FDDs, configuration checks and test design from one baseline, so the back half is not where the surprises land.

Let's Talk
Shobhit Sethi
Director, Delivery
LinkedIn
Shobhit Sethi, Director, Delivery
Shobhit Sethi
Director, Delivery
LinkedIn
Let's Talk