Agile Systems and EnterprisesResponse Ability Tool Templates

Team: __________________________

System:__________________________

Strategic Values/Objectives• ?• ?• ?• ?• ?• ?

Descriptive Statement?

Strategic Values/ObjectivesFunctional Activity

Strategic Activity ConOps Web

System: __________________________

Change the lines and bubbles,this is not a fill-in-the-blank model

??

?

?

?

?

?

?

?

?

?

?

System: __________________________

?

Strategic Values/ObjectivesFunctional Activity

Strategic Activity ConOps Web

Pro

ac

tiv

eR

ea

cti

ve

General Issues

•

•

System: __________________________

Response Situation Analysis (RSA)

Correction

Variation

Reconfigu-ration

Expansion(and

Contractionof Capacity)

Migration

Improvement

Modification(Add/Sub

Capability)

Creation(and

Elimination)

Pro

ac

tiv

eR

ea

cti

ve

Change Domain

What performance characteristics will the system be expected to improve during operational life cycle?•

What must the system be creating or eliminating in the course of its operational activity?•

What major events coming down the road will require a change in the system infrastructure?•

What modifications in resources-employed might need made as the system is used?•

What can go wrong that will need an automatic systemic detection and response?•

What process variables will range across what values and need accommodation?•

What are “quantity-based” elastic-capacity range needs on resources/output/activity/other?•

What types of resource relationship configurations will need changed during operation?•

Change/Response Issue

RS Analysis for System ____________________

Correction

Variation

Reconfigu-ration

Expansion(and

Contractionof Capacity)

Migration

Improvement

Modification(Add/Sub

Capability)

Creation(and

Elimination)

Pro

ac

tiv

eR

ea

cti

ve

Change Domain Response Issues

What types of resource relationship configurations will need changed during operation?• ?• ?• ?

What performance characteristics will the system be expected to improve during operational life cycle?• ?• ?• ?

What must the system be creating or eliminating in the course of its operational activity?• ?• ? Use as many bullet points as appropriate• ?

What major events coming down the road will require a change in the system infrastructure?• ?• ?• ? What modifications in resources-employed might need made as the system is used?• ?• ?• ?

What can go wrong that will need an automatic systemic detection and response?• ?• ?• ?

What process variables will range across what values and need accommodation?• ?• ?• ? What are “quantity-based” elastic-capacity range needs on resources/output/activity/other?• ?• ?• ?

with [t,c,p,s] metric-priorities for each issue, t = time of change, c = cost of change, p = predictability of change, s = scope of change

Correction

Variation

Reconfigu-ration

Expansion(and

Contractionof Capacity)

Migration

Improvement

Modification(Add/Sub

Capability)

Creation(and

Elimination)

Pro

ac

tiv

eR

ea

cti

ve

Change Domain

What performance characteristics will the system be expected to improve during operational life cycle?• ?• ?• ?

What must the system be creating or eliminating in the course of its operational activity?• ?• ? Use as many bullet points as appropriate• ?

What major events coming down the road will require a change in the system infrastructure?• ?• ?• ?

What modifications in resources-employed might need made as the system is used?• ?• ?• ?

What can go wrong that will need an automatic systemic detection and response?• ?• ?• ?

What types of resource relationship configurations will need changed during operation?• ?• ?• ?

What are “quantity-based” elastic-capacity range needs on resources/output/activity/other?• ?• ?• ?

What process variables will range across what values and need accommodation?• ?• ?• ?

Change/Response Issue

Response Situation Analysis for System: __________________________

System: ________________________

Encapsulated Modules• ?

Evolving Infrastructure Standards• ?

Sca

lab

leR

eus

able

(Think … Drag-and-Drop / Plug-and-Play)

Reconfigurable

Sca

lab

leR

eusab

le

Encapsulated Modules Modules are encapsulated independent units loosely coupled through the passive infrastructure.?

Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal.?

Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules.?

Peer-Peer Interaction Modules communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. ?

Deferred Commitment Module relationships are transient when possible; decisions & fixed bindings are postponed until necessary.?

Evolving Infrastructure Standards Module interface and interaction standards and rules that evolve slowly.?

Redundancy and Diversity Duplicate modules provide fail-soft & capacity options; diversity provides functional options.?

Elastic Capacity Module populations & functional capacity may be increased and decreased widely within the existing infrastructure.?

Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally.?

Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated. ?

(Think: Plug-and-Play, Drag-and-drop)RRS Principles for System: ________________________

Enc

apsu

late

d M

odul

es

Fac

ilita

ted

Inte

rfac

ing

Fac

ilita

ted

Re-

Use

Pee

r-P

eer

Inte

ract

ion

Def

erre

d C

omm

itmen

t

Dis

trib

uted

Con

trol

& In

fo

Sel

f Org

aniz

ing

Ela

stic

Cap

acity

Uni

t Red

unda

ncy

Evo

lvin

g S

tand

ards

Issues Principle-Based Activities and Issues Served

Activities

R

ea

cti

ve

Pro

ac

tiv

e

Capturing Hidden Tacit Knowledge 3567 35 356 57 3 37 6 3 3 37

Creating Student Interest and Value 124 1 1 1 12 124 124 1 1

Improving Knowledge Accuracy 3467 6 34 37 6 34 34 7

Improving Knowledge Effectiveness 12345 345 245 45 1 12 5 2

Migrating the Knowledge Focus 247 27 4 2 4 7 247 4 47

Accommodating Different Student Types (all) 25 6 347 2 12345 1 17 2

Injecting Fresh Outside Knowledge 26 26 26 2 6 2

Finding and Fixing Incorrect Knowledge 367 7 7 3 3 6 3 3 7

Excising Poor Value Knowledge 2357 7 7 3 3 2 23 35 257

Allowing Flexible Student Schedules 34 34 34 34

Accommodating Any Size Group 2345 2345 234 2 25 34 234

Reinterpret Rules for New Applications 23457 27 5 2 357 23457

Establish Personal Values 1

Analyze External Case for Ideas 2

Analyze Local Case for Principles 3

Design a Business Practice 4

Package as Metaphor Models 5

Rotate Student / Mentor Roles 6

Review and Select for Quality 7

RRS PrinciplesCore Competency Development

Excel template version (a different template file) may be easier to use

Sel

f Con

tain

ed U

nits

Plu

g C

ompa

tibili

ty

Fac

ilita

ted

Re-

Use

Pee

r-P

eer

Inte

ract

ion

Def

erre

d C

omm

itmen

t

Dis

trib

uted

Con

trol

& In

fo

Sel

f Org

aniz

ing

Fle

xibl

e C

apac

ity

Uni

t Red

unda

ncy

Evo

lvin

g S

tand

ards

Issues Principle-Based Activities and Issues Served

Activities

R

ea

cti

ve

Pro

ac

tiv

e

??

??

??

??

??

??

??

??

??

??

??

??

?? 1

?? 2

?? 3

?? 4

?? 5

?? 6

?? 7

RRS Principles<your system>

Excel template version(a different template file)

may be easier to use

Reality Factors

Organizational Behavior – Survival rules rule, nobody's in absolute control...• ?

Human (Including Customer) Behavior – Human error, whimsy, expediency, arrogance...• ?

Technology Pace – Accelerating technology and security-vulnerability introductions, sparse testing...• ?

System Complexity – Incomprehensible, highly networked, unintended consequences, emergence...• ?

Globalization – Partners with different ethics, values, infrastructures, cultural assumptions...• ?

Other?• ?

Agile Customers/Competitors/Adversaries – Distributed, collaborative, self organizing, proactive, impatient, innovative...• ?

Partially-Agile Enterprise Faddish Practices – Outsourcing, web services, transparency, COTS policies/affects...• x

System ____________________________

System _______________________Who is Accountable for Keeping the System Effective

(as part of their job description/responsibility/evaluation)

Module Evolution (who decides/specifies/adds which new types of modules, excises old useless modules) :

• ?• ?• ?

Module Readiness (who maintains serviceability/readiness and quantity on hand of which modules):

• ?• ?• ?

System Assembly/Reconfiguration (who assembles/configures/reconfigures the systems): • ?• ?

Infrastructure Evolution (who reviews and modifies the various framework elements):

• ?• ?• ?• ?

Your System

aaa cccbbb ddd eee fff

Infrastructure evolution

System assembly

Module mix evolution

Module inventory readiness

Infrastructure

Config 2 Config nConfig 1

Components/Modules

Rules/Standards

IntegrityManagement

Active

Passive

Sample Graphics for your modification into your system needs

SocketsSignalsSecuritySafetyService

Do not use this template – refer to file: TemplatesAgileArchitecturePatterns.pptx for many examples

who

who

who

who