Remove Development Team Review Remove Groups Remove Underperforming Technical Team
article thumbnail

Development Team Anti-Patterns

Scrum.org

TL; DR: Development Team Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the Development Team in Scrum. Do you want to get this article in your inbox?

article thumbnail

Dependency Management – the Good, the Bad, the Ugly

Scrum.org

Does your team struggle to get items to Done? Do they experience a high amount of spill-over into the next cycle because they are waiting on another team or another person? Do items sit in a blocked state and age out while waiting on other teams or people to complete work? Dependencies are an epidemic in software development.

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

Scrum Methodology: Roles, Events & Artifacts

ProjectManager.com

The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. The bad news, it’s hard to master. Scrum is part of agile software development and teams practicing agile.

SCRUM 353
article thumbnail

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

Scrum.org

I was working with various groups over the last year and noticed some commonalities in the problems they faced. The PO’s are then unsure what needs to be developed. I advise to start finding one person to be the single Product Owner for all teams. The Product Owner should develop an inspiring vision and a plan to make it happen.

article thumbnail

Why psychological safety enhances the abilities of the Scrum Team

Scrum.org

Long has spoonfeeding solutions and off-the-shelf feature descriptions prevailed in many development teams. Although some issues might have been fixed, I rarely see the full potential of a Scrum Team being achieved. Going all-in on predefined features fails to capitalize on hidden ideas in the brains of team members.

article thumbnail

My Experience With Growing A Developer Culture

Scrum.org

For years, I’ve fulfilled the role of Scrum Master for many different organizations and Scrum Teams. These teams were mostly focused on software development. These organizations were able to attract the smartest developers and create products customers loved. Sprint Review at Schiphol Airport with lot’s of stakeholders.

article thumbnail

15 Sprint Review Anti-Patterns

Scrum.org

TL; DR: 15 Sprint Review Anti-Patterns. Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns. Are we still on the right track?