1. Team Name: Team 1 Agile Engineering Process
Mike Morell, Zac Fisher, Tony Busby, Brandon Miller

2. DESCRIPTIVE STATEMENT
A development team that created a modular design yielding a quickly modifiable product using continuous improvement, lean principles, and the scrum process. The end goal was to compress the entire development cycle into short sprints, without compromising quality, resulting in a highly productive work environment.
STRATEGIC VALUES / OBJECTIVES
Modular
Efficient
Team oriented
Collaborative
Rapid evolution

3. RS Analysis for AEP (Proactive)
Creation (and elimination)
Specialized teams
Eliminate unnecessary processes
Improvement
Short, regular productive meetings
Accurate ETC
Increased team communication
Migration
Anticipating new regulations
Employee/team expertise
Modification (Add/Sub Capability)
Scalability to adapt to larger projects
Process changes required due to applicability to the design project

4. RS Analysis for AEP (Reactive)
Correction
Requirements changes
Module incompatibility
Test (verification / validation) outcomes
Variation
Manpower demand
Skill level
Expansion (and Contraction) of Capacity
Schedule adjustments as needed based on burn-down chart
Real estate and resources
Reconfiguration
Process priority change

5. WIKISPEED Agile Architecture Pattern (AAP)
Resources
Integrity
Management
Scrum Masters
Scrum team
Product Owners
Progressive (stakeholder)
Product Backlog
Resource mix evolution
Joe Justice
Resource readiness
Scrum Master, Scrum team
Situational awareness
Everybody
Activity assembly
Self Organizing
Infrastructure evolution
Joe Justice, Progressive
Active
Infrastructure
Passive
Standup Meeting
Iteration n
Sprint Retrospective
Sockets
Signals
Security
Safety
Service
Peer-Peer Interaction
Daily Standup Meeting
Trustworthy Transparency
Collaborative Review
Process Rules & testing
Rules/Standards
Retrospective Change

6. RRS Principles for System: WIKISPEED
(Think: Plug-and-Play, Drag-and-drop)
Reconfigurable
Scalable
Reusable
Encapsulated Modules Modules are encapsulated independent units loosely coupled through the passive infrastructure.
-Scrum team -Product backlog
-Sprints
-Product owner
-Scrum master
Evolving Infrastructure ConOps and module interface and interaction standards that evolve slowly.
-Standup meetings
-Testing
Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal.
-Team-to-team interaction
-Scrum board stories
Redundancy and Diversity Duplicate modules provide fail-soft & capacity options; diversity provides functional options.
-Multi-capable teams
-Pairing
Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules.
-Team members and teams
-Processes
Elastic Capacity Module populations & functional capacity may be increased and decreased widely within the existing infrastructure.
-Deadlines
-Scope of tasks
-System complexity
Peer-Peer Interaction Modules communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored.
-Swarming (working collaboratively to solve a problem)
-Team Co-location
Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally.
-Team networking
-Safety equipment room
Deferred Commitment Module relationships are transient when possible; decisions & fixed bindings are postponed until necessary.
-Iterative frame design
Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated.
-Team morale
-Volunteers, deep nerds