Herding Cats

MARCH 11, 2017

Information about key project cost, performance, and schedule attributes is often uncertain or unknown until late in the program. in Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. in Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. And we all know. Papers on Risk Management.

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. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. 79, 2008. “`,” Stephen Ward and Chris Chapman , International Journal of Project Management , 21, pp. Making,” T.

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. Effective Risk Management 2nd Edition, Edmund Conrow, AIAA, 2003.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MAY 7, 2019

The contribution of mathematical modelling to the practice of project management,” Terry Williams, IMA Journal of Management Mathematics, Volume 14, Issue 1, Jan. Estimating Models of Program Management,” Keith Womer and Jeff Camm, Final Technical Reports, N00014-00-1-0280, University of Mississippi, 2003. October 1, 2003. “A

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

Story Point Estimating,” Richard Carlson, ALEA, Agile and Lean Associates, 2013. Project Estimation in the Norwegian Software Industry – A Summary,” Kjetil Moløkken, Magne Jørgensen, Sinan S. IT Project Estimation: A Practical Guide to Costing Software , Paul Coombs, Cambridge University Press, 2003. Chemuturi, J.

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." . It's also a code word for bad project management.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42