Team: Juan Pablo Pods System:Team WikiSpeed Strategic Values/Objectives High Fuel Efficiency (Green Design) 5 Star Crash Safety Customizable design Uses New-to-Market Technologies Practical design and features (Family Friendly) Affordable Low maintenance costs and time Easily upgradable Descriptive Statement Team Wikispeed applies lean, agile, and scrum strategies to produce a street legal car capable of achieving 100 miles per gallon. Team Members: Cody Clanton, Brian Claussen, Josh Cory, Chris Leroux

RS Analysis for System Correction Variation Reconfigu- ration Expansion (and Contraction of Capacity) Migration Improvement Modification (Add/Sub Capability) Creation (and Elimination) Proactive Reactive Change Domain Response Issues What types of resource relationship configurations will need changed during operation? Storage/Passenger accommodations Module Replacement (Engine, Bumpers, Body) Tire/Suspension Replacement based on driving needs What performance characteristics will the system be expected to improve during operational life cycle? Fuel efficiency Handling What must the system be creating or eliminating in the course of its operational activity? An affordable, efficient transportation system. What major events coming down the road will require a change in the system infrastructure? Improved Technology New Safety Testing Requirements Autonomous Driving Aids What modifications in resources-employed might need made as the system is used? Tire/Suspension Upgrades Amenity replacement (A/C) (Overlaps with Reconfiguration) What can go wrong that will need an automatic systemic detection and response? Part Failure Engine Fire Battery Explosion What process variables will range across what values and need accommodation? Differences in Carbon Fiber quality Road Quality What are “quantity-based” elastic-capacity needs on resources/output/activity/other? Total Passengers Software Memory Fuel Tank Size

Juan Pablo Pods: WikiSpeed AEP Work Units Marketing Methodologies Communication Methods Team Morale eeefff Infrastructure evolution System assembly Module mix evolution Module inventory readiness Infrastructure Continental UniversalCommon Locality Components/Modules Rules/Standards Integrity Management Active Passive Sockets Signals Security Safety Service Project Lead Leadership Team SCRUM Master SME’s

Reconfigurable Scalable Reusable Encapsulated Modules Work Units Team Morale Communication Methods Marketing Methodologies Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal. Daily SCRUM styled meetings Open Tool Storage (Clear Containers with Labels Logical Layout (Drill bits next to drill press) Safety Shelf (One location for all safety materials) Google Docs (Used for method reviews) Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules. Google Docs (Used for Document accessibility) Peer-Peer Interaction Swarm style problem solving Pairing Deferred Commitment Standardized, Adaptable Interface Standards Evolving Infrastructure Standards Communication Protocols Work Unit Composition Facilities (Location) Knowledge Management Redundancy and Diversity Decentralized Knowledge Base (Doesn’t rely on Group-Think, no one person holds all knowledge) SME Variety Work Unit Pairing Elastic Capacity Common Access Communication Tools Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Google Doc (Used for document storage) Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated. Non-assigned, interest driven team creation methods RRS Principles for System: TEAM Wikispeed AEP