Leading Agile

MARCH 11, 2020

And what was fascinating about, and really sort of formed, solidified some of my way of thinking about these things, in some cases, those constraints, as we would identify them, they would be identified as explicit contracts between systems. – I would say 2009-ish, early 2009 maybe. – [Brian] 2009, 2010?

Agile 104

Agile Fractional CTO CTO Hire Influencer 104

Herding Cats

MAY 10, 2019

5887, 2009. 532, August 2009. Dorofee, CMU/SEI-2009-TR-007, April 2009. Brian Derfer, CTO. Introducing the Agile Risk Management (ARM) Framework,” Brian Derfer, CTO, Agile Six Applications, Inc., Risk a Feelings,” George F. Loewenstein, Elke U. Weber, Christopher K. 30, 1998. “A Alberts and Audrey J.

Risk Management 38

Risk Management Risk Technical Review 2004 38

Herding Cats

MAY 11, 2019

5887, 2009. 532, August 2009. Dorofee, CMU/SEI-2009-TR-007, April 2009. Brian Derfer, CTO. Introducing the Agile Risk Management (ARM) Framework,” Brian Derfer, CTO, Agile Six Applications, Inc., Risk a Feelings,” George F. Loewenstein, Elke U. Weber, Christopher K. 30, 1998. “A Alberts and Audrey J.

Risk Management 35

Risk Management Risk Technical Review 2004 35