Herding Cats

MAY 10, 2019

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. Elsevier, 2005. 15 July 2005. 9, September 2005, pp.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Let's start with a critical understanding of the purpose of managing risk on software development projects. Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. Elsevier, 2005. 15 July 2005. 9, September 2005, pp.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

APRIL 16, 2019

, Cost and schedule growth for federal programs is created by unrealistic technical performance expectations, unrealistic cost and schedule estimates, inadequate risk assessments, unanticipated technical issues, and poorly performed and ineffective risk management, all contributing to program technical and programmatic shortfalls.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MAY 7, 2019

Flint, School of Management, Working Paper Series, September 2005.”. Estimating Probable System Cost,” Stephen A. Why Monte Carlo Simulations of Project Network can Mislead,” Terry Williams, Project Management Journal 35(3), pp. Evaluating Project Decisions,” INTAVER Institute.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

The same process for estimating is applied to multi-billion dollar projects we work. And the same process is applied to the Scrum development processes on those projects. . An Analysis of XP, TDD, Pair Programming, and Scrum (Using Real Options),” Dr. David Rico, [link] davidfrico.com/rico08b.pdf. 400-407, 2009.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

FEBRUARY 9, 2019

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." . 4] "Explicating the dynamics of project capabilities," Andrew Davies and Tim Brady, .

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42