WikiSpeed Work Team: Car Riders Team members: Dmitry Retunski Charles Wyatt Todd Embree

Team: Agile System-Engineering Process: ________Team Wikispeed______ Descriptive Statement Team Wikispeed is a highly motivated international team of volunteers assembled to compete for the 100MPG Progessive Insurance Automotive X Prize. Team Wikispeed creates team subsystems that create separate modules, which can be easily interchanged or improved according to test requirements. Strategic Values/Objectives Use Agile techniques Cross cultural collaborative environment Quickly adapt to new requirements Quickly integrate new people into the team Design to test

Response Situation Analysis for System: __________________________ 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 Change/Response Issue Proactive Reactive Creation (and Elimination) What must the system be creating or eliminating in the course of its operational activity? Helps teams respond to unpredictability through incremental, iterative, work cadences and empirical feedback Provides opportunities to assess the direction of a project throughout the development lifecycle Improvement What performance characteristics will the system be expected to improve during operational life cycle? Higher team efficiency which shortens the product delivery time Better communication within the team leading to better understanding of member’s needs Migration What major events coming down the road will require a change in the system infrastructure? Learn to work with larger groups of people Adapt to different cultural norms Competitors adopt the same AEP Modification (Add/Sub Capability) What modifications in resources-employed might need made as the system is used? Additional people Involve more professionals Create better communications Correction What can go wrong that will need an automatic systemic detection and response? Technical debt due to speed of sprint deliverables Variation What process variables will range across what values and need accommodation? ? Expansion (and Contraction of Capacity) What are “quantity-based” elastic-capacity range needs on resources/output/activity/other? ? Reconfigu-ration What types of resource relationship configurations will need changed during operation? ?

System ______Team Wikispeed______________________ Sample Graphics for your modification into your system needs Resources Integrity Management Volunteers Knowledge Communication Standards eee fff Situational awareness Resource mix evolution Resource readiness Activity assembly Infrastructure evolution Team Collaboration Scrum Master Everybody Self Organizing Infrastructure Owner Active Infrastructure Passive Config 1 Config 2 Config n Sockets Signals Security Safety Service Peer to Peer Interaction Scrum Boards / Daily Standup Meeting Internal Team Trust Safety area / line of sight Agile System / Team Culture Rules/Standards

RRS Principles for System: ____ Team Wikispeed________ (Think: Plug-and-Play, Drag-and-drop) Reconfigurable Scalable Reusable Encapsulated Modules Modules are encapsulated independent units loosely coupled through the passive infrastructure. Volunteers/Teams Knowledge Standards Communication Evolving Infrastructure Standards ConOps and module interface and interaction standards that evolve slowly. Peer to Peer Interaction Scrum Boards / Daily Standup Meeting Internal Team Trust Safety area / line of sight Agile System / Team Culture Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal. Team Members can change focus to different area Redundancy and Diversity Duplicate modules provide fail-soft & capacity options; diversity provides functional options. New team members quickly integrated New members bring new perspectives Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules. Pair Teaming Knowledge Reuse Elastic Capacity Module populations & functional capacity may be increased and decreased widely within the existing infrastructure. Teams can grow and shrink as needs arise Peer-Peer Interaction Modules communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Swarm Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Daily Standup Meeting Deferred Commitment Module relationships are transient when possible; decisions & fixed bindings are postponed until necessary. Sprint Timeline, JIT Decision Making Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated. Team Members Choose Own Projects