Release Sprint

When the Product Owner and Stakeholders identify that there is sufficient functionality in the system to provide immediate business value they may choose to put this into production. Typically, a "Release Sprint" will follow that contains all the necessary Sprint Backlog tasks to put the system into production. These tasks shouldn't contain additional functionality but they may include:

  • Deploying the code to the Production Environment
  • Production data population
  • Setting up management and operational systems and processes
  • Training and handover for support staff
  • Cutover and fallback planning

Setting a Sprint as a Release Sprint

To set a specific Sprint as a release Sprint rather than a normal Sprint, first choose the required Sprint from the "All Sprints Query". Then mark the "Is Release Sprint?" as "Yes". See the screenshot below:


Click image to view full size