Create New feature Approved Change request Create User Stories for the feature Add User stories to Target Process backlog User Stories – 1.Create Story.

Slides:



Advertisements
Similar presentations
Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
Advertisements

BAM! Business Analysis Methodologies. Change-driven or Plan-driven?
Chapter 4 Quality Assurance in Context
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
<<replace with Customer Logo>>
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
Agile development By Sam Chamberlain. First a bit of history..
GAI Proprietary Information
SE 555 Software Requirements & Specification Requirements Management.
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
SE 555 Software Requirements & Specification Requirements Validation.
Software Configuration Management (SCM)
Course Technology Chapter 3: Project Integration Management.
1 Change Management FOR University Medical Group Saint Louis University Click this icon for Audio.
Software Engineering Institute Capability Maturity Model (CMM)
CSSE 375 Software Construction and Evolution: Configuration Management
Change Request Management
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Release & Deployment ITIL Version 3
Requirements Management Plan - Documents
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
RMsis – v Simplify Requirement Management for JIRA
CC20O7N - Software Engineering 1 CC2007N Software Engineering 1 Requirements Engineering Practices with Techniques.
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Software Configuration Management
Software Testing Life Cycle
Software Configuration Management (SCM)
Independent User Acceptance Test Process (IUAT)
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Requirements Traceability: Planning, Tracking and Managing Requirements Presenter: Paula R. Maychruk, BV/TEd., CAPM, CBAP.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Software Requirements Engineering: What, Why, Who, When, and How
INFO 637Lecture #51 Software Engineering Process II Defining Requirements INFO 637 Glenn Booker.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004.
Software Quality Assurance
Configuration Management Benchmarking Group Conference June 6 – 9, 2004 Kansas City, MO © 2004 CMBG Characteristics of a Good Calculation Program Presented.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
@2002 Copyright, Itreya Technologies CMMI kick off July 2005.
TM Copyright © 2009 NMQA Ltd. Behaviour Driven Testing with.
Develop Project Charter
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Project management Topic 1 Project management principles.
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
Integrated Change Control 1 MEC-8. Processing of a Change Processing of a Change 2 Assess Impact within KA Change Request Implemented Change Create a.
January 24, 2009 Agile Product Management Making Things Happen Walter Bodwell Planigle.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Project Management Basics
SCRUM.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Introduction to Agile. Introduction Who is this guy?
Information Technology Project Management, Seventh Edition.
Fall CS-EE 480 Lillevik 480f06-l4 University of Portland School of Engineering Senior Design Lecture 4 Definition phase Design phase.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Change Request Management
User Stories > Big and Small
Software Project Configuration Management
Preliminary Power Point Slides
TechStambha PMP Certification Training
Software Configuration Management
Guidance notes for Project Manager
KEY PROCESS AREAS (KPAs)
Applied Software Project Management
Configuration Management
Presentation transcript:

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

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

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

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

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

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

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