System: Team WikiSpeed Process
Strategic Values/Objectives
• Rapid Rate of Development
• Low Training Cost
• Open Source Development
• Modular Product Architectures
Descriptive Statement
The WikiSpeed development process enables fast product development
and the ability to rapidly make design changes and implement new
technologies with a modular product design. New team members can be
integrated with little if any direct training. Minimal management is and no
long term financial forecasting is required.
Response Situation Analysis for System: Team WikiSpeed Process
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
Change Domain
Proactive
Creation
(and
Elimination)
Improvement
Migration
Modification
(Add/Sub
Capability)
Correction
Reactive
Variation
Change/Response Issue
What must the system be creating or eliminating in the course of its operational activity?
• Facilitates creation of an agile product (didn’t get this section correct, too general)
• Eliminates wasted resources
What performance characteristics will the system be expected to improve during operational life cycle?
• Development process efficiency (didn’t get this correction correct, too general)
• Product performance
What major events coming down the road will require a change in the system infrastructure?
• Lack of volunteers
• Change in government regulations
What modifications in resources-employed might need made as the system is used?
• Add specialized sub-teams
• Add manufacturing capacity for higher volumes
What can go wrong that will need an automatic systemic detection and response?
• An act of God (flood/tornado/etc)
• Loss of funding
What process variables will range across what values and need accommodation?
• Number of available volunteers and workers
• Number of available sub-system teams
Expansion
(and
Contraction
of Capacity)
What are “quantity-based” elastic-capacity range needs on resources/output/activity/other?
• Too much open source information to process
• Not enough funds and volunteers
• No manufacturing capability or expertise
Reconfiguration
What types of resource relationship configurations will need changed during operation?
• Customer requirements
• Loss of key volunteer or access to key resource
RS Analysis of Team WikiSpeed
Team: Aero Outcasts
Kevin Johnson, Jamey Mulloy, Pete Opper
ES678 Agile Systems and Enterprises
System:Team WikiSpeed
Sample Graphics for your modification into your system needs
Resources
Integrity
Management
Volunteers
Team Leads
Tests
Standup Meetings
eee
fff
Team Leaders
Team Leaders & Volunteers
Tests
Kan Ban / Burn Down Schedule
Team Leaders
Resource mix evolution
Resource readiness
Situational awareness
Activity assembly
Infrastructure evolution
Active
Infrastructure
Passive
Config 1
Sockets
Signals
Security
Safety
Service
Rules/Standards
Peer to Peer Interaction
Stand-up meetings/Social Networks
Competency
Simplicity
ConOps
Config 2
Config n
RRS Principles for System: Team WikiSpeed
(Think: Plug-and-Play, Drag-and-drop)
Evolving Infrastructure ConOps and module interface and
Encapsulated Modules Modules are encapsulated independent units
interaction standards that evolve slowly.
loosely coupled through the passive infrastructure.
Facilitated Interfacing (Pluggable) Modules
Redundancy and Diversity Duplicate modules provide fail-soft &
& infrastructure have features facilitating easy module insertion/removal.
Pairing Training method allows fast reallocation of
volunteer resources
Tool/Consumable Organization
Scalable
Minimize Training
Reusable
Sub-system Teams
capacity options; diversity provides functional options.
Sprints
Multi-cultural Viewpoints
Facilitated Reuse Modules are reusable and/or replicable; with
Elastic Capacity Module populations & functional capacity may be
supporting facilitation for finding and employing appropriate modules.
increased and decreased widely within the existing infrastructure.
Pairing Training method allows fast reallocation of
volunteer resources
Open Source Collaboration
Paring Training Method
Reconfigurable
Peer-Peer Interaction Modules communicate directly on a peer-to-peer
Distributed Control & Information Decisions made at point of
relationship; parallel rather than sequential relationships are favored.
maximum knowledge; information accessible globally but kept locally.
Standup meetings and social network communication
Teams and Team Leads
Deferred Commitment Module relationships are transient when possible;
Self-Organization Module relationships are self-determined; and
decisions & fixed bindings are postponed until necessary.
component interaction is self-adjusting or negotiated.
Perform empirical testing when funding is available
Perform tasks when team resources are available