1. Agile Trainers – AEP Analysis
Jeffrey Richards
Curtis Hoffman
Rene Hanner

2. Strategic Values/Objectives Sought
Collaborative Development
Shortened Development Cycle
Test Driven Design/Development (TDD)
Integrating all skill levels – Pairing Concept
Minimal Overhead costs
Clearly defined team roles and responsibilities with no nonworking management roles
Use less stuff

3. Descriptive Statement
Team Wikispeed utilizes the concepts of agile, lean, and scrum to iterate and develop a highly modular and fuel efficient vehicle. The team uses free resources to collaboratively coordinate for each iteration of the design. These resources include linkedin, dropbox, Google Docs, and freeconference call which are available to everyday individuals. The process is highly dependent on volunteers who are passionate about the goals to produce a fuel efficient vehicle. This passion allows the team to work extensive hours in their free time which increases velocity.  

4. Proactive/Reactive Response Type Response Situations Creation
What must an Agile Engineering process be creating in the course of its operational activity?
Not good: More efficient way to utilize resources and focus energies of human capital
What does the process, once executing, have to create?
Better: Culture has to be created, instead of competition. Communication has to be created. Create an environment that attracts passionate people.
Improvement
What performance characteristics will an AEP process be expected to improve as it is used repeatedly?
Life Cycle turnaround time
Team Morale
Return on Investment
Refactoring
Migration
What major events coming down the road will require a change in the initially adopted AEP infrastructure?
Modifying the thought process for mass production
RM&S
Modification (capability)
What modification/evolutions in modules might be needed during the operational life cycle?
Addition of legal team
Correction
What can go wrong that will need a highly responsive fix?
Mass exodus of the committed core
Use of free resources that are no longer free
Variation
What process variables will range across what values and need accommodation?
Length of Sprint times
Available capital through donations
Expansion (Capacity)
What are “quantity-based” elastic-capacity range needs on resources/output/activity/other?
Amount and diversity of people involved in the group
Technical Debt – unable to go back and repay the technical debt before delivery date
Reconfiguration
What types of resource relationship configurations that will need changed during operation?
Reconfiguration of teams to focus on changing knowledge domains

5. Agile Engineering Process
Components/Modules
Integrity
Management
Lean Workstation
Scrum Team
Collaboration Software
Volunteers
User Stories
Task Backlog
Infrastructure evolution
System assembly
Module mix evolution
Module inventory readiness
Scrum Master
Scrum Master
Team Lead
Process Owner (JJ)
Active
Infrastructure
Passive
Shop Garage
Design Team
Competition
Sockets
Signals
Security
Safety
Service
Passion, Collaborative Working
Burn down log, standups/calls
Task Completion List, Backups
Pairing
Standard Interface Definitions
Rules/Standards
None

6. RRS Principles: Agile Trainers
Reconfigurable
Scalable
Reusable
Encapsulated Modules Modules are encapsulated independent units loosely coupled through the passive infrastructure.
Parallel Processing – design and test are not dependent
Small Sprint Times
Evolving Infrastructure Standards Module interface and interaction standards and rules that evolve slowly.
Amount of available capital leads to different topics – car to house
Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal.
Controlled Interfaces
Iterations and Stubs
Redundancy and Diversity Duplicate modules provide fail-soft & capacity options; diversity provides functional options.
Diversity of Volunteers
Amount of Volunteers
Online Forums
Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules.
Swarming – reuse of volunteer knowledge
Elastic Capacity Module populations & functional capacity may be increased and decreased widely within the existing infrastructure.
Pairing
Worldwide Support Group
Peer-Peer Interaction Modules communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored.
No Management positions
Team Morale
Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally.
Collaborative Working leads to quick unblock
Standups
Shared space
Deferred Commitment Module relationships are transient when possible; decisions & fixed bindings are postponed until necessary.
Don’t perform test until money is available
Test Driven Development
Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated.
Groups are self formed based on knowledge the volunteers bring to table