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. Elsevier, 2005.

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. Elsevier, 2005.

Risk Management 35

Risk Management Risk Technical Review 2002 35

The IIL Blog

JANUARY 24, 2024

Most of these roles were based on aspects of IT operation, such as mainframe operation and maintenance, which later evolved into software development and commercialisation. As governments and organisations began to utilise IT to run their organisations, the concepts of ‘services’ began to evolve.

2001 78

2001 2007 2024 Information Technology 78

Herding Cats

MAY 7, 2019

Flint, School of Management, Working Paper Series, September 2005.”. Eva Regnier, DRMI Newsletter, Defense Resources Management Institute, Naval Postgraduate School, Issue 12, April 8, 2005. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. Estimating Probable System Cost,” Stephen A.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

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 ‒ Steve McConnell. Software quality measurement,” Magne Jørgensen, Advances in Engineering Software 30 (1999) 907–912.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

FEBRUARY 9, 2019

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . 6, No 5, October 2014. [3]

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42