Remove Cadence Remove SCRUM Remove Software Review
article thumbnail

Getting started with a Definition of Done (DoD)

Scrum.org

In my last post about Professional software teams creating working software David Corbin made a good point. Updated to reflect the 2020 Scrum Guide! TL;DR; Your Developers are ultimately responsible for creating done increments of working software. The 2020 Scrum Guide. Done Increments. So what do you do?

article thumbnail

How We Reduced Cycle Time from 164 Days to 8 Days in 6 Months

Scrum.org

In December 2020, my friend Adrian Galarza and I delivered a Scrum.org Scrum Pulse Webinar - A Cycle Time Journey: 164 to 8 Days in 6 Months that summarized the journey of Adrian’s Scrum Team. Due to horrible time-management on my part, we could not answer all the questions in the webinar, so we are answering them in this blog instead.

Cadence 222
Insiders

Sign Up for our Newsletter

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

article thumbnail

Release planning and predictable delivery

Scrum.org

Updated to reflect the 2020 Scrum Guide! TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software.

article thumbnail

Beyond Mechanical Scrum

Scrum.org

The teams at his company had well established cadences for their Scrum events; well-oiled Daily Scrums that are done within 15 minutes and result in transparency of what the team will do for the next 24-hours. They are releasing software after every 2-week sprint. Get the basics in place and yes, you are doing Scrum.

article thumbnail

“Agile Is Just for Software” and other Scrum Myths

Scrum.org

Scrum is the most popular Agile framework. According to the latest State of Agile survey from Digital.ai, 90% of teams who are using an Agile framework are using Scrum. I like to think that this is because Scrum is a goldilocks framework … with just enough - but not too much - structure. That is the power of Scrum.

SCRUM 179
article thumbnail

Use MVIs for team improvements

Kiron Bondale

Whether a team uses a scheduled cadence for reviewing their WoW such as the use of retrospectives in Scrum, or they use a just-in-time approach they will come up with improvement ideas. Coding standards, coding reviews, non-solo coding, test-first development, and automated code quality tools are just a few choices.

article thumbnail

5  misconceptions about Scrum's Sprint Event

Scrum.org

Many well-meaning Scrum practitioners have misconceptions about Scrum, which sometimes leads to creating “rules” that do not exist in the framework. Scrum is deliberately incomplete because the framework is used in complex environments where simple best practices won’t fit all situations.

SCRUM 197