Resolved Issues

Problems that are openly raised and quickly addressed during Scrum of Scrums meetings; by resolving these cross-team issues in a timely way, teams improve coordination and reduce the chance of redesign and rework.

Key Points

  • Addresses cross-team impediments identified in the Scrum of Scrums.
  • Emphasizes transparency: issues are visible, owned, and tracked to closure.
  • Timely resolution limits dependency risks and cascading delays.
  • Successful resolution improves alignment and lowers rework and redesign.

Example

Three Scrum Teams building a shared platform hold a Scrum of Scrums. An API change is causing integration failures. The teams agree on a revised API contract, assign an integration lead to implement it, and validate the fix within two days. The item is marked as a resolved issue, preventing rework across teams.

PMP Example Question

During a Scrum of Scrums, two teams report conflicting database migrations. The group assigns an owner to create a unified migration plan and monitors progress until the conflict is eliminated. What is the best term for the outcome once the conflict is addressed?

  1. Resolved Issues
  2. Product Increment
  3. Definition of Done
  4. Release Plan

Correct Answer: A — Resolved Issues

Explanation: The conflict was raised and closed through the Scrum of Scrums, improving inter-team coordination and minimizing rework, which characterizes a resolved issue.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your career!

HK School of Management and Technology offers training in project management, job-search strategies, and career growth. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More