Thursday, November 19, 2020

SCRUM GUIDE 2020 Release Summary


SCRUM GUIDE 2020 Release Summary


Here is what's changed and new in SCRUM Guide 2020



https://www.scrumguides.org/scrum-guide.html


Significant changes:


People

  • “Roles” no longer used as a term: now accountability designations rather than “roles”.
  • No more Development Team: now just one team including “Developers” plus Product Owner and Scrum Master.
  • Beyond “self-organising”: the Scrum Team is “self-managing” rather than “self-organising”.
  • Beefed-up Scrum Master role: Scrum Master explicitly a “true leader” with an explicit overall accountability for the Scrum Team’s effectiveness.

Events

  • “Why” topic added to Sprint Planning: Sprint Planning has 3 topics rather than 2 with the addition of Topic 1: Why focused on agreeing on a Sprint Goal.
  • Daily Scrum questions removed: the What did I do yesterday / today / impediment questions no longer appear.

Artefacts

  • “Lean thinking” added as a foundation.
  • Each artefact has a “commitment”: Product Goal for Product Backlog, Sprint Goal for Sprint Backlog and Definition of Done for Increment.
  • “Product Goal” commitment added: commitment is added. “Product” is explicitly defined: as a vehicle to deliver value.
  • Multiple increments during a Sprint: increments come into being as Product Backlog items reach Done.
  • Only Done Product Backlog items show in Sprint Review: whilst previously somewhat implicit, this is now explicit.
  • Product Backlog items not Done return to the Product Backlog: now also explicit.
  • Sprint Review not a gate to releasing value: explicitly debunks the misinterpretation that releasing must be coupled with Sprint Boundaries.

Minor changes
  • Multiple Scrum Teams focused on the same product now should share the same Product Owner.
  • Scrum is founded on “empiricism” rather than “empirical process control theory”.
  • It is explicit that the whole Scrum Team collaborates on the Sprint Goal. Sustainable pace in Sprints now explicit.
  • Sprint Backlog contains “work items” rather than simply plan comprising “work”.

No comments:

Post a Comment

Featured Post

Agile DevSecOps

Over the past few years Software Development have gone through some major changes including applications being moved to cloud and DevOp...

Popular Posts