Case Studies
01
The team that "did Scrum" but nothing shipped
Client context: A mid-sized Australian software product company with three cross-functional development teams building a trading platform for securities.
The problem / structure blocker: The teams ran stand-ups, sprint planning, and retrospectives, yet kept missing delivery. The real blocker was structural, not ceremonial: the person deciding what got built was outside the Daily Scrum, so sprint goals never survived contact with the stakeholder calendar. Engineers couldn't adjust the sprint backlog without seeking approval up a chain ... the power to decide had been lent, not distributed. Working product rarely shipped at the end of a sprint.
What we did: Delivered a Certified Scrum Master (CSM) course for the delivery team and a Certified Scrum Product Owner (CSPO) course for the product owners, then worked with leadership on the structure rather than the events, moving the decision-maker into the team loop, giving teams authority to adjust their backlog mid-sprint, and shifting management from command-and-control toward coaching.
Measurable-style outcome: Teams moved from shipping "almost-working" demos to delivering a genuine working increment at the end of each sprints. Release cadence improved from every 6 months to every Sprint; lead time on changes dropped from 9 months (on average) to 4 weeks.
What the team can do now: Plan and run their own Scrum events without waiting for permission, reset their own Sprint backlog when reality contradicts the plan, and point to regular shipped software as the proof of value.
02
The enterprise "Agile transformation" that kept resisting change
Client context: A large banking organisation running Scaled Agile (SAFe) across multiple delivery streams, with layered management and strong internal competition between siloed departments.
The problem / structure blocker: "Agile" had been written on team pages and events were held, but real agility hadn't followed. As Larman's Laws predict, middle management resisted the structural threats Agile exposes, and a layered hierarchy concentrated decision-making power at the top. Every improvement attempt was absorbed by the existing power structure.
What we did: Took a coaching-led path. Certified Scrum training for teams, plus senior-leadership consulting focused on distributed structure: flattening layers, converting managers to coaches, establishing an end-of-sprint customer review so working software (not slides) became the definition of done, and measuring agility by what shipped, not by ceremony attendance.
Measurable-style outcome: Development cycles shortened from 18 months to 3 months; product owners reported a clearer link between strategic goals and what teams actually built; team moral and satisfaction greatly improved.
What the team can do now: Sustain a pace of continuous, autonomous delivery without daily escalation, because the authority to decide now lives in the structure and not in one person's head or one manager's calendar.
03
From "too many priorities" to shipping every sprint
Client context: A fast-growing company whose one team kept re-prioritising mid-sprint, churning work and rarely releasing usable software in a sprint rhythm.
The problem / structure blocker: The team's sprint was theatre. Priorities were set outside the team's control and overridden mid-sprint, so commitment meant nothing. Conway's Law was visible too. Communication was shaped by where people sat on the org chart, not by what needed to be true for the product, producing fragmented systems. Value wasn't being delivered because working software wasn't shipping at the end of each sprint.
What we did: A combined CSM + CSPO engagement to build the skills on both sides of the agreement, facilitation and ownership, followed by a structural adjustment so the Product Owner had real authority over priorities and the team had the autonomy to adjust within the sprint. Coaching embedded retrospectives that fed a genuine continuous-improvement loop.
Measurable-style outcome: The team began shipping a usable increment at the end of every sprint. Scope-churn dropped sharply; product owners could commit to a goal and see it align with a release plan.
What the team can do now: Own the product goal end-to-end, prioritise autonomously using customer feedback, and importantly, survive the loss of a key person or manager, because the structure now embeds the decisions and capacity rather than relying on one individual.
