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. requires making estimates)

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 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. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

FEBRUARY 9, 2019

1] "Systems Engineering Strategies for Uncertainty and Complexity," MITRE Corporation, Systems Engineering Guide. [2] 2] "A Guide to Deal with Uncertainties in Software Project Management," International Journal of Computer Science & Information Technology (IJCSIT), Vol. 6, No 5, October 2014. [3]

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

JANUARY 23, 2019

Judgment from experience requires repeatability (experts work best in Complicated or Ordered cynefin domains) The moment you have little-to-no repeatability experts are at best useless, adaptability is a better survival strategy. Rarely are software engineers working on science experiments. Plans are Strategies.

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37