article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Scrum.org

The first, official version of the Scrum Guide was released in February 2010. So, how was Scrum defined before 2010 then? How did its definition evolve before and after 2010 and become the framework that we know today? The Scrum Guide” by Ken Schwaber and Jeff Sutherland (2009, 2010).

2010 232
article thumbnail

Top PM 10 Articles of All Time

Rebel’s Guide to PM

My project alphabet was a popular post of 2010 and inspired Derek Huether to write a book about zombie project management. This was one of my favorites: about Pareto and the 80/20 rule and how some stuff just needs to get done. Don’t know what that is? Here’s the scoop on zombie projects and how to kill them ).

2007 323
Insiders

Sign Up for our Newsletter

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

article thumbnail

7 Hidden dangers of project management (Or why even well-planned projects sometimes fail)

Rebel’s Guide to PM

For example, in June 2010 Chrysler merged with Fiat. However, as much as we would like to keep everything on the same page, changes happen. Whether it’s the client who decided to change the scope of the work or the team faced some unforeseen difficulties, changes can kill a project. The merger was not a successful one.

Planning 418
article thumbnail

The Fascinating Origin of the Term 'Scrum Ceremony'

Scrum.org

The people most likely to use the term 'scrum ceremonies' were those that did a Scrum course before 2010. Scrum Training Before 2010. Between Scrum's formal introduction in 1995 and the publication of the first Scrum Guide in 2010, Ken Schwaber and Mike Cohn delivered most Scrum training courses. I followed the thread.

2010 158
article thumbnail

How to improve cross-functionality within your team?

Scrum.org

2010) and Verwijs & Russo (2022) found that team effectiveness is inhibited when teams lack such cross-functionality. Cross-functionality in teams has been linked to shorter development time ( Eisenhardt & Tabrizi, 1995 ) and increased quality and improved performance ( Keller, 2001 ). For Scrum teams specifically, Moe et.

2001 226
article thumbnail

In-Depth: How To Create Better Work Agreements For Your Team

Scrum.org

It has been linked to higher performance and motivation (Mathieu et al, 2000), increased effectiveness (Kearny, Gebert & Voelpel, 2009), and generally explains a substantial amount of the variance (~19%) in the effectiveness of teams (De Church & Mesmer-Magnus, 2010). You can read more about this here. How to coordinate the use of skills.

2004 227
article thumbnail

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

Scrum.org

2010) reviewed 28 scientific studies that investigated how Scrum is associated with overall business outcomes. Many studies have identified high autonomy as an important prerequisite for Agile teams ( Moe, Dingsøyr & Dybå, 2010 ; Donmez & Gudela, 2013 ; Tripp & Armstrong, 2018 ; Melo et. 2010, April). Cardozo et. References.

Agile 206