01
Made technical risk visible early
Reviewed migration, compatibility, dependencies, and post-migration structure with Technical Leads. Issues were treated as decisions with owners—not as late surprises during UAT.
All projects
Hugo / Case studyVN
Enterprise modernization · Delivery governance
Turning a compressed modernization into a governable delivery.
Toshiba Australia needed to modernize an integration-heavy customer portal from Sitecore 8 through 9 to 10 while releasing B2B/B2C capabilities. I combined project-management ownership with senior engineering judgement to keep a fixed-price, high-risk delivery moving.
Role
Technical Project Manager · Senior Developer
Team
10–15 person cross-functional delivery team
Industry
Enterprise commerce & customer portal
Scope
Migration, delivery governance, UAT, release risk
The challenge
A fixed-price commitment left little room for hidden complexity.
The delivery window was compressed to roughly half of the original technical estimate. At the same time, the platform was not a conventional CMS: it carried B2B/B2C behavior, deep integrations, migration dependencies, uneven local environments, and an expanding team with varied experience.
How I led the work
Turning complexity into work the team could own.
02
Turned reporting into an early-warning system
Created JQL monitoring views in Confluence for completion, remaining work, defects, blockers, and individual progress; then investigated the root cause and dependency behind every concerning signal.
03
Protected quality while the team scaled
Decomposed committed scope into smaller owned workstreams, strengthened QC planning and deployment monitoring, and escalated technical blockers quickly enough to preserve fixed-price milestones.
Operating model
A shared delivery rhythm for a complex release
Clear communication channels, two-week planning, twice-weekly customer stand-ups, and visible risk ownership gave the distributed team one operating model from scope to release.
- 1Clarify requirements
- 2Plan & assign work
- 3Build & quality control
- 4UAT & release
Outcome
Modernization released with control—not just speed.
Sitecore 10 and the B2B/B2C capabilities went live together. UAT completed on schedule, quality controls helped keep UAT defects comparatively low for the scale, and proactive monitoring surfaced blockers before they grew into schedule failures.
8 → 10
Sitecore modernization path
10–15
people aligned across delivery
On schedule
UAT completion
- —Coordinated a Sitecore 8 → 9 → 10 transition and B2B/B2C release.
- —Supported custom Sitecore libraries where standard platform behavior was insufficient.
- —Maintained delivery focus through a highly compressed, fixed-price timeline with limited overtime.
Platform & practices
Sitecore XP/XCJiraJQLConfluenceUATB2B/B2CRelease governance
“In enterprise modernization, alignment is a technical capability. Clear ownership, early risk signals, and credible communication make complex delivery more predictable.”