article thumbnail

21 Sprint Retrospective Anti-Patterns — Scrum Anti-Patterns Guide 2022

Scrum.org

Hence, learn more about 21 common Sprint Retrospective anti-patterns that will hold back your Scrum team. ???? Join Stefan in one of his upcoming Professional Scrum training classes ! The Scrum Guide on the Sprint Retrospective. The Scrum Team identifies the most helpful changes to improve its effectiveness.

SCRUM 199
article thumbnail

Epic Fail - Why Product Backlog Refinement is Essential for Scrum Teams?

Scrum.org

Part 1 intends to focus on the Scrum Team, Part 2 will be released shortly after our Webinar on April 29th and will focus on the “Epic” challenges agile leaders are facing. Product Backlog is not an event in Scrum, but has its place in the Scrum Guide and therefore the Scrum Framework.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

15 Sprint Review Anti-Patterns — Scrum Anti-Patterns Guide 2022

Scrum.org

Moreover, how did the previous Sprint contribute to our Scrum team’s mission? Answering these questions and adapting the Product Backlog in a collaborative effort of the Scrum Team with internal and external stakeholders is the purpose of the Sprint Review. The Scrum Guide on the Sprint Review.

SCRUM 199
article thumbnail

Fixing Your Scrum: A Forensic Product Backlog Analysis (Part 1)

Scrum.org

Garbage in, garbage out: No matter whether your team chose Scrum for the right purpose—solving complex, adaptive problems. No matter whether your Scrum Team’s product quality is top-notch or whether your teammates embrace self-management to the fullest. Engage the team in a further inspection of the items in question.

SCRUM 203
article thumbnail

Forensic Product Backlog Analysis – Making Your Scrum Work

Scrum.org

Garbage in, garbage out: No matter whether your team chose Scrum for the right purpose—solving complex, adaptive problems. No matter whether your Scrum Team’s product quality is top-notch or whether your teammates embrace self-management to the fullest. Engage the team in a further inspection of the items in question.

SCRUM 148
article thumbnail

Event Series: Practical Kanban with MS Project Agile

MPUG

The most well-known framework for iteration-based Agile is Scrum , while Kanban represents flow-based Agile. The team pulls a feature or work item from the backlog based on the available capacity, executes the work, and when complete, delivers the work incrementally. Now, the MS Project Agile software allows both Scrum and Kanban.

Agile 52
article thumbnail

Practical Fibonacci: A Beginner's Guide to Relative Sizing

Scrum.org

A traditional or Waterfall software development lifecycle includes a long and detailed planning period to define requirements before beginning development. In an Agile approach, the developers only know enough to get started–they don’t know everything needed to complete an item. Ab solute vs. Relative Sizing.