Remove 2011 Remove Meeting Remove Process Remove Software Developers
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. He leads scrum meetings.

SCRUM 338
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). Phases, meetings, time-boxes, events.

2010 232
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

We are entering the Deployment Phase of the Digital Age

Scrum.org

Of course, this list changes with the markets, but if you compare that to 2011, the list is 60% different. Scrum, agile thinking, modern software development working practices are synonymous with Digital Technology and have evolved out of the fundamentally different characteristics of the opportunity presented by technology.

article thumbnail

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Take for example the deployment of an ERP system, the installation, and startup of a process control system, the release of a suite of embedded software controllers for a car, aircraft, petrochemical plant. risks that may prevent the end item from performing as intended or not meeting performance expectations.

article thumbnail

SAFe Simply Explained (Part 1): Core Competencies and Principles

Inloox

High flexibility, adaptability and increased communication are just a few of the benefits that have led to significant improvements through the introduction of agile work processes in organizations. What usually started in software development can now be extended to the entire company and thus, change the way people collaborate.

article thumbnail

How To Base Your Beliefs About Agile On Evidence

Scrum.org

There are dozens of high-quality academic works to draw from, there are dozens of academic journals dedicated to (agile) software development (ASD) and change management. Some of the references in the paper “The impact of inadequate customer collaboration on self-organizing teams” by Hoda, Noble & Marshall (2011). That is great!

Agile 201