ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard PBM Ag Innovations ES 678 Agile Systems Pat Bullock Brian Dodds Mike Leonard

Team: PBM Ag Innovations System: Team WikiSpeed Descriptive Statement Produce a road-legal (NTSA) 100mpg vehicle through the use of an iterative development, modular design approach and agile management to design and production Strategic Values/Objectives Produces modular design Minimizes development time Create reconfigurable designs Agile management Prize winning designs (Win 10M prize purse)

Response Situation Analysis for System: Team Wiki Speed 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 be creating or eliminating during its operational activity? Process knowledge Vehicle Marketable subassemblies Improvement What performance characteristics will the system be expected to improve during operational life cycle? Safety Fuel economy Performance (handling, top speed, acceleration) Migration What major events coming down the road will require a change in the system infrastructure? Driveline/propulsion Regulation Modification (Add/Sub Capability) What modifications in resources-employed might need made as the system is used? Autonomy/intelligent driving Battery technology Drive side Correction What can go wrong that will need an automatic systemic detection and response? Safety Software irregularities Regulations Variation What system/process variables will range across what values and need accommodation? Power and acceleration Suspension and handling Number of cupholders Expansion (and Contraction of Capacity) What are “quantity-based” elastic-capacity range needs on resources/output/activity/other? Manufacturing constraints (producibility) Market demands Reconfigu-ration What types of resource relationship configurations will need changed during operation? Vehicle type/capacity (e.g. truck bed size, passenger count)? Tooling Human resource availability and capability

RRS Principles for System: Team Wikispeed Car (Think: Plug-and-Play, Drag-and-drop) Reconfigurable Scalable Reusable Encapsulated Resources Resources are encapsulated independent units loosely coupled through the passive infrastructure. Distributed design teams Modular components Evolving Infrastructure ConOps and resource interface and interaction standards that evolve slowly. Volunteer labor Incremental improvements Facilitated Interfacing (Pluggable) Resources & infrastructure have features facilitating easy resource insertion/removal. Virtual environment (global) Highly skilled volunteers Redundancy and Diversity Duplicate resources provide fail-soft & capacity options; diversity provides functional options. Pairing and swarming Global resources Facilitated Reuse Resources are reusable and/or replicable; with supporting facilitation for finding and employing appropriate resources. Modular design for each subcomponent Elastic Capacity Resource populations & functional capacity may be increased and decreased widely within existing infrastructure. Team members can come and go as they need to Peer-Peer Interaction Resources communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Bullpen working environment and global virtual connection Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Teams managed own tasks Global interconnectivity Deferred Commitment Resource relationships are transient when possible; decisions & fixed bindings are postponed until necessary. Design to test requirement and only change to meet that Trial configuration Self-Organization Resource relationships are self-determined; and resource interaction is self-adjusting or negotiated. Weekly local scrum meetings

System: Team Wikispeed Car Resources Integrity Management Materials Scrum Master Team Fab/Assy Tooling Situational awareness Resource mix evolution Resource readiness Activity assembly Infrastructure evolution Scrum Master Teams Everyone Scrum Master “Awesome” Joe Justice Active Infrastructure Passive Team Config 2 Config n Sockets Signals Security Safety Service Information exchange Communications Trust and engagement Iterative review/team awareness Procedures and team norms Rules/Standards