Lecture Notes on Release Management and Digital Product Release (DPR)

Introduction

• Day 19 of ITM batch.
• Topics covered: Incident, Problem, Change, Knowledge, CMD/CSDM, and now Release Management.
• Release Management module not visible in ServiceNow due to absence of plugin in PDI after the Washington DC release.
• New product introduced: Digital Product Release (DPR), different from traditional Release Management.

Key Concepts of Release Management

• Definition of Release Management:
  • Combining all complex changes into a package for release.
  • Involves building, testing, and deploying changes (e.g., software updates).
• Change Management vs. Release Management:
  • Change Management focuses on governing processes to minimize disruption in production.
  • Release Management involves building, testing, and deploying changes.
• Release Phases:
  1. Planning
  2. Build
  3. Deployment
  4. Review

Overview of DPR

• Requirement for DPR:
  • Users need specific roles (e.g., Product Manager, Release Coordinator).
• Workflow:
  • Users define the process, plan updates for products, and ensure readiness.
• Phases in DPR:
  • Interaction with change, configuration items, and problem management.
• Initial Setup:
  • Activation of Digital Product Release plugin needed.
  • Product definition includes product name, features, and versions.

Features of DPR

• Release Templates:
  • Each product may follow different deployment formats.
  • Templates for requirements gathering, planning, and approvals.
• Integration with DevOps:
  • DPR works with DevOps for continuous integration and delivery.
• Approval Processes:
  • Similar to Change Management, approvals are necessary at various phases.

DPR Process Details

• Creating a New Product:
  • Steps to define and create products and features within the system.
• Release Execution:
  • Phases include planning, development, and acceptance before final deployment.
• Release Policies:
  • Policies govern the movement between phases based on approvals and task completion.

Transition from Old Release Management to DPR

• Comparison:
  • DPR offers improved security, visibility, and is more integrated than old Release Management.
• Future of Release Management:
  • Old Release Management is being sunset; organizations encouraged to transition to DPR.

Service Catalog and Request Management

• Definition:
  • Service Catalog provides users with options to request items/services.
  • Request Management processes the order after payment, generating an order number.
• Understanding Workflows:
  • Workflows play a crucial role in managing requests and fulfilling them.
• Practical Examples:
  • Used restaurant ordering analogy to explain Service Catalog vs. Request Management.

Conclusion

• The transition to DPR is ongoing, with many organizations still utilizing the old Release Management.
• Key learning points: Importance of defining processes, using templates, and understanding integration with other modules like DevOps.

Next Steps

• Future sessions will cover Service Catalog and Request Management in detail.