School of Systems and Enterprises Stevens Institute of Technology, USA ES/SDOE 678 Reconfigurable Agile Systems and Enterprises Fundamentals of Analysis, Synthesis, and Performance Session 4 – Analysis: Team Analysis Exercise School of Systems and Enterprises Stevens Institute of Technology, USA

Tassimo Beverage System Drag-and-Drop – Plug-and-Play File BRAUN - http://www.tassimodirect.com/tassimo/

In-Class Tool Applications Class Warm-ups Team Trials Team Project Unit 2 Unit 3 Unit 4 Unit 5 Unit 6 Unit 7 Unit 8 Unit 9 Unit 10 AAP Analysis: Football ConOps: Objectives Reality Factors: TSA CURVE & Reality RSA Analysis: Tassimo RSA Analysis: TWS RSA Analysis RRS Analysis: Multiple AAP RRS Analysis: TWS RRS Synthesis ConOps: Activities Integrity: TWS Closure

Tassimo Beverage System Response Issues Correction Variation Reconfig-uration Expansion (Capacity) Migration Improve-ment Modification (Capability) Creation Proactive Reactive Response Type Response Situations What artifacts/data/knowledge must the system be creating or eliminating during operational activity? On demand beverage experience What performance characteristics will the system be expected to improve over time? Time to make a drink What major event coming down the road will require a change in the system infrastructure? International power What modifications/evolutions in modules might be needed during the operational life cycle? Other pods Size of machine What can go wrong that will need an automatic systemic detection and response? Leaching plastic Reservoir low sensing What process variables will range across what values and need accommodation? Variety of beverages What are “quantity-based” elastic-capacity range needs on resources/output/activity/other? Size of the beverage What types of resource relationship configurations will need changed during operation? Ease of dissembly Beverage making for recipe elements Response Situations (Amalgam) Correction Variation Reconfig-uration Expansion (Capacity) Migration Improve-ment Modification (Capability) Creation Proactive Reactive Response Type Hot beverages to order New recipe creation New T-disk creation Make better tasting stuff Faster Easier cleaning Sense size of cup User custom-recipes, remembered Other mfg’ers disks Other kinds of drinks (eg cocktails) Other kinds of stuff (eg soups) Add features (eg Auto-start timer) Bar-code reader failure manual fall-back Power failure (graceful recovery) Cup overflow Taste preferences Volume variation per cup Seasonal changes in market tastes? Number of process steps Two cups simultaneously Small to large cup Process steps per disk Homemade disk inserts Multi-disk recipes x Battery for camping x Night light x Wrong-size-cup detector x Pleasurable user experience (these change framework, not modules) maybe modification migration or Overall system value ≠ system activity

Guest Speaker: Joe Justice Managing a Collaborative Multi-National Team in Real Time Recorded at Agile2012 Dallas, TX, 13-17Aug2012 File36 Transcript Team WIKISPEED entered a $10 Million competition to produce road legal 100+ mpg cars. They built the impossible in three months, and they have done it repeatedly. Joe Justice will talk about Agile practices applied to speed up development and physical manufacturing. Joe leads Team WikiSpeed, and walks through how their 100 MPG road car was made possible through modular design, iterative development, and Agile project management. This Keynote features a short piece by Christopher Gong from Deloitte’s Center for The edge, reviewing the 2011 Shift Index, which shows disturbing trends in Fortune 50 company performance and longevity, This session shows the WikiSpeed approach applied in a number of other-than-car product development companies, with a revealing detailed walk-through at Tait Radio. Raw video at: www.parshift.com/s/JusticeJoe-ManagingCollaborativeMulti-NationalTeam-55-92min.mp4 Edited video at: www.parshift.com/s/JusticeJoe-ManagingCollaborativeMulti-NationalTeam-Edited36min.mp4 Transcript at: www.parshift.com/s/JusticeJoe-ManagingCollaborativeMulti-NationalTeam-55-92min-Transcript.pdf

Terms Used by Joe Justice File Product Owner Scrum Master Scrum Object Oriented Programming (OOP) Test Driven Development (TDD) Extreme Programming (XP) Kanban Lean Software Development Standup Meeting Technical Debt Backlog Refactoring Sprint Sprint Planning Meeting Team WikiSpeed Methods & Terms at: www.parshift.com/AgileSysAndEnt/Cases/Case Team WikiSpeed Methods and Terms.pptx

Response Requirements In addition to the system functional requirements, response situation analysis helps identify response requirements that inform the design of architecture, indicating the necessary nature of modules and modules pools, which in turn help identify the necessary nature of both passive and active infrastructure. Note that response requirements are system-operational time requirements, not system-design time requirements; and should be stated as operational needs independent of possible solution strategies which will evolve with time. Proactive domains Creation/Elimination – what artifacts/data/knowledge must the system create during operation that can be facilitated by modules and module pools; what situational evolution will cause obsolesce of modules which should be removed? Improvement – what improvements in system response performance will be expected over the system operational life? Migration – what evolving technologies and opportunities might require future changes to the infrastructure? Modification – what evolving technologies, opportunities, and situations might require future modifications to modules? Reactive domains Correction – what types of response activities might fail and need correction? Variation – what operational conditions and resources vary over what range when response capabilities must be assembled? Expansion/Contraction – what are the upper and lower bounds of response capacity needs? Reconfiguration – what types of situations will require modular system reconfiguration to react effectively?

In-Class Tool Applications Class Warm-ups Team Trials Team Project Unit 2 Unit 3 Unit 4 Unit 5 Unit 6 Unit 7 Unit 8 Unit 9 Unit 10 AAP Analysis: Football ConOps: Objectives Reality Factors: TSA CURVE & Reality RSA Analysis: Tassimo RSA Analysis: TWS RSA Analysis RRS Analysis: Multiple AAP RRS Analysis: TWS RRS Synthesis ConOps: Activities Integrity: TWS Closure

Exercise – RS Analysis of Agile Engineering Process Today you are going to analyze the response issues of managing the Team WikiSpeed (TWS) agile engineering process, not the agile product (car). Tomorrow you will design an agile solution to the issues you identify today. Your knowledge base is the Joe Justice videos. If you have additional appropriate knowledge, from any domain, that’s a plus and should be brought to bear, but it isn’t necessary. You will have to think about the issues that Joe doesn’t articulate. Discuss what you saw in the videos and compare notes amongst your team. Generate: Slide 1: Strategic Values/Objectives Sought Slide 2: RS Analysis – response issues in 8 change domains NOTE: This and the subsequent related design exercise go in a new and separate file. Name your work file: ExAEP-teamname.pptx (or ppt). This exercise is about the issues that must be addressed for a distributed development project which occurs in an unpredictable and uncertain environment – where project requirements, goals, budget, and time may be discovered and may change during the development effort. You are identifying fundamental response issues that your agile process must be able to deal with. No solution suggestions should be present, just problems/issue that need to be addressed. Prepare two (or three) slides for brief out

Team: __________________________ Agile System-Engineering Process: Team WikiSpeed Descriptive Statement ? Strategic Values/Objectives ?

RS Analysis for an Agile Engineering Process (AEP) Change Domain General Issues Proactive Reactive Creation (and Elimination) What artifacts/knowledge must an Agile Engineering process be creating during its operational activity? ? Improvement What performance characteristics will an AEP process be expected to improve as it is used repeatedly? ? Migration What major events coming down the road will require a change in the initially adopted AEP infrastructure? ? Modification (Add/Sub Capability) What modifications/evolutions in modules might be needed during the operational life cycle? ? Correction What can go wrong that will need a highly responsive fix? ? 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 in the course of process operation? ?

BREAK For Wikispeed exercises coming up later, check out: Methods & terms in binder section 3 Wikispeed video transcript in binder section 4 (after slides) BREAK Your Class web-page: www.parshift.com/678/current.htm Support docs & links: www.parshift.com/678/support.htm

FEEDBACK REVIEW (Lesson: RS Analysis states the response issues… without any hint of how they should be resolved)

RAP Tools & Process We discussed the yellow boxes. All lectures will show what has been discussed like this. Operational Story with CURVE "When I am working on a problem, I never think about beauty, but when I have finished, if the solution is not beautiful, I know it is wrong." -- R. Buckminster Fuller Quality Evaluation Reality Factors Identified RAP Tools & Process Closure Matrix Design Response Situation Analysis ConOps Objectives & Activities Agile Architecture Pattern RRS Principles Synthesis

IMPORTANT Read the term project instructions in tab 12, you will have an opportunity to clear up any questions tomorrow. Tomorrow at day’s end, know what your term project will be about

In-Class Tool Applications Class Warm-ups Team Trials Team Project Unit 2 Unit 3 Unit 4 Unit 5 Unit 6 Unit 7 Unit 8 Unit 9 Unit 10 AAP Analysis: Football ConOps: Objectives Reality Factors: TSA CURVE & Reality RSA Analysis: Tassimo RSA Analysis: TWS RSA Analysis RRS Analysis: Multiple AAP RRS Analysis: TWS RRS Synthesis ConOps: Activities Integrity: TWS Closure

Exercise Re-evaluate and refine RS Analysis for your project Make ready for presentation tomorrow morning – Fill out an 8-part Response Situation Analysis template with [t,c,p,s] metric-priorities for each issue add to end of your Ex-<team name> file Prepare one new slide for brief out

RS 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 General Issues Proactive Reactive Creation (and Elimination) What artifacts/data/knowledge must the system be creating or eliminating during its operational activity? ? ? Use as many bullet points as appropriate Improvement What performance characteristics will the system be expected to improve over time? ? Migration What major event coming down the road will require a change in the system infrastructure? ? Modification (Add/Sub Capability) What modifications/evolutions in modules might be needed during the operational life cycle? ? Correction What can go wrong that will need an automatic systemic detection and response? ? 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? ?