Evidence from the floor
Client stories
Testimonials and longer notes from software service teams who sat through the coaching — including the uncomfortable midpoints.
Stand-ups stopped being a roll call. After the third coached sprint, engineers named blockers before the PO asked, and we cut the average carry-over stories from a fuzzy pile to a counted list on the board.
The facilitation intensive was shorter than I wanted, and that constraint helped. We practised one retrospective format until the room could close with owners instead of another parking lot.
Their assessment brief called out our estimation theatre more bluntly than our internal review had. Useful, though I wish we had budgeted a coaching follow-on in the same quarter — the gap after the brief felt abrupt.
Programming consulting office hours saved us from inventing story-splitting rules in Slack at midnight. Having a coach answer concrete backlog questions beat another generic agile webinar.
Extended note: Mid-contract rescue for a mobile build crew
A twelve-person service team building a client’s mobile release had burned two consecutive sprint goals after a late API dependency landed mid-sprint. Service Stonebase joined for an eight-week cadence coaching block. Week two’s readout was awkward: WIP limits existed on paper but every engineer held three “almost done” items. We redesigned planning to include a dependency check with the client’s integration contact before commitment, and coached the daily so unfinished work could not hide behind “waiting on them.”
By sprint five the team hit the agreed release slice without weekend crunch. The mild reservation from their PM: coaching required calendar discipline their account managers initially resisted. Once the sponsor protected the ceremony slots, the rhythm held.