Release Management

20,102 views

Published on

Achieve Release & Deployment Process Excellence with BMC Remedy ITSM

Published in: Technology, Business

Release Management

  1. 1. BMC REMEDY ITSM 7.6 RELEASE MANAGEMENT Webinar
  2. 2. Disclaimer <ul><li>All other trademarks, service marks and logos used in this webinar are the trademarks, service marks or logos of their respective owners. </li></ul><ul><li>The views expressed in this webinar are views of the speakers and do not necessarily reflect the views of Vyom Labs Pvt. Ltd. </li></ul>
  3. 3. AGENDA <ul><li>About Release Management </li></ul><ul><li>Release Request Lifecycle </li></ul><ul><li>Release Management form view </li></ul><ul><li>Roles in Release Management </li></ul><ul><li>Approvals involved in release requests </li></ul><ul><li>Release Management Tasks </li></ul>
  4. 4. Introducing Release management <ul><li>Release management is the process responsible for planning, scheduling, and controlling the movement of releases to test and live environments. </li></ul><ul><li>ITIL specifies that the primary objective of Release Management is to make sure that the integrity of the live environment is protected and that the correct components are released. </li></ul><ul><li>Release management works closely with Change Management to make sure that changes to the IT infrastructure are implemented to keep the functionality and service levels of the services aligned with the ever-changing business needs of their customers. </li></ul>
  5. 5. U nderstanding the need for R elease M anagement <ul><li>With numerous changes occurring daily, Release Management is the key component in making sure that applications are successfully deployed without compromising the integrity or availability of the production environment. </li></ul><ul><li>Using a systematic and repeatable release process, organizations can achieve greater success rates of change rollout, higher quality of IT service, and accelerated time-to-market. </li></ul>
  6. 6. Roles involved in Release request process: <ul><li>Release Coordinator </li></ul><ul><li>Reviews the RFCs for the services after they have been passed on from Change Management. </li></ul><ul><li>Organizes and facilitates the CAB meetings for the services. </li></ul><ul><li>Change Manager </li></ul><ul><li>Reviews the risk and impact analysis. </li></ul><ul><li>Ensures that appropriate actions have been planned to minimize both the risk of failure and the impact on users during change implementations. </li></ul><ul><li>Ensures that the timing of planned implementations does not conflict with other planned changes or events. </li></ul><ul><li>Obtains approval for changes. </li></ul>
  7. 7. BMC Remedy Release Management support & management roles
  8. 8. <ul><li>Task Implementer </li></ul><ul><li>Support staff member who performs the tasks associated with a change request. </li></ul><ul><li>Activity Assignee </li></ul><ul><li>Staff members or groups who perform the activities associated with a release request. </li></ul>
  9. 9. Process Flow Status bar on the Release form
  10. 10. Release lifecycle
  11. 11. Milestones in Release Request lifecycle:- <ul><li>Initiate </li></ul><ul><li>Plan </li></ul><ul><li>Build </li></ul><ul><li>Test </li></ul><ul><li>Deployment </li></ul><ul><li>Close down </li></ul>
  12. 12. <ul><li>Henry the release coordinator creates the release request </li></ul>Initiate milestone
  13. 13. <ul><li>A Release Request </li></ul>
  14. 14. <ul><li>In the Summary field, enter a brief description of the release. </li></ul>
  15. 15. <ul><li>Select the Risk Level to indicate the relative risk associated with the release </li></ul><ul><li>Click Rollup to accumulate the risk level from the related change requests </li></ul>
  16. 16. <ul><li>Henry then blocks out a time segment to work on the release by indicating the scheduled start and end dates. </li></ul>
  17. 17. Creating a Manifest <ul><li>The release must be divided into several changes and activities, </li></ul>
  18. 18. <ul><li>Activity </li></ul><ul><ul><li>Specific units of work are called activities . </li></ul></ul><ul><ul><li>Activities have their own lifecycle with a series of status transitions, </li></ul></ul><ul><ul><li>for example, Draft, Assigned, etc. </li></ul></ul><ul><ul><li>A sequence of tasks can be present in your activities. </li></ul></ul><ul><ul><li>Activities are useful when you need to create a structured sequence of tasks that you must complete to fulfill the release, but these tasks should not be classified as a change request. </li></ul></ul>
  19. 19. <ul><li>Creates a change request to install the new server for the payroll service at the Deployment milestone in change form. He assigns the change request to Mary, the change manager. </li></ul>
  20. 20. <ul><li>Mary’s profile on people form </li></ul>
  21. 21. Change request at the deployment milestone
  22. 22. <ul><li>Creates an activity to train employees on the new payroll service. He assigns it to John, the activity assignee </li></ul>
  23. 23. Collision Detection tool
  24. 24. Plan milestone <ul><li>Henry reviews the release plan </li></ul><ul><li>Henry reviews these requests for change with Mary, the change manager of the service for which the release is to be implemented. Together they divide the requirements of the different RFCs amongst them and they draft a high-level implementation plan that indicates the duration of each change, and the dependencies between these changes. </li></ul>
  25. 25. Release at Planning stage
  26. 26. <ul><li>John, the activity assignee plans to add training tasks to the activity that will be implemented in the last deployment phase. </li></ul>
  27. 27. <ul><li>Task generated w.r.t to the activity </li></ul>
  28. 28. <ul><li>Task attached with an activity of a Release request </li></ul>
  29. 29. Build milestone <ul><li>Henry establishes the approach to building the controlled Environments before the release goes into production. </li></ul>
  30. 30. Test milestone <ul><li>The release coordinator makes sure that the CIs, IT service, or process meet their specifications and requirements. </li></ul><ul><li>When all the tests have been completed satisfactorily, the release coordinator seeks approval from BMC Remedy Change Management for the actual deployment. </li></ul>
  31. 31. Deployment milestone
  32. 32. <ul><li>Mary, the change manager opens the change request and moves it to the </li></ul><ul><li>Implement stage. </li></ul>
  33. 33. <ul><li>Installation task inside change request, assigned to Charles D. </li></ul>
  34. 34. <ul><li>Charles installs the new server. </li></ul>
  35. 35. <ul><li>Mary then closes the change request. </li></ul>
  36. 36. <ul><li>John, the activity assignee executes the training activity. When all the trainers finish their tasks, she marks the activity as Completed. </li></ul>
  37. 37. <ul><li>The release request showing the manifest tab: </li></ul>
  38. 38. Close Down milestone <ul><li>The release request enters the Close Down milestone. </li></ul><ul><li>Reviewers provide feedback on the effectiveness of the release, and record metrics for deployment to make sure the release met its service targets. </li></ul>
  39. 39. Preconfigured approval phases & processes for Release Management <ul><li>Approval Phase </li></ul><ul><ul><li>Planning- </li></ul></ul><ul><ul><ul><li>This phase is defined in process Release Level CI – Planning which is Used with Configuration Item on the Approver Mappings form. The Planning phase starts when the release request is placed in Planning Approval status </li></ul></ul></ul><ul><ul><ul><li>If the release request is approved, it moves to the In Progress status. </li></ul></ul></ul><ul><ul><ul><li>If no approvers are mapped to the Planning phase, the release request moves to the In Progress status and requires the release coordinator to move the request forward. </li></ul></ul></ul><ul><ul><ul><li>If the request is rejected, it moves to the Rejected status. </li></ul></ul></ul><ul><ul><ul><li>By default, the status of this approval process for this phase is Enabled </li></ul></ul></ul>
  40. 40. <ul><li>Build- </li></ul><ul><ul><li>This phase is defined in process Release Level CI-Build which is Used with Configuration Item on the Approver Mappings form. The Build phase starts when the release request is placed in Build Approval status. </li></ul></ul><ul><ul><li>If the release request is approved, it moves to the In Progress status. </li></ul></ul><ul><ul><li>If no approvers are mapped to the Build phase, the release request moves to the In Progress status and requires the release coordinator to move the request forward. </li></ul></ul><ul><ul><li>If the request is rejected, it moves to the Rejected status. </li></ul></ul><ul><ul><li>By default, the status of this approval process for this phase is Enabled. </li></ul></ul>
  41. 41. <ul><li>Test- </li></ul><ul><ul><li>This phase is defined in process Release Level CI-Test which is Used with Configuration Item on the Approver Mappings form. The Test phase starts when the release request is placed in Test Approval status. </li></ul></ul><ul><ul><li>If the release request is approved, it moves to the In Progress status. </li></ul></ul><ul><ul><li>If no approvers are mapped to the Test phase, the release request moves to the In Progress status and requires the release coordinator to move the request forward. </li></ul></ul><ul><ul><li>If the request is rejected, it moves to the Rejected status. </li></ul></ul><ul><ul><li>By default, the status of this approval process for this phase is Enabled. </li></ul></ul>
  42. 42. <ul><li>Deployment- </li></ul><ul><ul><li>This phase is defined in process Release Level CI-Deployment which is Used with Configuration Item on the Approver Mappings form. The Deployment phase starts when the release request is placed in Deployment Approval status. </li></ul></ul><ul><ul><li>If the release request is approved, it moves to the In Progress status. </li></ul></ul><ul><ul><li>If no approvers are mapped to the Deployment phase, the release request moves to the In Progress status and requires the release coordinator to move the request forward. </li></ul></ul><ul><ul><li>If the request is rejected, it moves to the Rejected status. </li></ul></ul><ul><ul><li>By default, the status of this approval process for this phase is Enabled. </li></ul></ul>
  43. 43. <ul><li>Close Down- </li></ul><ul><ul><li>This phase is defined in process Release Level CI-Close Down which is Used with Configuration Item on the Approver Mappings form. The Close Down phase starts when the release request is placed in Close Down Approval status. </li></ul></ul><ul><ul><li>If the release request is approved, it moves to the Completed status. </li></ul></ul><ul><ul><li>If no approvers are mapped to the Close Down phase, the release request moves to the Completed status. </li></ul></ul><ul><ul><li>If the request is rejected, it moves to the Rejected status. </li></ul></ul><ul><ul><li>By default, the status of this approval process for this phase is Enabled. </li></ul></ul>
  44. 44. <ul><li>We need to map approvers to approver phases for level type approval processes </li></ul>
  45. 45. Q & A Session Questions Answers
  46. 46. <ul><li>www.vyomlabs.com </li></ul><ul><li>[email_address] </li></ul><ul><li>Our Locations: </li></ul><ul><li>Pune, India (Head Quarters) </li></ul><ul><li>Bangalore, India </li></ul><ul><li>Oklahoma, USA </li></ul>

×