Scrum.org

OCTOBER 19, 2022

Is it really that important that they are autonomous, able to release frequently, interact closely with stakeholders and spend all that time on continuous improvement? However, the sheer effort involved is so gargantuan that this is close to impossible. SCRUM and productivity in software projects: a systematic literature review.

Agile 200

Agile 2010 2013 2008 200

Herding Cats

MARCH 11, 2017

Accuracy - how close is the estimate to the actual value? So in the end, if we are to make a decision in the presence of uncertainty, we MUST make estimates to develop a reliable shipping date while producing an accurate and precise estimate of the cost, schedule, and technical performance of the product shipped on that date.

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. Software Engineering Institute, January 1996. 4, February 24, 2015.

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

Scrum.org

JANUARY 25, 2021

The decade-long window of opportunity in outsourcing disruptive innovation is closing. Here’s an example: InfoQ — a community news site facilitating the spread of knowledge and innovation in professional software development — has a rigorous editorial process and focuses on delivering quality content to its audience.

SCRUM 186

SCRUM Technical Review Engineering Lean 186

Herding Cats

MARCH 4, 2017

Software development project schedule estimation has long been a difficult problem. Instead, it suggests the Cone of Uncertainty is not the proper model for software estimating, with no evidence other than anecdotal examples from observed projects. This approach ignores the core principle of closed loop control.

2010 28

2010 2007 Estimate Aerospace 28

Herding Cats

APRIL 4, 2019

It just closed the loop faster. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Proofing Your Project , 3rd Edition, Tom Kendrick, AMACOM, March 25, 2015. This is good, but it doesn't reduce risk.

Risk Management 43

Risk Management Risk 2003 2011 43