Release Management

• Release Management (aka Release Train)


  can be defined as a methodology for planning and implementing an integrated set of functional components and processes in a controlled manner
• Data-driven


  releases are scoped in order to meet pre-specified delivery dates
• Reversed planned


  start with your target implementation dates and work backwards
• mechanized process


  should try to emulate a typical factory operation
• forecasted schedules as well as functionality


  force an organization to strategize and plan in advance
• Integrated and predictable


  many business needs folded into one release, and everyone knows the schedule
• Uses standard system development lifecycle (SDLC), project management methodologies (PMBOK) and best practices
• Each release will have its own release lifecycle, with their own phases
• Identified within each phase is a key milestone(s)
• Rigidity of the release schedule is dependent upon the organization implementing Release Management.
• Typically, there is a process for introducing “ Hot Fixes ” in between release deployment dates.
• PMBOK

  Project Management Body of Knowledge
• Release Manager


  A project manager whom manages release
• Business Project Manager


  Focused on the business needs
• Other Release Management – Roles

  Development Manager

  Configuration Manager

  Environments Manager

  Testing Manager
• Release Management Planning and Deployment tool (RMPD)


  Tracking of multiple business requests, the associated software deliverables of those requests, as well as release planning and scheduling, and the association of software deliverables contained within a release.
• Some tools that are currently available are:

  • Confluence
  • MS Planner
  • MS Project
  • Monday.com
  • Basecamp
  • Airtable
• Pilots are useful for testing the service with a small part of the user base before rolling it out to the whole business/ organization
• Software Quality Management


  Concerned with ensuring that the required level of quality is achieved in a software product
• QUALITY ASSURANCE


  The development of a framework of organizational procedures and standards that lead to high quality software.
• QUALITY PLANNING


  The selection of appropriate procedures and standards from this framework and adapt for a specific software project.
• QUALITY CONTROL


  Definition of processes ensuring that software development follows the quality procedures and standards
• Product Standards


  checks the output of the software development process
• Software Standards


  based on best practices and they provide a framework for implementing the quality assurance process
• Software Quality Attributes

  • Safety
  • Security
  • Reliability
  • Resilience
  • Robustness
  • Understandability
  • Testability
  • Adaptability
  • Modularity
  • Complexity
  • Portability
  • Usability
  • Accessibility
  • Reusability
  • Efficiency
  • Learnability