Team: __Remote Site_____________ System: ___TWS__________________ Descriptive Statement Develop a process that allows the team to deliver a product meeting customer requirements on a compressed schedule at minimum cost using fewest number of resources. The process must be able to respond to changes quickly and use a Test Driven Development approach. Also utilize Scrum techniques to facilitate communications, remove barriers, and coordinate workflows. Adapt Software Development techniques to other domains. Strategic Values/Objectives Response capability Modularity Highest Safety rating Esthetics exceed expectations Distributed collaborative team Cost effective

Response Situation Analysis for System: __TWS_____________________ with [t,c,p,s] metric-priorities for each issue, t = time of response, c = cost of response, p = predictability of response, s = scope of response Domain Response Issue Proactive Reactive Creation (and Elimination) What artifacts/data/knowledge must the system/process be creating or eliminating during operational activity? Scrum artifacts (board, sprints, tasks, user stories, backlog, etc. Test designs Owners manual Improvement What process/system performance characteristics will be expected to improve during its operational life cycle? Time estimation Implementation / fabrication techniques Team building & communication Migration What major events coming down the road will require a change in the process/system infrastructure? Embracing next generation communication & collaboration tools Licensing to other industries Modification (Add/Sub Capability) What modifications to employable resources might need made as the process/system is used? Different and / or more people Different and / or more tools Correction What will impair/obstruct process/system agility that will need an automatic systemic detection and response? Lack of knowledge Impaired communications (distributed teams) Resource availability Variation What process/system variables will range across what values and need accommodation? Resource skill and knowledge variation (unskilled – ignorant to skilled – knowledgable) ? Expansion (and Contraction of Capacity) What are “quantity-based” elastic-capacity range needs on resources/output/activity/other? Team size ? Reconfigu-ration What types of resource relationship configurations will need changed during operation? ?

RRS Principles for System: __TWS Agile Engineering__ (Think: Plug-and-Play, Drag-and-drop) Reconfigurable Scalable Reusable Encapsulated Resources Resources are encapsulated independent units loosely coupled through the passive infrastructure. Local scrum teams - Vendors Domain experts - Team members Evolving Infrastructure Key elements of the infrastructure likely to evolve and need to be evolvable. Dropbox, YouTube, Google Docs Sprint and Retrospectives Facilitated Interfacing (Pluggable) Resources & infrastructure have features facilitating easy resource insertion/removal. Pairing and Swarming Defined Conventions Redundancy and Diversity Duplicate resources provide fail-soft & capacity options; diversity provides functional options. Revolving Pair Training (cross training) Variable Product Owners Facilitated Reuse Resources are reusable and/or replicable; with supporting facilitation for finding and employing appropriate resources. Globally available knowledge (docs, data, etc) Cross Training Elastic Capacity Resource populations & functional capacity may be increased and decreased widely within existing infrastructure. Fluid Team Size Expertise Purchasing Web Based Documentation Peer-Peer Interaction Resources communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Daily Standups Sprint Meetings Pairing and Swarming Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Web based sharing Distributed Scrum teams Deferred Commitment Resource relationships are transient when possible; decisions & fixed bindings are postponed until necessary. Test Driven Development Technical Debt Management Self-Organization Resource relationships are self-determined; and resource interaction is self-adjusting or negotiated. Swarming Self-selected tasking Unconstrained team building

System ____TWS Agile Engineering____ Resources Integrity Management Scrum Masters Team Members Scrum Teams Experts Vendors Situational awareness Resource mix evolution Resource readiness Activity assembly Infrastructure evolution Scrum Teams, Product Owner Scrum Master All Product Owner Members, Experts, Vendors Active Infrastructure Passive Daily Standup Swarm Sprint Planning Mtg Sockets Signals Security Safety Service Web Interfaces, face-to-face CAD drwgs, videos, guides Open Resources Training, Scrum Rooms, Gov Oversight Process Evolution, cross training Rules/Standards