1. Create New feature Approved Change request Create User Stories for the feature Add User stories to Target Process backlog User Stories – 1.Create Story Plan 2.Create Design Doc 3.Implementation 4.Test cases Design doc created by spec factory/ developers Create Story Plan with Acceptance criteria for the feature May create additional user stories based on the story plan Map Acceptance criteria in story plan with User story confirmation Implementation Stage Test/Validation Stage Test cases created based on acceptance criteria in story plan Story Plan Process Flow

2. CONNECT User Story* for a new feature* is added to the Target Process Backlog per approval by the CONNECT Customer Configuration Control Board (CCCB) and/or Program CCB (PCCB). User Story - The use story has a card (As a… I want… So that…), conditions that must be met before the story can be started, conversations that track communication with the stakeholders, and confirmations that define done. Feature - A collection of “inter-related” (or similar) capabilities (user stories) that can be completed within a release. 1. New Feature User Story

3. Technical Specification and/or Design Document is developed by Specification Factory and/or CONNECT developer. 2. New Feature Spec/Design Doc

4. Story Plan is developed per Spec/Design Doc and Product Owner input to explain the business process. Once business process in place, Story Plan explains the detailed flow of the business process to facilitate software development. Story Plan includes User Acceptance. Story Plan also includes Test Acceptance Criteria. 3. Story Plan for New Feature

5. Story plans are typically created for large/epic features or services. One to one mapping between story plan and a feature/Service. It explains business process, implementation specific design detail and acceptance criteria for validating the process steps. 3.1 Characteristics of Story Plan

6. User Stories resulting from Story Plan are assigned to and implemented by CONNECT developers. Confirmation of User Stories is mapped to the corresponding Acceptance Criteria within the Story Plan. Once implementation is complete, User Stories are tested against Acceptance Criteria included in Story Plan. 4. Develop and Test New Feature

7. User Stories completed and successfully tested per Story Plan Acceptance Criteria are included in official CONNECT baseline. Original User Story as well as resulting User Stories are statused throughout the development process within Target Process and closed within Target Process upon completion. New Feature/Implementation is described in Release Notes for all official CONNECT releases. 5. New Feature in Release