Remove 2011 Remove 2013 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. What Is the Scrum Methodology? Scrum Values.

SCRUM 335
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 228
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

But adherence to a framework or prescribed process does not guarantee agility. Adherence to a framework or prescribed process does not guarantee agility.”. I prefer a process-based definition of agility. Although we used Scrum teams for our investigation, these processes are generic enough to apply to Agile teams in general.

Agile 197
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

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

Scrum.org

Bushe and Chu (2011) identify seven situations that drive the use of fluid teaming in those environments: High turnover among employees, leading to changes in teams. Even a single change in team membership can disrupt that process, and consequently, make it harder for teams to become high-performing sooner. The need for fluid teams.

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. This uncertainty is modeled as a stochastic process of an inherently random physical model. Now To Risk Management.

article thumbnail

Estimating is a Learned Skill

Herding Cats

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . Here's some materials that provide the tools and processes needed to learn how to estimate. The Future of Systems-and Software Development.