Herding Cats

MAY 10, 2019

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. Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. Elsevier, 2005. 15 July 2005.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. The Rise and Evolution of the Chief Risk Officer: Enterprise Risk Management at Hydro One,” Tom Aabo, John Fraser, and Betty Simkins, Journal of Applied Corporate Finance , Volume 17, Number 3, Summer 2005. Elsevier, 2005.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Leading Agile

MARCH 11, 2020

And in those days, so if this was 2004, 2005, something in that kind of range, in those days, then, you know, for the most part, Agile was still maybe one team of six, or eight, or 10. From the top strategy to the last line of code, how do we bring the right science into the system and design it? – [Mike] Yeah, yeah.

Agile 77

Agile Fractional CTO CTO Hire Influencer 77