Avion Knowledge Base
avion.ioSign inSign up
  • 👋Introduction
  • 👉Getting started
    • What is Avion?
    • Define your product backbone
    • Scoping and prioritizing your product
    • Creating your release plan
    • Aligning the team
    • Integrating with backlog tools
  • Docs
    • 👏Core concepts
      • Projects
        • Project team
        • Migrating to projects
      • Organizations
        • Invite a member
        • Remove a member
        • Roles
        • Transfer ownership
        • Configure your path
        • Delete your organization
    • 🚀Story map
      • Story map anatomy
      • Journeys and steps
      • Stories
      • Releases
      • Attachments
      • Tags
      • Personas
      • Labels
      • Dependencies
      • Search and filter
      • Sharing
        • Restricted links
        • Public links
      • Workflow
      • Importing data
        • Import from Excel
          • XLSX import template
        • Import from StoriesOnBoard
      • Exporting data
        • Export to PDF
        • Export to image
        • Export to CSV
        • Export to Excel
      • Rich text editor
        • Keyboard shortcuts
        • Known limitations
      • Keyboard shortcuts
      • Tips
    • 🤝Integrations
      • Backlog tools
        • Set up an integration
          • Authentication
          • Project / board selection
          • Backbone syncing
          • Map story states
          • Additional syncing options
          • Importing data
        • Sync data
          • Pushing
          • Importing
          • Attachments
          • Deleting data
        • Configuration
        • Pause an integration
        • Re-authenticate
        • Remove an integration
        • Maintenance
          • Removing stale webhooks
        • FAQs and troubleshooting
        • Services
          • Jira Cloud
            • Features
            • Set up
            • Permissions required
            • Mapping options
              • Mapping fix versions
            • Epics ~ our thoughts
            • Additional data syncing
              • Mapping custom fields
                • Company-managed projects
                • Team-managed projects
            • Migrating to epic hierarchies
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Verify webhooks
              • JQL import issues
              • Workflow issues
              • Ghost cards (cards with a dashed border)
              • Limitations
              • Jira Cloud or Jira Server
          • Jira Data Center (Server)
            • Features
            • Set up
              • Creating an application link
            • Permissions required
            • Mapping options
            • Additional data syncing
              • Mapping custom fields
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Ghost cards (card with a dashed border)
              • Jira Cloud or Jira Server
              • JQL import issues
          • Azure DevOps
            • Features
            • Set up
            • Permissions required
            • Import using WIQL
            • FAQs and troubleshooting
              • Verify webhooks
              • No Azure DevOps accounts were found for your user
              • Problems communicating with Azure DevOps
              • Work items couldn't be imported
              • Show epics in Azure DevOps backlog
              • Import limits
          • Trello
            • Features
            • Set up
            • FAQs and troubleshooting
          • GitHub
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
              • What types of GitHub Projects are supported?
          • Linear
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
      • Notifications
        • Slack
          • Set up
          • Configure notification settings
          • Remove Slack
      • Design tools and media
        • Figma
        • Adobe XD
        • Axure
        • Framer X
        • Invision Web & Studio
        • YouTube & Vimeo
      • Embed Avion
        • Confluence
        • Confluence Server
        • Notion
        • Coda
    • 🔒Security
      • Single Sign-On (SSO)
        • Setup & Configure SSO
        • Azure AD
        • Google Workspace
        • Okta
        • OpenID Connect
      • Two-factor authentication (2FA)
    • ❓FAQs
      • Attachment file types
    • 💳Billing
      • Plans and pricing
      • Legacy plans
      • Free trials
      • Billing and payments
      • Change your plan
      • Cancel your plan
      • Refunds
      • Startup, student and educational discount
  • Story Mapping Guides
    • How To Story Map — A Simple Example
    • Advantages of Story Mapping
    • A Recommended Workflow
Powered by GitBook
On this page
  • Overview
  • Create releases
  • Archive releases
  • Unplanned release
  • Best practice
  1. Docs
  2. Story map

Releases

Last updated 1 year ago

Overview

Releases in Avion are a collection of stories that—when shipped together—will deliver working, coherent software for your end-users. Depending on the maturity of your project, this could be an "MVP" or it could be a particular feature set, like "Ratings & Reviews". Some customers use releases for time-based delivery cycles, like Q1 and Q2, for example. However, it's worth noting that releases are not intended to be used as sprints in Avion. The story map is agnostic of your sprints.

Releases are powerful because they allow you to plan based on value to your end-users. They span horizontally across your , cutting through the and forcing you to plan more holistically.

The order of your releases matters! The order should follow your delivery priorities, so the top release is the next to be delivered, or is already in progress.

Create releases

Hover above any existing release and you will see an Add release button. Clicking this will create a new release and open up a panel for you to fill in some detail about the release.

Archive releases

When you have completed a release and need it to be removed from the story map, you can archive it. Do this by clicking Archive release from the release details panel or by right-clicking on the release name and selecting Archive release.

You can view your archived releases by going to the story map Archive from the side bar. From here you can restore releases to view your previously delivered plans.

Unplanned release

The unplanned release is a special type of release that holds stories that are not yet part of your delivery plans. The unplanned release:

  • Will be present by default when you create a new story map

  • Will always be at the bottom of the story map, (as the priority of your releases run from highest, at the top to lowest, at the bottom)

  • Cannot be renamed

  • Cannot be pushed to integrations (although individual stories can be, if you want)

  • Cannot be archived or deleted

Best practice

  • Releases are a powerful tool for sorting by must/could/should have (MoSCoW). This can be a great way to come up with your initial MVP

  • Order your releases from most important and most clear at the top to least important and most hazy at the bottom. This is your development roadmap

  • If a release is too large, try splitting it down into two or three deliverable chunks. But make sure each chunk delivers value on its own. For instance — Ratings & Reviews Base, Ratings & Reviews Enhancements, etc

  • We recommend not tying releases to sprints. Check this diagram for a nice illustration of our recommended delivery model:

  • Aim to make releases valuable and measurable. Set out the metrics you intend to measure when planning the release

  • Use the collapse/expand release feature to make planning easier. You can right-click a release name to access this or click the release's horizontal line to toggle the collapse/expand state

🚀
backbone
steps
Add a release
Release details