Remove 2011 Remove Initiating Remove Process Remove Software Development
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 333
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.

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: 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

In-Depth: How Easily Biases Distort What We Believe (In The Workplace)

Scrum.org

Initially coined by Wason (1960), this bias manifests when we only look for confirmation of our beliefs. When organizations start initiatives or change programs and only see or look for evidence that supports the belief that it is working, but fail to see where it doesn’t work or even causes damage. Confirmation bias. Survival bias.

2015 213
article thumbnail

Become a Skilled SAFe® SPC | Safe Program Consultant

Agilemania

2011 marked a new beginning in the era of large-scale software project management. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for attaining business agility using Lean, Agile, Systems Thinking, and DevOps to manage large scale software development. . But what is SAFe? .

article thumbnail

Reading List for the Cone of Uncertainty

Herding Cats

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? This problem is visually depicted in the “cone of uncertainty” diagram which was initially conceived by Boehm. 1, January 2011. "A

2012 48
article thumbnail

The Complete Guide to Scaling Agile and SAFe for Business Agility

Agilemania

The entire organization had to be in the process, not just a few self-managed teams. . In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise.

Agile 98