This session will cover the WHAT, WHY, and HOW of release orientation:

  1. What does it mean to be a release-oriented organization? (WHAT)
  2. Why should you move to release orientation? (WHY)
  3. How do you make the shift to become a release-oriented organization? (HOW)

WHAT (25 minutes): Project oriented organizations focus entirely on getting a related set of intent packaged into a container called a project and seeing that entire container move through from requirements generation to software release. Release-orientated organizations are singularly focused on continuously getting releases out the door that maximize business value delivery without being constrained to only releasing related business intent in the portfolio. To achieve the continuous release of software systems, organizations must apply lean thinking and principles to every aspect of their delivery frameworks and minimize the overhead associated with making releases with high quality. In this portion of the session, we will cover:

  • Agile organizational design and resource allocation to ensure maximum flow of shippable product to the release
  • Agile portfolio management, funding, and approval approach geared towards agile organizational design, smaller, incremental business intent approval and prioritization. Moving towards a mindset of customer value delivery in shorter iterations vs. delivering full projects. Moving away from large project funding towards capacity funding.
  • Lean configuration management and branching strategies focused on continuous releases
  • Automation strategies for a continuous integration, deployment, and testing model to allow scaling of a Release-Oriented organization
  • Fixed release schedules that provide a known cadence to delivery within groupings of business value streams
  • Lean, real-time architectural governance for new and significantly enhanced systems
  • The importance of holding and prioritizing retrospectives at both the team and release levels.
  • Creation of key Release-Oriented teams to provide the “glue” for the release and provide agile change management, software packaging and release

WHY (10 minutes): Release-orientation gets the entire organization to focus on the most important reason we exist as software developers – maximizing business value delivery through frequent, quality software releases. Moving the organization towards release-orienting thinking provides an invaluable lens for wise organizational decision making. In this portion of the session, we will cover:

  • Examples of decisions made when release-oriented vs. project-oriented
  • Key benefits realized when you have moved towards release-orientation
  • Enablement for scaling of agile frameworks when release-oriented
  • Release-orientation budgeting reduces organizational churn for resource allocation

HOW (15 minutes): The move from project-orientation to release-orientation is both a mindset shift as well as a framework practice change. For too many years, we as software developers, IT shops, and businesses have been successful delivering projects. In this portion of the session, we will cover:

  • How to sell the organization on the benefits of release-orientation
  • How to transform your company from its current organizational design to a structure that supports release-orientation - How to make release-orientation a long-lived, self-sustaining aspect of your software delivery framework.

Q & A (10 minutes): The session will finish with a brief questions and answers section.



Outline/Structure of the Workshop

  • What does it mean to be a release-oriented organization? (WHAT - 25 minutes)
  • Why should you move to release orientation? (WHY - 10 minutes)
  • How do you make the shift to become a release-oriented organization? (HOW - 15 minutes)
  • Q & A (10 minutes)

Session details are provided in the Abstract section.

Learning Outcome

The key learning objective for this session is to provide the motivation for all attendees to start approaching their current agile implementations in a release-oriented fashion and recognize the significant benefits of believing release-orientation versus project-orientation. After the session achieves this primary objective, attendees will also have a high level roadmap for next steps to realize release-orientation in their organizations.

Target Audience

Anyone with basic agile experience - Solution Delivery Executives / Leaders, Product Owners, Scrum Masters, and Team Members



schedule Submitted 7 years ago

Public Feedback