Remove 2013 Remove Software Development Remove Software Review
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. Scrum is part of agile software development and teams practicing agile. What Is the Scrum Methodology? Learn More!

SCRUM 353
article thumbnail

Dependency Management – the Good, the Bad, the Ugly

Scrum.org

Dependencies are an epidemic in software development. Sutherland, Scrum Guide, 2013. Thing we hear (or say): Organizational Design: My team is mostly back-end; we rely on another team for the (fill in with any component of software – front end enhancements, database layer, integration, API). Schwaber and J.

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

In-Depth: The Evidence-Based Business Case For Agile

Scrum.org

So we went to Google Scholar and searched for review articles. 2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. A strength of such a review is that it allows for the identification of patterns across many studies. Journal of systems and software , 81 (6), 961–971.

Agile 225
article thumbnail

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

Scrum.org

al, 2013), healthcare professionals (Papathanasiou et. 2013), and in the workplace (Manganelli, Thibault-Landry & Forest, 2018). For example, I (Christiaan) love the thrill of solving a hard coding problem. Burnout–depression overlap: A review. Clinical psychology review , 36 , 28–41. Source: Wikipedia. .

article thumbnail

A Review Of Scrum For Kanban Teams

Digite

It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. As I wrote in 2013, Scrum and Kanban both share a use of values to encourage users of the methods to behave a certain way. You should go read it now.

article thumbnail

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

Scrum.org

Wang et al (2006) studied software teams tasked with ERP implementations and found that cohesive teams performed significantly better than less-cohesive teams. However, several studies show that cohesion positively impacts performance only in later stages of team development (e.g. Bradley et. Or if these processes can be fast-tracked.

article thumbnail

In-Depth: How Easily Biases Distort What We Believe (In The Workplace)

Scrum.org

When comparing different approaches to develop software, survival bias can lead someone to conclude that plan-driven approaches work well based on a few success stories they have where they did. All drivers consider their own driving skills above average (Roy & Liersch, 2013). Psychological Review, 94 (2), 211–228.

2015 230