Remove 2007 Remove SCRUM Remove Software Review
article thumbnail

Five reasons why Scrum is not helping in getting twice the work done in half the time

Scrum.org

Scrum doesn’t help complete the product faster rather than how quickly a team can release a product. I worked as a product owner for my first product in 2007–08 to manage the insurance lifecycle for a major insurance company in America. They got training on Scrum, understood concepts, and formed teams, but struggle to commit.

article thumbnail

On Technical Debt And Code Smells: Surprising insights from scientific studies

Scrum.org

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why is code quality so often an issue? Why do software teams?—?despite But also a field that has much to say about code quality and how we can be better developers. Technical Debt and Code Smells.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Thinking By Sprinting: What Cognitive Science Tells Us About Why Scrum Works

Scrum.org

A while ago, I received an interesting scientific article from Gunther Verheyen titled “Getting Things Done: The Science Behind Stress-Free Productivity” (Heylighen & Vidal, 2007). Their paper provides useful insights into why the Scrum Framework might be so effective when it comes to managing complex work.

2002 225
article thumbnail

In-Depth: How Coherence And Cohesion Are Critical To Scrum

Scrum.org

Do your Daily Scrums feel like a pointless ritual where everyone just lists what they’ve done yesterday, and what they do will do today? And does your Sprint Review consist of team members listing their individual accomplishments? In our work with Scrum teams, we’ve been part of teams that had it. Some developed it over time.

SCRUM 235
article thumbnail

Scrum Master Engagement Patterns: The Development Team

Scrum.org

TL; DR: Scrum Master Engagement Patterns. Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single Scrum Team. The first article of this series will address the Scrum Master engagement with the Development Team.

article thumbnail

Diese 5 Probleme machen Scrum Teams langsam, das Leben der Entwickler zur Hölle und kosten dein Unternehmen 800.000 Euro (und wie du sie vermeidest)

Scrum.org

Diese 5 gngigen Probleme machen Scrum Teams langsamer. Die meisten denken, es liegt daran, dass Scrum nicht verstanden wurde. In Scrum Teams uert sich Multitasking im besten Fall dadurch, dass das Team an vielen Eintrgen des Sprint-Backlogs zur selben Zeit arbeitet. Abhngigkeiten behindern die Arbeit von Scrum Teams.

SCRUM 183
article thumbnail

In-Depth: Stable Or Fluid Teams? What Does The Science Say?

Scrum.org

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. This post is my attempt to do this. This post is part of our “in-depth” series.