Remove Cadence Remove Software Remove Underperforming Technical Team
article thumbnail

How I transformed “multiple Scrum teams” into “multiple team Scrum”

Scrum.org

The PO’s are then unsure what needs to be developed. For instance, a lead developer or architect prepares the work for sprints ahead, acting as a proxy between the teams and the PO’s, splitting the requirements in tasks per team. I advise to start finding one person to be the single Product Owner for all teams.

article thumbnail

“Agile Is Just for Software” and other Scrum Myths

Scrum.org

According to the latest State of Agile survey from Digital.ai, 90% of teams who are using an Agile framework are using Scrum. That is why Scrum can be used in so many different contexts: because of its flexibility and the fact that Scrum provides just enough - but not too much - structure to enable teams to work together to deliver value.

SCRUM 207
Insiders

Sign Up for our Newsletter

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

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. TL;DR; Your Developers are ultimately responsible for creating done increments of working software. Developers needs to decide what Done means within the organisational context and the product domain.

article thumbnail

Don’t Blame Agile for Bad Agile

Velociteach

We should not blame Agile for bad Agile. Agile teams are empowered and collaborative. They provide the structure and practices to guide the teams. High-performing agile teams are characterized by the following: Psychological Safety. Team members are empowered. We developed our own lightweight practices.

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. Visualising your work on a physical or electronic board?

article thumbnail

Is SAFe Agile?

Leading Agile

It doesn’t mean they are bad. Agile is an incremental and iterative approach for developing software products. It’s typically best for small teams. The most common small team Agile methodologies are Scrum and XP, maybe Kanban, or a combination of the three. They didn’t have small teams. What is Agile?

Agile 133
article thumbnail

Don’t Say NoGet Them to Understand Your Team Delivery Capacity

Leading Agile

Do you, or the teams you work with, feel pressure from stakeholders to say “yes” to everything they ask for? I often see advice from coaches that teams should learn to say “no” to stakeholders. I often see advice from coaches that teams should learn to say “no” to stakeholders.