Scrum.org

OCTOBER 19, 2022

And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We collected the data through our Scrum Team Survey. We worked with Prof.

Agile 197

Agile 2010 2013 2008 197

Gunther Verheyen

DECEMBER 26, 2023

We have three kids (2001, 2003, 2013) of which the two oldest (sons) have a disability ( Duchenne and Down Syndrome ). My work as an independent Scrum Caretaker via my one-person company Ullizee-Inc is the sole source of money for our family. Scrum is what I do for a living. Let there be no misunderstanding: money is important.

2001 67

2001 2013 2024 SCRUM 67

Scrum.org

NOVEMBER 24, 2021

Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. From our own quantitative research with 1.200 Scrum Teams , we know that teams are more effective when they are more aware of the needs of their stakeholders. The Scrum Guide seems pretty clear about what Product Owners are accountable for.

2014 205

2014 2008 Technical Review 2019 205

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. Performance Evaluation of non?Markovian

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

And the same process is applied to the Scrum development processes on those projects. . 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 ‒ Steve McConnell.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. México, 1 al 3 de Febrero de 2006.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MARCH 11, 2017

The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp.

2003 46

2003 2014 2015 2011 46