handout for Part 2 on the Agile4Defense GitHub page at: https://git.io/JeaO2 Risk The presence of uncertainty is the simple reason why Agile approaches work better than plan-driven approaches—it is also the adopting an intelligent attitude toward risk. Risk is the chance of a negative impact resulting from uncertainty. We can reduce risk—often at a cost —but there is generally no way to eliminate it.  Almost all under conditions of tremendous uncertainty, your choices will often turn out to be wrong.Agile and plan-driven models have very different ways of dealing with uncertainty. Plan driven approaches, even

will substitute for the outdated project view in my vision for what IT leadership must become. Uncertainty and Risk: Third, underlying all of these changes – all of the problems with plan-drive approaches approaches, all of the advantages of Agile approaches – is a confusion about how to deal with uncertainty and risk. What I call the “contractor-control paradigm” – is really about trying to make risk go away  What is the value of adhering to a plan that was made at the beginning of a project, when uncertainty was greatest? Business value is destroyed only when we substitute extensive planning for execution

idea that we should make a plan and then stick to it is a terrible idea in an environment of uncertainty and change. It has dominated the IT world because it appears to offer predictability, control time through incremental investments.  Managing the EA asset is an art, just as all strategic management is an art. Just as the CMO must sense market opportunities, weigh tactics for communicating with will turn off my sarcasm engine for a moment. Look—it turns out that the future involves lots of uncertainty. No one knows exactly what the benefit of an investment will be—no one even knows approximately

could beget geopolitical leadership – and not vice-versa. This state of affairs brings tremendous uncertainty…yet it leads us back to one of our favorite quotes – Statistically speaking, the world doesn’t AI – top-of-mind for many – generate warranted excitement and trepidation, further fueled by uncertainty over the rapid pace of change and intensifying global competition and saber rattling.​ The pros mobile app ordering, point of sale, kitchen and delivery optimization, menu management, inventory and labor management, and team member tools. - Yum! Press Release, 2/25 Number of Restaurants Yum

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 16 Modules 205 16.1 Namespace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 16.2 Submodules and relative Julia Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 30.5 Memory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 30.6 Working with Arrays you have to import it or use the name qualified with module names. See the section on namespace management. 12.1 Defining Methods Until now, we have, in our examples, defined only functions with a single

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 16 Modules 205 16.1 Namespace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 16.2 Submodules and relative Julia Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 30.5 Memory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 30.6 Working with Arrays you have to import it or use the name qualified with module names. See the section on namespace management. 12.1 Defining Methods Until now, we have, in our examples, defined only functions with a single

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17 Modules 218 17.1 Namespace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 17.2 Submodules and relative Julia Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 31.5 Memory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 31.6 Working with Arrays you have to import it or use the name qualified with module names. See the section on namespace management. 13.1 Defining Methods Until now, we have, in our examples, defined only functions with a single

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17 Modules 218 17.1 Namespace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 17.2 Submodules and relative Julia Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 31.5 Memory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 31.6 Working with Arrays you have to import it or use the name qualified with module names. See the section on namespace management. 13.1 Defining Methods Until now, we have, in our examples, defined only functions with a single

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17 Modules 218 17.1 Namespace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 17.2 Submodules and relative Julia Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 31.5 Memory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 31.6 Working with Arrays you have to import it or use the name qualified with module names. See the section on namespace management. 13.1 Defining Methods Until now, we have, in our examples, defined only functions with a single

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17 Modules 218 17.1 Namespace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 17.2 Submodules and relative Julia Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 31.5 Memory Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 31.6 Working with Arrays inference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 35.4 Memory management and arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 35.5 Execution latency, package