article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Scrum.org

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996). The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002). The book “The Enterprise and Scrum” by Ken Schwaber (2007).

2010 232
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). Butchibabu and her colleagues (2016) performed an experiment with 13 teams.

2004 236
Insiders

Sign Up for our Newsletter

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

article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Gunther Verheyen

For every source I have described the same three topics to show what Scrum consisted of at the time (regardless the different terms used), what the ‘definition’ of Scrum was at the time: Roles, responsibilities, accountabilities Controls, deliverables, artifacts Phases, meetings, time-boxes, events.

2010 141
article thumbnail

Agile. Creativity. Innovation.

International Institute for Learning

During the last two decades there has been the emergence of a number of software development methods as a response to the inefficiency of existing software development methods in rapidly changing environments (Highsmith, 2004). Fitzgerald, B (2009). Creativity in agile systems development: a literature review.

article thumbnail

Summary of Capabilities Based Planning

Herding Cats

This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world. This missing document is a root cause of many failures in tradition and agile software development. 1595 Spring Hill Road, Suite 250 Vienna, VA 22182 kossakowski@ebrinc.com. Lizotte, C. Nécaille, C.

Planning 109
article thumbnail

Risk Management Resources

Herding Cats

5887, 2009. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. 2128, International Technical Paper , 2016. Project Risk Management: Lessons Learned from Software Development Environment,” Y. Loewenstein, Elke U.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. 5887, 2009. Risk a Feelings,” George F.