Delivering
software that
matters.

When I joined this engagement there was no SOW, no SOP, no RAID log and no agile process in place. The client had an ecommerce platform running on physical infrastructure in Malaysia and needed it migrated to AWS while keeping the payment checkout flow secure and the business running.

My first two weeks were spent onsite in Malaysia doing discovery. I sat with infrastructure teams, payment vendors and business stakeholders to map out every data flow and integration touchpoint before writing a single project document. There was no existing structure to inherit and no prior delivery lead to hand over from.

From that discovery I built the project baseline from scratch. This included the SOW, SOP and SLAs, a RAID log, a dependency map and a steering cadence. I also introduced agile practices to a team that had never worked that way, coaching them through Scrum one sprint at a time.

The payment integration workstream carried the highest risk. I coordinated between development, QA and the third party payment gateway to make sure the checkout journey was both secure and compliant before go live. In parallel I managed the data migration covering customer records, product catalogues and transactional data, making sure nothing broke during the move to AWS.

By the time we reached go live the numbers told the story. Delivery predictability improved by 15 percent. Manual testing effort dropped by 40 percent once automated regression suites were in place. The go live itself was clean with no major incidents.

What this taught me is that governance is not something you wait to receive. When there is no playbook the job is to build one fast enough that the team can move with confidence while you are still building it.

Midway through a release cycle our sprint velocity and dependency data started telling a different story than our original commitment. The integration work was slipping and the gap between what leadership expected and what the data showed was widening.

Rather than wait for the gap to become a crisis I brought it forward early. I pulled together sprint velocity trends, dependency mapping and a risk register update into a clear RAG status report. Then I built an options paper for leadership with two real choices, slip the release date or descope certain features and ship on time.

I presented both options with their trade offs laid out plainly, no hedging and no burying the bad news. Leadership chose to descope. We delivered a stable release on the original date and I followed up immediately with a plan for the deferred scope so nothing fell through the cracks.

This is the kind of decision I try to bring to every programme. Data should drive the conversation, not opinions or optimism. And when you give stakeholders a clear choice instead of a vague warning, they can actually decide.