Herding Cats

OCTOBER 24, 2018

This first post is a follow-on from the posts Root Cause of Project Failure , Root Cause Analysis , Discovering the Root Cause - The 5 Whys , T urning Editorials into Root Cause Analysis , Observation Issues and Root Cause Analysis , Without a Root Cause Analysis, No Suggested Fix Can Be Effective. References .

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

MARCH 17, 2019

Nine Best Practices of Project Management , Software Program Managers Network (SPMN). Project Governance. Establishing the Performance Measurement Baseline (PMB) , AACE Workshop, Denver, Colorado, April 16, 2011. Establishing the Performance Measurement Baseline , AACE Workshop , April 16, 2011. Project Breathalyzer.

2003 54

2003 2011 2008 Performance Measurement 54

Agilemania

DECEMBER 6, 2021

Be it monitoring and control, collaboration, stakeholders onboarding, change management, and governance methods, the problems only keep increasing. It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. Kanban is a preferred framework for implementing Agile and DevOps software development.

Lean 98

Lean 2011 Cadence Innovation 98

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. The Effectiveness of Risk Management: An Analysis of Project Risk Planning Across Industries and Countries,” Ofer Zwikael and Mark Ahn, Risk Analysis , Vol. Finucane, Ellen Peters, and Donald MacGregor, Risk Analysis , Vol.24, 24, 2010. “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

Herding Cats

MARCH 11, 2017

“Quantifying Uncertainty in Early Lifecycle Cost Estimation (QUELCE),” Robert Ferguson, Dennis Goldenson, James McCurley, Robert Stoddard, David Zubrow, and Debra Anderson, Technical Report, CMU/SEI-2011-TR-026 ESC-TR-2011-026. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

Herding Cats

OCTOBER 5, 2018

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 ? A Probabilistic Method for Predicting Software Code Growth," Michael Ross, Journal of Cost Analysis and Parametrics 4:127-147, 2011. "10

2012 48

2012 2007 2011 2010 48