Herding Cats

MAY 10, 2019

Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. IEEE Transactions on Software Engineering , Vol. 105, 2003. “A

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Effective Risk Management 2nd Edition, Edmund Conrow, AIAA, 2003. A Taxonomy-based Model for Identifying Risks, Sebastian Maniasi, Paola Veronica Britos, and Ramon Garcia-Mertinez, JIISIC'06 - V Jornadas Iberoamericanas de Ingeniería de Software e Ingeniería del Conocimiento, Memoria Técnica, Proceedings, Puebla, Pue. 105, 2003. “A

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

MAY 7, 2019

So start here to build your academic foundation, that can be put to work to build a foundation of validated experience of making estimates in the presence of uncertainty and protect yourself from fallacious claims that estimates are a waste, not needed, and produce bad resulting in the decision making process for those paying you to produce value.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

FEBRUARY 9, 2018

The "bad management" is itself a symptom of untrained, inexperienced, unskilled decision making processes in the presence of uncertainty. . An Estimate is a value inferred for a population of values based on data collected from a sample of data from that population or generated from a model of the process being estimated.

Underperforming Technical Team 44

Underperforming Technical Team Estimate 2003 Software Review 44

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." . The Design Structure Matrix .

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Herding Cats

JANUARY 23, 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." .

Estimate 37

Estimate Technical Review Underperforming Technical Team Software Review 37