The Product Owner Who Has to Ask Permission
At Meridian Health, the person holding the Scrum Master accountability is also the engineering line manager who conducts annual appraisals and approves leave for the same seven Developers. Sprint Planning is attended by Priya, who holds the Product Owner title, but every ordering decision is confirmed afterwards by a five-person Portfolio Board that meets fortnightly. Sprints are three weeks; the Board re-prioritises monthly. Developers routinely ask the Scrum Master to assign Monday tasks, and two Developers were recently told by their line manager to stop attending the Daily Scrum because it 'eats 45 minutes a week'. Priya has begun writing tasks directly into the tracker with hour estimates so the Board can see progress.
1. Which Scrum accountabilities and events are being undermined, and what is the consequence for the team's ability to self-manage?
Read the worked answer
Product Owner. Priya has the title but the Portfolio Board orders the backlog. When ordering is split between a person and a fortnightly committee, the team has no single source of priority - exactly what the accountability exists to prevent. Writing hour-estimated tasks is the PO reaching into work the Developers own.
Scrum Master. The same person appraises the people they are meant to coach. Developers cannot raise impediments candidly to someone who controls their rating, and the SM cannot serve two masters when the impediment is line management itself.
Developers. Asking the SM to assign Monday tasks is learned behaviour from a command-and-control history; self-management will not appear while planning belongs to someone else. Being told to skip the Daily Scrum removes their only daily inspection of the plan.
Events. A three-week Sprint combined with monthly external re-prioritisation routinely invalidates Sprint Goals from outside.
The consequence: nobody in the room can say what the team is trying to achieve this Sprint and mean it. Self-management is not a motivational problem here; it is structural.
2. The organisation cannot remove the Portfolio Board this quarter. What is the most useful thing the Scrum Master can do in the next 30 days?
Read the worked answer
Do not spend the quarter fighting a body you cannot dissolve. Convert it from an orderer into a goal-setter.
- Get the Board to agree one objective for the quarter - a Product Goal - within which Priya is empowered to order. One page, written, endorsed by the Board chair. This is the highest-leverage change available.
- Bring two Board members to a Sprint Review and let them see an Increment. Committees change behaviour faster from evidence than from coaching.
- Publish a short decision-rights map: what the Board decides, what the PO decides, what the Developers decide. Fortnightly re-prioritisation is a symptom of ambiguity, not of malice.
- Separate the SM accountability from line management, even partially - move appraisals elsewhere or reassign the role. If that is impossible this quarter, say so openly in the retrospective so the team understands the constraint is organisational rather than personal.
- Coach Priya on declining requests in writing, with a reason and a date.
3. Priya wants to add hour estimates to every task so the Board can track progress. What is the best response?
Read the worked answer
Answer the question underneath the request. The Board wants visibility and control; hour estimates give an illusion of both while costing real money - they corrode self-management and are wrong within days.
Offer what the Board actually needs:
- A forecast against the agreed quarterly objective, expressed as a range derived from observed throughput and the current Definition of Done.
- A Sprint Review where they see working software, plus a Sprint Goal per Sprint so progress is legible as outcomes rather than hours.
- Early escalation of the risks that are genuinely the Board's to resolve: dependencies, missing skills, decisions they owe the team.
If the Board still insists, be honest about what is happening. Developers may record remaining work in the Sprint Backlog because they find it useful - that is their call. If the organisation imposes hour tracking as policy, the Scrum Master should make the cost visible and record it as an impediment rather than pretend the practice is free.