CREOSS Agile Software Execution Framework Value Proposition.

1. “ Agile In a Box” An overview of the Rhythm Agile Software Development Ecosystem (ASDE) and Agile Execution Framework (AEF) Version 1.2

8. Enter: Agile Manifesto (http://agilemanifesto.org)

14. Staged versus Stacked Iterations Staged Stacked X X X X   X X  X X X      Highly Tuned Software Factory Test Domain Area 4 Write Test Specs against Domain Area 5 Test Domain Area 3 Write Test Specs against Domain Area 4 Test Domain Area 2 Write Test Specs against Domain Area 3 Test Domain Area 1 Write Test Specs against Domain Area 2 Write test specs against Domain Area 1 Develop Domain Area 4 Req/Anal/DesignDomain Area 5 Develop Domain Area 2 Req/Anal/DesignDomain Area 3 Develop Domain Area 3 Req/Anal/DesignDomain Area 4 Develop Domain Area 5 Develop Domain Area 1 Preparation Req/Anal/DesignDomain Area 6 Req/Anal/DesignDomain Area 2 Req/Anal/DesignDomain Area 1 Test Domain Area 2 Write Test Specs against Domain Area 3 … wait… … wait… Test Domain Area 1 Write Test Specs against Domain Area 2 Write test specs against Domain Area 1 Develop Domain Area 2 … wait… … wait… … wait… … wait… Req/Anal/DesignDomain Area 2 … wait… Develop Domain Area 1 Preparation … wait… … wait… Req/Anal/DesignDomain Area 1 Iteration 1 Iteration 2 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Iteration 6

16. Status Quo “ We do a horrible job going from one iteration to the next; we feed on percentage complete!” “ Our artifacts(specs) are close to being worthless; they are big, heavy, out of date and often times more wrong than right.” “ Our project plans are big, heavy and just about worthless (change all the time) that typically do not include defects, change requests and the underlying tasks that are the important details showing dependencies, etc. “ “ Our methodology team gets in our way, is completely worthless, try to help, but end up getting in our way, can we send them elsewhere?” “ Once we get towards the end of the project, we don’t seem to have a good pattern for managing our backlog of defects and such.” “ Our software deliveries are atrocious, most of our deliveries fail on deployment, our unit tests hardly work or cannot be re-run once they’ve been run.” “ Our ‘review’ meetings such as design review meetings are horrible experiences that are a bear to get through.” “ Our team has no rhythm, we restart, pause, delay all the time; we can’t get into a consistent groove with the organization participating.”

17. Putting together some ingredients… “… we are status-based, instead of delivery based!” Iteration Transition Meeting (ITM) “ ..worthless artifacts” Iteration Artifacts “… worthless project plans “ Software Iteration Plan (SIP) “… methodology team gets in our way” Iteration Advocate “… lack of pattern for managing our backlog of defects ….” Issue Review Meeting (IRM) “… software deliveries are atrocious” Software Push “… worthless review meetings.” Iteration Artifact Review Meeting (iARM) “… no rhythm” Heartbeat/Stacked Iterations

20. Rhythm ASDE (Myers flavor) Enhancement Requests New Feature Requests Defects PDS SRS SIP Roadmap Phase 1: Definition Client Facing Group QA/Test PPB PM Factory Definition Team

21. Rhythm ASDE (Myers flavor) Agile Software Factory Enhancement Requests New Feature Requests Defects Iteration 5 Iteration 6 Iteration 7 Iteration 8 Iteration 9 Iteration 9 Iteration 10 Iteration 11 PDS SRS SIP … .. Roadmap Phase 2: Iteration Phase 1: Definition Client Facing Group QA/Test Iteration 1 Iteration 2 Iteration 3 Iteration 4 iDS iCode iTS iSRS iDS iCode iTS iSRS iDS iCode iTS iSRS PPB Factory Team PM Factory Definition Team

22. Rhythm ASDE (Myers flavor) Agile Software Factory Enhancement Requests New Feature Requests Defects Phase 1: Definition Phase 3: Production Iteration 5 Iteration 6 Iteration 7 Iteration 8 Release Opportunity Iteration 9 Iteration 9 Iteration 10 Iteration 11 Release Opportunity Release Opportunity PDS SRS SIP … .. … .. Phase 2: Iteration Roadmap Client Facing Group QA/Test Iteration 1 Iteration 2 Iteration 3 Iteration 4 iDS iCode iTS iSRS iDS iCode iTS iSRS iDS iCode iTS iSRS Factory Definition Team PPB Factory Team PM

23. Rhythm ASDE (Myers flavor) Project Planning Board (Mondays 1pm) Phase 1: Definition Phase 3: Production Phase 2: Iteration iARM (Wednesdays, 9-11) SIP Review (Wednesdays, 3-4pm) iTM (Thursdays, 10-11am) IRM (Frequency dependent upon org) Factory Definition Team PPB CFG Factory Iteration Team PMO PPB/CFG (both optional but requested) PPB/CFG

24. Rhythm AEF (Phase 2: Iteration) Principles Primary Ancillary Your ASDE, PLUS: Buyer/Seller marketplace for artifact promotion Iteration Transition Meeting (ITM) Code, and specs are cycled together Iteration Artifacts Functionality, defects, change requests and tasks all in one place. Software Iteration Plan (SIP) Buzzing bee; Risk mitigator; Process-mentor in disguise! Iteration Advocate (IA) Transitioning from iterations to pre-production taskings Issue Review Meeting (IRM) Regression tested functionality for delivery Software Push Informal transfer of artifacts. A review of the next iterations domain developers are to build Iteration Artifact Review Meeting (IARM) Establish, support the rhythm of the efforts related to the project Heartbeat/Stacked Iterations At the conclusion of each iteration, challenge the team to migrate the application, one or two environments upstream Upstream Migration At end of each Hearbeat, measure planned versus actual Measure Velocity Pick a location; come only if you have something to say/contribute Daily 15 minute meetings Set this up once, it acts like a virtual developer whos job is to build applications Continuous Integration Engine (CIE) Performance test your implementation at 40 and 60 percent point. Performance test at the 40% and 60% completion The conveyor belt into production Unified Build Infrastructure (UBI) Use the ITM’s as your software factory; gate small and frequent releases Release Management and PMO Transfer debugging time into your regression testing engine Test Driven Design and Development (TDDD)