Adaptive Product Development Process Framework

APD Process Speculate Collaborate Learn Request Solution 1.0 Project Approved Project Accepted Solution Request Solution 1.0 Project Initiation 2.0 Adaptive Cycle Planning 3.0 Concurrent Component Engineering 4.0 Quality Review 5.0 Final Q/A and Release Maintain Solution Speculate Collaborate Learn Legend: Preceding or Succeeding Process Project Process Parallel Processes Milestone Version 02 -- 2/ 21 / 2001

APD Process Summary Name Purpose Input Activities Output Notes To deliver Input Activities Output Request to develop a solution; the request may occur in various forms: Formal or informal Verbal or written Initial project charter Initial creative brief Initial prototype etc. 1.0 Project Initiation Identify the mission Identify project team Create mission artifacts Obtain approval Share mission values 2.0 Adaptive Cycle Planning Determine time boxes Write objective statements Define product components Assign components to cycles Plan project Develop project task list 3.0 Concurrent Component Engineering 4.0 Quality Review 5.0 Final Q/A and Release Solution Project documentation artifacts: Project Vision Project Data Sheet Product Mission Profile Product Specfication (outline) Mission Values Etc. Notes Place to describe roles, whatever Place for notes Version 02 -- 2/ 21 / 2001

2.0 Adaptive Cycle Planning 1.0 Initiate Project Request Solution Approved Project 1.1 Identify the Mission 1.3 Create Mission Artifacts Project vision (charter) Project data sheet Product mission profile Product specification (outline) 1.4 Obtain Approval 1.5 Share Mission Values 1.2 Identify Project Team 2.0 Adaptive Cycle Planning Version 02 -- 2/ 21 / 2001

1.0 Initiate Project Name Purpose Input Activities Output Notes To define the project and obtain approval to proceed Input Activities Output Request to develop a solution; the request may occur in various forms: Formal or informal Verbal or written Initial project charter Initial creative brief Initial prototype etc. 1.1 Identify the mission 1.2 Identify project team 1.3 Create mission artifacts Create project vision (charter) Create project data sheet Create product mission profile Develop product specification outline 1.5 Obtain approval 1.4 Share mission values Discuss quality Define the result Define the quality criteria to measure the result Approval to proceed Project documentation artifacts: Project Vision Project Data Sheet Product Mission Profile Product Specification (outline, Story Cards, Use Cases) Mission Values Etc. Notes Place to describe roles, whatever Place for notes Version 02 -- 2/ 21 / 2001

2.0 Adaptive Cycle Planning 4.0 Quality Review 1.0 Initiate Project JAD Sessions 2.1 Determine Time Boxes 2.2 Write Objective Statements 2.3 Define Product Components 2.4 Assign Components To Cycles 2.6 Develop Project Task List Feature Technology Support 2.5 Plan Project 3.0 Concurrent Component Engineering Version 02 -- 2/ 21 / 2001

2.0 Adaptive Cycle Planning Name Purpose 2.0 Adaptive Cycle Planning To define components and allocate them to cycles, conduct detailed planning of the next cycle incorporating feedback from quality review Input Activities Output Approval to proceed Change requests Project documentation artifacts: Project Vision Project Data Sheet Product Mission Profile Product Specification (outline) Mission Values Etc. 2.1 Determine time boxes Project Cycles 2.2 Write objective statements(for each cycle) 2.3 Define product components (using Joint Application Design sessions) Feature Technology Support 2.4 Assign components to cycles 2.5 Plan project Schedule Risks Analyze resource requirements Deploy methods and tools for collaboration Buffer the schedule 2.6 Develop project task list Cycle plan Product Specification (draft) List of product components allocated to cycles Project schedule Risk list Collaboration methods and tools Project task list Notes Place to describe roles, whatever Place for notes Version 02 -- 2/ 21 / 2001

3.0 Concurrent Component Engineering 3.4 Prepare For Quality Review 3.1 Develop Components Primary Technology Support 2.0 Adaptive Cycle Planning 4.0 Quality Review 3.2 Manage Project 3.3 Prepare For Final Q/A 5.0 Final Q/A and Release Version 02 -- 2/ 21 / 2001

3.0 Concurrent Component Engineering Name Purpose 3.0 Concurrent Component Engineering To develop components allocated to the cycle and make preparations for quality review and final Q/A. Input Activities Output Cycle plan Product Specification (draft) List of product components allocated to cycles Project schedule Risk list Collaboration methods and tools Project task list 3.1 Develop components* Primary Technology Support 3.2 Manage project Persisting (communications, focus, obstacle removal) Monitor progress, Contain change (bounding, ignoring, postponing, filtering, re-planning), 3.3 Prepare for final Q/A Develop test plan Develop test cases Develop test scripts 3.4 Prepare for quality review Setup meeting time & place Create agenda Executable Risk list (updated) Issues list Project status Change requests Test plan Test cases Test scripts Quality review agenda Notes * Practices that can be applied under 3.1 Develop Components: Daily and weekly builds Refactoring Pair programming Peer reviews, inspections Unit tests Integration tests Version 02 -- 2/ 21 / 2001

4.0 Quality Review 3.0 Concurrent 2.0 Adaptive Component Engineering 2.0 Adaptive Cycle Planning Customer Focus Groups 4.1 Conduct Cycle Review 4.2 Determine Next Steps OR - customer focus groups - Evaluate focus group results- 5.0 Final Q/A and Release 4.3 Conduct Cycle Post Mortem Review team, process and practice effectiveness Version 02 -- 2/ 21 / 2001

4.0 Quality Review Name Purpose Input Activities Output Notes To review incremental build of product and collect feedback. Decide whether to proceed with final Q/A or develop another cycle Input Activities Output Components Risk list (updated) Issues list Project status Change requests Test plan Test cases Test scripts Agenda 4.1 Conduct cycle review Conduct customer focus groups Document change requests Evaluate focus group results 4.2 Determine next steps Develop another cycle -or- Release for final Q/A 4.3 Conduct cycle post mortem Review team, process and practice effectiveness Take corrective actions Customer focus group results Change requests Decision to develop another cycle or release for final Q/A Cycle post mortem Corrective actions Notes * notes Place for notes Version 02 -- 2/ 21 / 2001

Component Development 5.0 Final Q/A and Release 2.0 Adaptive Cycle Planning 3.0 Concurrent Component Development 4.0 Quality Review Accepted Solution 5.1 Perform Tests 5.2 Evaluate Test Results 5.4 Make Decision 5.5 Transition To Production OR 5.3 Fix Problems 5.6 Close Project Maintain Solution Version 02 -- 2/ 21 / 2001

5.0 Final Q/A and Release Name Purpose Input Activities Output To review incremental build of product and collect feedback. Decide whether to proceed with final Q/A or develop another cycle Input Activities Output Customer focus group results Change requests Decision to develop another cycle or release for final Q/A Cycle post mortem Corrective actions Test plan Test cases Test scripts 5.1 Perform tests 5.2 Evaluate test results 5.3 Fix problems 5.4 Make decision 5.5 Transition to production 5.6 Close project Declare success, Wrap up loose ends Conduct post mortem Conduct party Test results Problem fixes Decision to release or develop another cycle Post mortem report Party Notes * notes Place for notes Version 02 -- 2/ 21 / 2001

2.0 Plan and Initiate Release Name Purpose 2.0 Plan and Initiate Release … Input Activities Output …. 2.1 Optional template …. Entry Criteria Exit Criteria …. …. Tools Notes Templates …. ….. …. Version 02 -- 2/ 21 / 2001