Rebel’s Guide to PM

APRIL 12, 2023

After $170m spent on a project to upgrade its computer system, the FBI project crumbled because the requirements were ill-defined from the beginning and the software didn’t function the way the agency had hoped. For example, in June 2010 Chrysler merged with Fiat. The merger was not a successful one.

Planning 414

Planning Underperforming Technical Team Technical Review 2010 414

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. 255, April 2010. 24, 2010. “A Software Engineering Institute, January 1996.

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

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. 24, 2010. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35