Day-to-day operating brief
What Scrum Master work looks like in practice
A Scrum Master helps a delivery team use an agreed agile framework, facilitates events, exposes impediments and coaches improvement. The role supports transparency and collaboration but does not own product priority, technical design or employee performance decisions unless separately assigned. Terms should identify teams, locations, facilitation duties, access to delivery metrics, organisational escalation, training, confidentiality and the boundary with product owners and managers. Retrospective actions should have owners, intended observations and review dates rather than disappear into meeting notes. Facilitation must make room for quieter or remote participants without manufacturing consensus. Recurring impediments that exceed team authority need organisational escalation, not repeated discussion framed as local improvement. Delivery metrics should be used to ask questions about flow, ageing and blockage, not to set arbitrary team quotas. Changing estimation behaviour can improve a chart without improving customer outcomes or the time work actually spends waiting.
Individually written and reviewed against the maintained role record.