1. ES 678 Engineering of Agile Systems and Enterprises Team Members: Brian Andrews Craig Kerr John Parker

2.  Strategic Values/Objectives > 100MPG vehicle Street legal Five Star safety rating Uses less stuff Aesthetically pleasing Reconfigurable Descriptive Statement ?

3. Correction Variation Reconfigu- ration Expansion (and Contraction of Capacity) Migration Improvement Modification (Add/Sub Capability) Creation (and Elimination) Proactive Reactive Change Domain What performance characteristics will the system be expected to improve during operational life cycle? Reduce Change cycle time Reduce Cost of change What must the system be creating or eliminating in the course of its operational activity? Vehicle Development Team Eliminate wasted tool search time High morale What major events coming down the road will require a change in the system infrastructure? Changing Safety Requirements Commercialization – designs and prototypes are not products Team member quality – production team is different from development team What modifications in resources-employed might need made as the system is used? Module management – which modules must be created and why? Strategic product planning ability - What can go wrong that will need an automatic systemic detection and response? Liability/ legal issues Development of system firmware patches and upgrades What process variables will range across what values and need accommodation? Supply chain relationships issues Unanticipated material changes What are “quantity-based” elastic-capacity needs on resources/output/activity/other? Production capacity Optional module development Change management What types of resource relationship configurations will need changed during operation? Manage/restrict module options and interface contracts Certification issues with flexible configurations Customer interface/website Change/Response Issue

4. Reconfigurable Scalable Reusable Encapsulated Modules Modules are encapsulated independent units loosely coupled through the passive infrastructure. Team leadersModule Designs DevelopersCommunications Processes Tests Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal. Communication Standards Process Standards Training/Orientation Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules. Change pairing Peer-Peer Interaction Modules communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Online communications media (social media) Deferred Commitment Module relationships are transient when possible; decisions & fixed bindings are postponed until necessary. Use of stubs Build to order Evolving Infrastructure Standards Module interface and interaction standards and rules that evolve slowly. Process updates Group communications updates Team skill needs Evolving goals Redundancy and Diversity Duplicate modules provide fail-soft & capacity options; diversity provides functional options. Pair working teams Volunteer based workforce Online consultation with deep nerds Elastic Capacity Module populations & functional capacity may be increased and decreased widely within the existing infrastructure. Quick, documentation free introduction of new team members Distributed workplaces Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Distributed teams Online documentation (google docs, video) Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated. Team Swarming SCRUM

5. developers/ engineers communicationsteam leadersprocesses tests designs Infrastructure evolution System assembly Component mix evolution Component inventory readiness Self organizing Incremental delivery Iterative convergence Emergent requirements Infrastructure X-prize Team Distributed TeamsJoe Justice Components Rules/Standards Integrity Management Active Passive Time Emergent and team Team/Process TL and volunteer emergent Team leaders (key core practices detailed in a process manual) Agile WIKISpeed Development Process www.parshift.com/Files/PsiDocs/Pap080404Cser2008DevOpsMigration.pdf Group communications updates Team skill needs Process updates Evolving goals

6. Correction Variation Reconfigu- ration Expansion (and Contraction of Capacity) Migration Improvement Modification (Add/Sub Capability) Creation (and Elimination) Proactive Reactive Change Domain What performance characteristics will the system be expected to improve during operational life cycle? Change cycle time Cost of change What must the system be creating or eliminating in the course of its operational activity? High fuel efficiency vehicle Adaptability to multiple, complete changes in track layout What major events coming down the road will require a change in the system infrastructure? Safety Requirements Commercialization Team member quality What modifications in resources-employed might need made as the system is used? Module management Strategic product planning What can go wrong that will need an automatic systemic detection and response? Liability/ legal issues Development of system firmware patches and upgrades What process variables will range across what values and need accommodation? Supply chain relationships Material changes What are “quantity-based” elastic-capacity needs on resources/output/activity/other? Production capacity Optional module development Change management What types of resource relationship configurations will need changed during operation? Manage/restrict module options and interface contracts Certification issues with flexible configurations Customer interface/website Change/Response Issue

7. Correction Variation Reconfigu- ration Expansion (and Contraction of Capacity) Migration Improvement Modification (Add/Sub Capability) Creation (and Elimination) Proactive Reactive Change Domain What performance characteristics will the system be expected to improve during operational life cycle? Ergonomics Air bags Performance What must the system be creating or eliminating in the course of its operational activity? High fuel efficiency Adaptability to multiple, complete changes in track layout Customer satisfaction What major events coming down the road will require a change in the system infrastructure? Safety Requirements Auto-driving What modifications in resources-employed might need made as the system is used? Additional modules to support different driving styles (multiple aeroshells) Creature comforts (air conditioning, cup holders, GPS, radio, etc.) What can go wrong that will need an automatic systemic detection and response? Replacement and repair parts System firmware patches and upgrades What process variables will range across what values and need accommodation? Fuel efficiency with different modules Color offerings What are “quantity-based” elastic-capacity needs on resources/output/activity/other? Production capacity Passengers and payload Optional modules What types of resource relationship configurations will need changed during operation? Restrict module combinations Certification issues with different module combinations Customer interface/website Change/Response Issue