Engagement Path
From first conversation to handback — what a Web Valley Hub coaching engagement looks like week by week.
Coaching for software service teams works best when everyone knows what the weeks will feel like. This page is the path we follow for the flagship Agile Delivery Coaching offer. Shorter offers compress the same ideas.
01 — Discovery conversation
A thirty-to-forty-minute call covering team size, client mix, current ceremonies, and the failure you are trying to stop repeating. We say clearly if we are not the right fit — for example when the real need is staffing, not facilitation.
02 — Observation week
We attend your existing planning, daily coordination, and review without redesigning them. Notes stay internal until the first intervention checkpoint. The goal is evidence, not theatre.
03 — Intervention weeks
Co-facilitation begins. Working agreements are drafted in the room with the people who must live them. Midway, sponsors hear a plain progress brief: what improved, what is still brittle.
04 — Stabilise
Your leads run the ceremonies. We observe and correct. If the room collapses without us, we extend intervention rather than pretend handback happened.
05 — Close & continuation
A closing session documents agreements and sets a two-sprint experiment the team will run alone. Optional follow-up check-ins are available as separate facilitation days.
Protect calendar blocks
Coaching days need the delivery lead and most of the squad present. Partial attendance produces partial results.
Share board access early
Read-only access to the sprint board and a sample acceptance pack save the first week from administrative delay.
Name a sponsor
Someone who can approve process changes without a committee keeps momentum when intake rules need rewriting.
Ready to walk the path?
Review coaching offers or request a conversation with your preferred start window.