1 / 10

Change Control Boards and Release Planning

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.

rhona-fields
Download Presentation

Change Control Boards and Release Planning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Change Control Boards andRelease Planning Presented by Alicia Iwaniw

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

  3. 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. Definitions

  4. 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

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

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

  7. Subscriber Process SW HW CCB Type of CCBs Infrastructure Inputs CCB ECCB SW CCBs HW CCBs Solutions Process CCB

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

  9. 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

  10. 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

More Related