Author

Wayne Arendse

Delivery & Transformation Lead

20+ years in technology delivery and operational transformation.

Brings the operating system: strategy-to-execution alignment, measurable delivery, and transformation leadership for programmes that have gone off the rails.

Lean Six Sigma Master Black Belt — operations and transformation
SAFe 6 Certified Practitioner · PMP — project and programme management
Finance & Quantitative Modeling — solutions anchored in financial models
Data Science, Python & ML (IBM · Meta) — stable software and data engineering

Credentials

20+ years delivery & transformationPMP · Lean Six Sigma MBB · SAFe 6Finance & Quantitative ModelingData Science, Python & ML — IBM & MetaScaled orgs 7 to 85 across 35 countries

Essays by Wayne Arendse

Business Cases2026-06-10· 6 minThe €220k a month nobody was countingHow a healthy-looking delivery pipeline quietly leaked a fifth of a million euros a month, and why no dashboard showed it.Delivery2026-08-07· 20 minSoftware Project Rescue: How to Know Whether a Project Can Be SavedA six-factor decision framework — business value, remaining work, architecture, team capability, vendor risk, time to market — for deciding whether to rescue, rebuild, replace, or stop.Delivery2026-08-18· 18 min12 Warning Signs Your Software Project Needs RescueThe warning signs that predict a project will not self-correct cluster into three categories — operational, technical, and stakeholder — and how they combine matters more than how many you count.Delivery2026-09-05· 15 minThe First 72 Hours of a Software Project RescueSix moves in a deliberate order — access, evidence, critical path, production risk, decision rights, and stakeholder communication — that determine whether a rescue stabilizes or makes things worse.Delivery2026-09-09· 16 minSoftware Project Rescue vs Rebuild: How to DecideThe rescue-vs-rebuild question is usually the wrong frame. There are four real paths — stabilize, modernize, rebuild selectively, restart — and the right one is determined by evidence, not instinct.Delivery2026-09-13· 17 minHow to Take Over a Software Project From an Underperforming VendorA vendor takeover is a knowledge-extraction operation — three phases, six workstreams, and a plan for when the outgoing vendor will not cooperate.Delivery2026-09-16· 15 minHow Much Does Software Project Rescue Cost?Rescue cost is driven by what an assessment finds, not project size. Six cost drivers, a worked example, and when rescue stops being the economically correct call.Delivery2026-09-20· 14 minWhy Software Projects Stay 90% Complete for MonthsThe missing 10% clusters into five categories a weak definition of done leaves out: integration, quality, deployment, security, and acceptance work.Delivery2026-09-23· 14 minSoftware Project Turnaround Plan: What Leadership Should Expect in the First 30 DaysA credible turnaround plan replaces vague reassurance with verifiable deliverables — six elements, a week-by-week timeline, and what leadership should be able to check directly by day 30.