Skip to content
Skills Library
Management & product · Planning

azure-devops-scrum-master

/azure-devops-scrum-master

Support Scrum events and team improvement using Azure Boards. Use for sprint planning preparation, Sprint Goal risk reviews, daily progress briefings, impediment discussions, sprint reviews, and retrospective agendas in an Azure DevOps organization, project, and team.

Licence
MIT
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Support Scrum events and team improvement using Azure Boards. Use for sprint planning preparation, Sprint Goal risk reviews, daily progress briefings, impediment discussions, sprint reviews, and retrospective agendas in an Azure DevOps organization, project, and team.

Original author description

Support Scrum events and team improvement using Azure Boards. Use for sprint planning preparation, Sprint Goal risk reviews, daily progress briefings, impediment discussions, sprint reviews, and retrospective agendas in an Azure DevOps organization, project, and team.

How it works

  1. Prepare a sprint briefing
Original SKILL.md headings · 26 lines, 369 words
SKILL.md preview
---
name: azure-devops-scrum-master
description: Support Scrum events and team improvement using Azure Boards. Use for sprint planning preparation, Sprint Goal risk reviews, daily progress briefings, impediment discussions, sprint reviews, and retrospective agendas in an Azure DevOps organization, project, and team.
---

# Scrum Master support

Read [Azure Boards context](../azure-devops-workflow/references/boards-context.md) before fetching work. Follow its organization selection, process discovery, evidence, and edit rules.

For synchronized Jira counterparts, use the [Jira bridge](../azure-devops-jira-bridge/SKILL.md) to resolve record identity and field ownership before combining evidence.

Identify the requested event and the team's decision to prepare. Ask for the Sprint Goal and relevant Definition of Done or working agreements if they are unavailable. Label a goal suggested from backlog content as a proposal.

## Prepare a sprint briefing

- Resolve the team and iteration and read its work items, estimates, dates, and relevant parent or dependency links.
- Summarize progress toward the stated Sprint Goal using linked work items. Separate observed facts, possible risks, and questions.
- Surface explicit blockers, unresolved dependencies, work in progress, and items needing a team decision. Distinguish an explicitly blocked item from an item that merely has a dependency or a high age.
- Report counts only for the reviewed scope. Keep backlog items and tasks separate. Use estimate totals only when the units and scope are comparable.
- For planning, identify candidate work and capacity questions. Ask the Developers to confirm capacity, estimates, and the Sprint Backlog.
- For a daily briefing, prepare concise prompts about progress toward the goal and impediments. Use the team's preferred meeting format.
- For a sprint review, map completed evidence to the goal and prepare demo topics and stakeholder questions. Confirm completion against the team's Definition of Done.
- For a retrospective, distinguish observations from hypotheses, prepare discussion prompts, and propose one or two improvement experiments with suggested owners and review dates for the team to confirm.

Return the organization, project, team, iteration, evidence coverage, goal, observed progress, risks with work item links, and decisions or discussion prompts. Add the event-specific agenda when useful. State missing evidence near the conclusion it affects.

Support the Scrum Master and team in facilitation. Leave backlog ordering to the Product Owner and sizing and delivery commitments to the Developers. Avoid individual productivity rankings and unsupported performance judgments. Request historical evidence before reporting velocity, carry-over, or cycle-time trends.

Example requests include "Prepare a planning briefing for Team Dispatch in Contoso" and "Review this sprint's risks to the Sprint Goal."

Versions

The database has no other skills named azure-devops-scrum-master.

Database snapshot: 13.11.2026 · package version b422adb3681c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100scrum
    Scrum framework fundamentals: roles, events, artifacts, sprint goal writing, and retrospectives. Use to plan a sprint, write a sprint goal, or facilitate a Scrum event.
  • 100sprint-planning
    Facilitates Sprint Planning by helping the Scrum Team craft a Sprint Goal, select Product Backlog items, and build an initial Sprint Backlog. Use when anyone says things like "let's plan the sprint", "sprint planning", "what should we work on this sprint", "help us pick stories…
  • 100scrum-master
    Use when teams need facilitation, process optimization, velocity improvement, or agile ceremony management—especially for sprint planning, retrospectives, impediment removal, and scaling agile practices across multiple teams.
  • 90scrum-event-sprint-retrospective
    Guide Sprint Retrospectives to identify improvements. Use when reflecting on sprints, planning process improvements, or executing improvement actions.
  • 100audit-sprint-ado
    Audits a completed or in-progress Azure DevOps sprint against Scrum and ADO best practices — checks Sprint Goal presence, work item hygiene, state transitions, field completeness, capacity tracking, and Definition of Done compliance. Surfaces findings with severity levels and…
  • 100agile-scrum
    Use this skill when the user says 'set up scrum', 'sprint planning', 'sprint goal', 'daily scrum', 'sprint review', 'definition of done', 'story points', 'scrum events', 'scrum roles', 'sprint length'. It sets up and runs Scrum per the 2020 Scrum Guide (accountabilities, events…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.