Change Control Boards and Release Planning Presented by Alicia Iwaniw.

Slides:

Advertisements

Similar presentations

Software change management

Advertisements

Configuration Management

A BPM Framework for KPI-Driven Performance Management

Global Congress Global Leadership Vision for Project Management.

Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)

MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.

Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.

More CMM Part Two : Details.

Change Control Change is inevitable - how to manage it?

QAAC 1 Metrics: A Path for Success Kim Mahoney, QA Manager, The Hartford

Configuration Management Main issues:  manage items during software life cycle  usually supported by powerful tools.

Copyright 2009  Develop the project charter: working with stakeholders to create the document that formally authorizes a project—the charter  Develop.

GAI Proprietary Information

Dr. L. K. Gaafar The American University in Cairo

Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.

Project Integration Management Sections of this presentation were adapted from A Guide to the Project Management Body of Knowledge 4 th Edition, Project.

SE 555 Software Requirements & Specification Requirements Management.

Course Technology Chapter 3: Project Integration Management.

Remedyforce Value Enablement Kit – Change Management

1 Change Management FOR University Medical Group Saint Louis University Click this icon for Audio.

Planning. SDLC Planning Analysis Design Implementation.

Software Engineering Institute Capability Maturity Model (CMM)

Change Request Management

Project Life Cycle Introduction and Overview © Ed Green Penn State University All Rights Reserved.

How the Change Control Process Affects Project Quality

CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Change Control.

International Business and Technology Consultants AMS confidential & proprietary SPS Help Desk Presentation Army User’s Conference June 2002.

The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.

Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.

Software Project Management

SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.

Information Assurance The Coordinated Approach To Improving Enterprise Data Quality.

CMM Level 2 KPA’s CS 4320 Fall Requirements Management 1 Goals: – System requirements allocated to software are controlled using a baseline for.

Roles and Responsibilities

Configuration Management Matti Kuikka CONFIGURATION MANAGEMENT by Matti Kuikka, Unit Manager, Ericsson, Turku, Telecom R&D, Wireless Charging.

 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.

1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.

Agenda  Purpose  Definition  Processes  Performance Reports  Quality Control  Risk Monitoring & Control  Change Requests 5.3.

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.

Viking Quality Report Team Assignment 9 Team 2-1.

Software Quality Assurance

Georgia Institute of Technology CS 4320 Fall 2003.

© Mahindra Satyam 2009 Configuration Management QMS Training.

Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.

Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.

CHANGE CONTROL PROCESS SEPTEMBER 22, /16/2015 Purpose  a methodical approach for capturing, managing and implementing IT changes  ongoing management.

Configuration Management Main issues:  manage items during software life cycle  usually supported by powerful tools ©2008 John Wiley & Sons Ltd.

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.

Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.

Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands

How do You Fit within the Process? Roles and Responsibilities – Pre CAB (1/2) 1 Change Requestor Initiates the Change Request (CR) in Service-now Includes.

Project Organization Chart Roles & Responsibilities Matrix Add Project Name.

Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.

Software Testing Process

~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.

Texas Nodal Program ERCOT Readiness Update TPTF May 5, 2008.

1 CCSAS Governance An Overview 2007 Annual Child Support Training Conference and Expo September 18, :30 – 12:00.

Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.

1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.

USDA 2016 Financial Management Training Transforming Shared Services Change Management Presented by Ron Gros.

Agenda  Purpose  Processes  Deliverables  Executing Activities 4.3.

Change Request Management

Configuration Management

Software Project Configuration Management

Incident Management Incident Management.

CS4311 Spring 2011 Process Improvement Dr

Software Configuration Management

Configuration Management

TechStambha PMP Certification Training

Testing Workshop.

Presentation transcript:

Change Control Boards and Release Planning Presented by Alicia Iwaniw

AGENDA Definitions Reasons for having a CCB process Who are the drivers Process Type of CCBs Supporting tools Metrics Tips

Definitions CCB: Group of appropriate people who meet periodically, analyze change requests for consistency, review changes in a project, assign champions to implement corrective actions, monitor progress, check closures. Release Planning: Meetings held periodically to review the business integrity of a project/product release. The release planning takes under consideration the customer, marketing and financial issues and communicates via CCB meetings the urgency of a problem resolution.

Reasons for having a CCB process The CCB process is required to ensure schedule and business commitments for planned releases. Controlled process to estimate Impact of changes Communication that authorizes changes to a baseline release

Who are the drivers CCB Coordinator Quality Requirements Product architect Software Hardware Test / Integration Project Management Requestors / Petitioners

New CRs approval Process Request Entry CCB Coordinator reviews Request Core Team Reviews Requests E-Approved? Y N Assign and start cooking the solution Schedule CCB Mtg. Impact needed ? N Y Impact Analysis Impact Analysis Impact Analysis CCB meeting Approve Requests ? N Y Doc. Why Rejected.

Type of CCBs InfrastructureSubscriber Inputs Solutions

Supporting tools Rational Software Defect tracking tool: ClearDDTS QSS requirements tool: DOORS Internally developed scripts for reports and metrics generation.

Metrics CR lifecycle based on severities No. of CRs per release Closure Rate Unresolved CRs per manager Correlation with Customer Satisfaction surveys Correlation between unresolved corrective issues and Availability/Reliability

Tips Find consensus in the decisions Make Severity definition posters and leave them as decoration in CCB meeting rooms Plan for 3 minutes per item (20/hour) Follow up on decisions Be organized, consistent and be on time Ensure training : –supporting tools –supporting process Publish updates of metrics to DE Don’t forget the Hardware folks! Award effort on key members and engineers