Remove 2017 Remove Agile Remove Development Team Review Remove Underperforming Technical Team
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?

article thumbnail

Agility and Scrum According to OpenAI’s ChatGPT — Be Surprised!

Scrum.org

TL; DR: Business Agility, Scrum and Generative AI’s Take on Getting There. I thought it might be fun to ask ChatGPT a few questions about business agility in general and Scrum in particular. . ???? You can sign up here for the ‘Food for Agile Thought’ newsletter and join 36,000-plus other subscribers. ??

ChatGPT 197
Insiders

Sign Up for our Newsletter

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

article thumbnail

21 Sprint Retrospective Anti-Patterns

Scrum.org

The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint. By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint.

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. Source : Scrum Guide 2017. .

article thumbnail

In-Depth: The Science On Sustainable Pace, Stress, And Motivation

Scrum.org

How sustainable is your pace as a developer? This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. The initial practice was for developers to work no more than 40 hours a week.

article thumbnail

Working Remotely? This Will Hit You Next!

Scrum.org

Despite the rapidness of the change, moving to remote worked surprisingly well for many teams, because they were used to some degree of remote work before. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like.

article thumbnail

Scrum Master Anti-Patterns — 20 Signs Your Scrum Master Needs Help

Scrum.org

They run from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself. Read on and learn in this post on Scrum anti-patterns how you can identify if your Scrum Master needs support from the team. The Scrum Master is a servant-leader for the Scrum Team. Source : Scrum Guide 2017.

SCRUM 134