Scrum.org

OCTOBER 19, 2022

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 214

Agile 2010 2013 2008 214

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. Turof, IOP Conference Series: Materials Science and Engineering , 400, 2018. “A

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Leading Answers

JUNE 9, 2019

   “ Continuous Digital: An agile alternative to projects for digital business ”. Allan Kelly, Software Strategy Ltd.; October 2018. Allan’s book was the first I read about switching to continuous product development. Evan Leybourn, Shane Hastie, lulu.com; July 2018.

Technical Review 113

Technical Review Software Review Lean 2018 113

Leading Agile

JUNE 7, 2018

The core principle of engineering, found on signs in labs the world over, is: “Don’t do anything stupid on purpose.” ” This principle applies equally to software development. Now we’re going to do software development work. cd playservice mkdir app. mkdir spec. rake integration.

Software Review 84

Software Review Technical Review 2018 Software Developers 84

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. & Zein, S.,

Estimate 40

Estimate Software Review Software 2012 40

Leading Agile

AUGUST 20, 2018

They asked a software developer what it would take, and he estimated something like 20,000 pounds over several months. Building software. Circa 2018 this might seem rather obvious, but one aspect of automating a software delivery pipeline is to automate the build process for the application. It is not true.

Software Review 78

Software Review Software Technical Review Development Team Review 78