WikiSpeed Process Team Pest Control Mike McMahon Justin Petersen Dustin Soeder David Tolman

Team: Pest Control System: Team WikiSpeed Process Strategic Values/Objectives Volunteer Shared workspace (physical and virtual) Modular Rapidly iterated Innovate quickly High-velocity/high-morale Descriptive Statement To create a distributed volunteer team for the purpose of creating a 100mpg car.

Response Situation Analysis for System: Team WikiSpeed Process 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/process be creating or eliminating during operational activity? The team -Tests Roles and responsibilities Central command point Improvement What process/system performance characteristics will be expected to improve during its operational life cycle? Rate of learning Team knowledge capacity Morale Migration What major events coming down the road will require a change in the process/system infrastructure? Virtually distributed to physically located, and vice versa Increasing team size Modification (Add/Sub Capability) What modifications to employable resources might need made as the process/system is used? Onboarding/training Single, growing physical location Correction What will impair/obstruct process/system agility that will need an automatic systemic detection and response? Failed objectives Variation What process/system variables will range across what values and need accommodation? Shipping and receiving times/availability of parts and materials Requirements changes Cultures, opinions, styles Expansion (and Contraction of Capacity) What are “quantity-based” elastic-capacity range needs on resources/output/activity/other? Unexpected team size growth and diminishing Available budget Reconfigu-ration What types of resource relationship configurations will need changed during operation? A spread factory to a central location

Team Wikispeed Agile Engineering Process Graphic template for your modification Resources Integrity Management Virtual Knowledge Repository Product Owner ScrumMaster Volunteers Workspace Situational awareness Resource mix evolution Resource readiness Activity assembly Infrastructure evolution Product Owner / Volunteers Volunteers / Scrum Master / Joe Justice ScrumMaster Joe Justice Joe Justice Active Infrastructure Passive Sprint Test Swarm Sockets Signals Security Safety Service Peer-Peer Interaction Daily Scrum Info Trustworthy Transparency Collaborative Review Process Rules & ConOps

RRS Principles for System: Team WikiSpeed (Think: Plug-and-Play, Drag-and-drop) Reconfigurable Scalable Reusable Encapsulated Resources Resources are encapsulated independent units loosely coupled through the passive infrastructure. Product Owner Scrum Master Teams Workspaces – Local & Remote – Physical & Virtual Evolving Infrastructure Key elements of the infrastructure likely to evolve and need to be evolvable? Training Tools Team Integration / Human Element / Scrum Evolution Skillsets Facilitated Interfacing (Pluggable) Resources & infrastructure have features facilitating easy module insertion/removal. Scrum Meetings + Scrum Master Pairs Swarms Collaboration Media – Virtual Tools – You Tube Redundancy and Diversity Duplicate resources provide fail-soft & capacity options; diversity provides functional options. Individual skillsets Work locations – distributed producers Pair approach / Crosstraining Facilitated Reuse Resources are reusable and/or replicable; with supporting facilitation for finding and employing appropriate resources. Cross Trained Volunteers Organized Tools Training Videos – Collaboration Media Automated Test approaches Elastic Capacity Resource populations & functional capacity may be increased and decreased widely within the existing infrastructure. Work Scaling due to available resources & skillsets Donation funding to acquire missing skillsets Peer-Peer Interaction Resources communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Pairing approach Swarming Collaboration Media – Virtual – Skype/GoogleDocs Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Scrum Master Product Owner Swarms Collaboration Media – Google Docs/You Tube Deferred Commitment Resource relationships are transient when possible; decisions & fixed bindings are postponed until necessary. Short Sprints – 2 Weeks Test Driven Development – focus on good enough Self-Organization Resource relationships are self-determined; and resource interaction is self-adjusting or negotiated. Pairing approach Swarming Volunteer structure Rotating Product Owner