2013 Agile Software Software Engineering 
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.
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 ). Money was not what drove my wife and I when I gave up my position as software engineer and aspiring project manager in favor of running a bookshop (1996). Let there be no misunderstanding: money is important.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
NOVEMBER 24, 2021
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Van Waardenburg & Van Vliet (2013) offer a case study in a large organization and conclude that “The Project Manager focuses on the ’how’ of a project, the Product Owner focuses on the ’what’”. When agile meets the enterprise.
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. 5, September/October 2011.
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. This is the motivation for short work intervals found in agile development. . Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391.
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.
Herding Cats
OCTOBER 24, 2018
But before going further, let's establish the definitions we need to understand and apply Root Cause Analysis needed to discover the corrective and preventive actions to increase the probability of project success - especially Software Project Success. What factors lead to software project failure?” All for the want of a nail.
Expert insights. Personalized for you.
204 
Let's personalize your content