Herding Cats

MARCH 11, 2017

Information about key project cost, performance, and schedule attributes is often uncertain or unknown until late in the program. Pesotskaya, 7 th Central and Eastern European Software Engineering Conference, 2011. “A NASA Risk Management Handbook,” NASA/SP-2011-3422, Version 1.0, November 2011. Eggstaff, Thomas A.

2003 46

2003 2014 2015 2011 46

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. A Risk Management Methodology for Project Risk Dependencies,” Tak Wah Kwan and Hareton K.N., 5, September/October 2011. IEEE Transactions on Software Engineering , Vol. 24, 2010. “A

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. 5, September/October 2011. 3, March 2002. 24, 2010. “A Dorofee, et.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

APRIL 16, 2019

PMI EVM Community of Practice, EVM World , May 16-18 2011. Establishing the Performance Measurement Baseline - The PMB is the time-phased schedule for all the work to be performed, the budgeted cost for this work, and the organizational elements that produce the deliverables for this work, AACE Workshop , April 16, 2011.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42