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. The Heisenberg Uncertainty Principle and Its Application to Software,” P. 8, August 1995.

Estimate 64

Estimate 2006 2005 2013 64

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. Control Variates for Stochastic Network Simulation,” T. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MARCH 11, 2017

Information about key project cost, performance, and schedule attributes is often uncertain or unknown until late in the program. Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects,” Dana Roberson and Mary Anne Herndon, 10 th Annual CMMI Technology Conference And User Group , November 5 – 8, 2012, Denver, CO.

2003 46

2003 2014 2015 2011 46

Herding Cats

MARCH 11, 2018

If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Software engineering economics." IEEE Transactions of Software Engineering, 1 (1984): 4-21.

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Teamweek

NOVEMBER 9, 2022

It also features a helpful color-coded system so you can see what aspects of the project are on track or need investigation at the next team meeting: 5. Workflow management software. Your workflow management software is like your mission control. Example: Microsoft Project. Example: Traction. Example: Backlog.

Software Review 52

Software Review Software Technical Review Construction 52

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. 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.

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. Management of Novel Projects Under Conditions of High Uncertainty,” A.

Risk Management 35

Risk Management Risk Technical Review 2002 35