Release management
Fabric — OMS, Offers, Cart & Checkout release trains
The problem
Fabric’s commerce platform shipped as separate products — OMS, Offers, Cart and Checkout — each built by a distributed engineering team. Their monthly rollouts overlapped, and hotfix escalations landed in between. Without a single owner of the release calendar, a slip in one team could put another team’s rollout, and enterprise clients’ SLAs, at risk.
The approach
Owned the release roadmap across teams and synchronized their release schedules into one monthly plan, so simultaneous rollouts and hotfix escalations were sequenced rather than colliding. Gave final production sign-off on every release and hotfix, 100+ in all, running go/no-go reviews with engineering and client teams during and after QA. Kept milestones and risk visible to engineering, product, and client stakeholders through reviews and weekly business reviews.
The impact
Across 100+ production releases and hotfixes, 99% of scheduled releases shipped on time and 87%+ of committed features landed in their planned release, with rollbacks kept under 5%, protecting uptime for enterprise clients.