All Collections
Getting started
Configuring Increments in BigAgile
Configuring Increments in BigAgile

A guide to Increments - what are they and how to configure them in Big Agile

B
Written by BigAgile Support
Updated over a week ago

Increments are time periods defined by you, and a key component to structuring your programme delivery timeline in BigAgile.

💡Tip: Most commonly, a single Increment is 3 months long and is made up of 6, 2-week Sprints. However, BigAgile is flexible and allows you to create Increments and Sprints of any duration.

Creating an Increment

You can create an Increment at any time by accessing the Admin view -> Increments -> + Button, and populating the following fields:

1. Add Increment Name: give your Increment a name.

💡Tip: We recommend using a simple convention, which will make it quick and easy to track and manage your Increments. We call ours 'PI-1; PI-2; PI-3...'

2. Select an Increment Status: There are 3 options here:

  • Planning means the Increment is in planning mode

  • Active means the Increment is in delivery mode

  • Complete means the Increment has finished

3. Connector: select the task management tool integration you would like to sync your Features and Teams with for this Increment.

4. Default Project ID: specify the key of the Jira Project you would like BigAgile to sync with as a default for this Increment.

💡Tip: This is typically a short abbreviation in capitals (e.g. ABC), which you can locate by logging into Jira-> Projects-> Search Project and finding the corresponding key in the 'Key' column.

5. Sprints: here, you can add Sprints to your Increment, give them names, and specify a time-frame for each sprint.

💡Tip: Remember the simple naming convention we used for our Increments? You can apply this to your Sprints too - e.g. there are 5 Sprints in our PI-6, so we call them 6.1, 6.2, 6.3, 6.4, and 6.5. Our Sprints for PI-5 are called 5.1, 5.2, 5.3...and so on)

💡Tip: When you add a Sprint, BigAgile will try help you name & timebox the next one by determining the name convention & matching the Sprint duration. For example, if you create a Sprint called 6.1 with a 2-week duration ending on 19/02, BigAgile will generate a name of 6.2 with a start date of 20/02 and a 2-week duration ... but you can override this.

6. Teams: this is where you will see all the teams comprised in the Increment. You have the ability to link each Team Sprint to Sprints in Jira or Iterations in Azure DevOps. Click on the 'Teams' button to assign your Jira/AzDo sprints to your BigAgile teams.

This screen is also where you are able to edit Sprints and Team Sprints.
​
Click 'Save and Post' to update your changes.

Did this answer your question?