Remove Development Team Review Remove Software Review Remove Survey
article thumbnail

How agile is your team (and what you can do about it!)

Rebel’s Guide to PM

Did you know, one survey found that the most common reason to adopt agile is to be able to deliver products more quickly? Yet the same survey found that 75% of people did not believe their organisation had a culture that supported agile ways of working. Discovering the recipe for team agility. This matches my experience.

article thumbnail

Scrum Master Engagement Patterns: The Development Team

Scrum.org

Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single Scrum Team. Much to the surprise of many readers, the direct Scrum Master engagement with a single Scrum Team of average size and a typical 2-week Sprint turned out to be about 12 hours per week.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

SAFe®’s NPS® Score as a Scaling Framework Is -56 According to 505 Survey Participants

Scrum.org

Therefore, back in 2017, I ran a first survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. Survey Data. Between December 13, 2021, and January 27, 2022, 505 peers participated in the survey. Additionally, I distributed the survey link via blog posts and various social media postings.

Lean 183
article thumbnail

Why Great (Scrum) Teams Have A Mind Of Their Own

Scrum.org

What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to develop team cognition and become high-performing. Pictures of a session where we created a skill matrix with a team.

2010 231
article thumbnail

Self Managing Defects escaping into Prod

Scrum.org

Code is reviewed by a different team member before it is committed. About 2 months ago, the team noticed an uptick in the number of production defects they had to fix urgently. Due to this, the team adopted the practice of swarming which enabled them to minimize the impact of their production defects on the customer.

article thumbnail

The Sprint Planning Checklist

Scrum.org

The following Sprint Planning checklist includes tasks for everyone on the Scrum Team: Preparing the Sprint Planning: T-2 : Address the number of open tickets in the “code review” & “ready for acceptance columns.” Ask the team members to focus on moving tickets to “Done” before starting work on new tickets.

Planning 225
article thumbnail

Innovation within a Scrum Team

Scrum.org

There are two metrics from Evidence-based management (EBM) Ability-To-Innovate Area, that are related to each other and help us to understand how much is spent on innovation and on code maintainance throughout the sprints: innovation rate : the percentage of budget spent on innovation. customer or end-users satisfaction surveys.