Remove 2002 Remove Agile Remove Software Development
article thumbnail

Top 10 Project Management Methodologies – An Overview

ProjectManager.com

We’ll go through some of the most popular project management methodologies, which are applied in many sectors such as software development, R&D and product development. Agile Methodology. What It Is: In a nutshell, Agile project management is an evolving and collaborative way to self-organize across teams.

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. Scrum Values.

SCRUM 397
Insiders

Sign Up for our Newsletter

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

article thumbnail

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

Scrum.org

What is the business case for Agile teams? We think we do well to base our beliefs about Agile more on evidence. This post is our attempt to bring an evidence-based perspective to the business case of Agile teams. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams.

Agile 225
article thumbnail

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

Scrum.org

Software development is (generally speaking) very complex. Scrum/Agile) are more suitable to deal with complex problems because they are more attuned to our cognitive abilities. It is a mental process and a limited mental resource (Ashcraft, 2002). Cognitive paradigms, applied to Scrum / Agile. References.

2002 225
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).

2010 234
article thumbnail

Questioning Agile Dogma

Leading Agile

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. How can the same principle be a good idea in 2002 and a bad idea in 2019? ” A lot more is possible than was imagined when “Agile” was first defined.

Agile 116
article thumbnail

Scrum: A Brief History of a Long-Lived Hype

Gunther Verheyen

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 paper “SCRUM: An extension pattern language for hyperproductive software development” by Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber and Jeff (..)

2010 144