Product Owner / Scrum Master
We take on the key agile roles to maximise product value and smooth delivery, aligning technical teams and stakeholders. Holding the role is not about running rituals, it is about making calls.
What we do
Backlog management and prioritisation
A backlog ordered by value and risk, not by the order requests arrived. Each item carries a goal, an acceptance criterion and an estimate, and what is not a priority is said to be so rather than left waiting indefinitely.
Scrum ceremonies
Sprint planning, review, retrospective and daily, run in a format that serves the team. A ceremony that produces no decision is removed or reformed, not endured.
Agile coaching and continuous improvement
We work with the existing teams so they can hold the role without us in the end. An agile engagement that leaves the team dependent on the consultant has missed its point.
How we work
-
1
Diagnose before ritualising
Many teams already have the ceremonies and not the results. We first look at where value is lost: missing decisions, a vague definition of done, unmanaged external dependencies.
-
2
Hold the role for real
A Product Owner without the mandate to say no is not a Product Owner. We clarify that mandate with management before starting, as a condition of the engagement.
-
3
Hand over
Pairing with a future internal holder, then gradual withdrawal. Success is measured at the point where we are no longer needed.
What you get
- Structured and prioritised backlog
- Shared definition of ready and definition of done
- Established sprint rhythm and delivery cadence
- Team indicators tracked over time
- Handover plan to an internal role holder
Frequently asked questions
Are Product Owner and Scrum Master the same role?
No, and conflating them is a common cause of failure. The first decides what is built, the second how the team works. One person holding both ends up arbitrating against themselves.
Do we need to be agile already?
No. We also work with organisations in transition, where the first step is often to reduce work in progress rather than install a framework.
How long does an engagement last?
Long enough for the team to stand alone. Depending on starting maturity, from a few months to a year, with a gradual withdrawal rather than a hard stop.
Let's talk about your project
Tell us about your situation and we will come back with a first reading and the questions that matter.
Contact us