Agile approach means that, you will be using Story points to estimate your work (although you might still want to use the time tracking, if so check the Waterfall article), hence it is important to check if your Jira and BigPicture app are configured correctly and you have all the required data available.

Configure the app (requires Jira Administrator permissions)

  1. Start with the  section where you can define the mapping of your Jira issues to fields wich will determine the start and end dates of your work items. As you will be planning your work in sprints, there is no need to use dates at the task (Jira issue) level and you can select the '– Not synchronized --' options for start date and end date fields.
  1. In case, you are have already defined the dependencies between issues using your custom links or native Jira dependencies you can map the dependency link as a soft link in Technical configuration - Tasks - Link configuration. The agile dedicated modules do not use traditional end-start, end-end types of links, only the 'soft links'.
  2. In order to use the agile modules, you are required to create Teams so make sure to select a way to identify the assigned Team in Technical configuration - Modules - Resources . Using labels is more convenient as they can be generated automatically and you will not be required to predefine the select options.
  3. Another important sections is the Technical configuration - Security to grant permissions to users.
  4. Last step is to check if your Risk matrix matches your organization - change the field mapping or update the select options if required in Technical configuration - Modules - Risks. Select options can be changed in Jira Administration > Issues > Custom fields. The dimensions of the matrix can be changed by narrowing the select options.

Administration (requires app's admin permissions)

  1. Before you create your schedule there are a couple of more items which need to be configured summarised in Administration - Interface overview
  2. Your default Teams' capacity is derived from individual workload and holiday plans and the default values can be edited in Administration - Workload plans and Administration - Holiday plans. Please note, that you do not have to use those plans to calculate the capacity as you can always overwrite the defaults using the Board (at the iteration level only).
  3. If you are using Tempo apps, the above data should be already available - all you need to do is to synchronize with Tempo using BigPicture Enterprise (Integration with Tempo is not available on Jira Cloud).
  4. You are now ready to create your Program!

Create a Program Box

  1. Go to the Program manager and click the '+Add new Program' button. The Program Wizard will facilitate the process. Concept of a Program Box section explains how Program can be used with your Jira, long story short, a Program can be used to represent a your Products' and sprints' backlogs and all work already planned in sprints.
  2. If your project data is stored in Jira use the Program Wizard - Creating a new Program and a very important step is to define the Box schedule and WBS presets. Don't worry, you can do that later using the Overview- Hierarchy - Adding, editing and deleting boxes or by drag and drop using the Overview - Timeline.
  3. Last step is to create your program.

Working with a Program Box

  1. There are different modules which you can use depending on the methodology. You can change which modules are available in Program Box Configuration - General - Modules, at any time.
  2. Here is an example of how to manage your program starting with the Scope, Roadmap and Board modules. The most important settings to make your life easier and to automate your work include:
    1. The already mentioned Overview- Hierarchy - Adding, editing and deleting boxes - to define the iterations and Program Increments.
    2. Program Box configuration - Task - Task structure - generate the WBS of your Epics, Stories, and Tasks automatically (you can also use the presets .
    3. Program Box configuration - Board - Task card - select the fields which you would like to see on the card.

    4. Program box configuration - Board - Synchronization- map sprints to iterations.

    5. Board - Capacity planning - define the capacity of your Teams.
  3. Set the main goals for each sprint using the Roadmap module - Objective types and lifecycle.
  4. Now, using the Board module you can plan your sprints and inline edit your estimates if necessary - Board - Working with the Board. Customize your backlog - Board - Backlog - Tasks in Backlog to see the relevant information about your work items (e.g. Story points estimate, WSJB). Check the conflict indicated by red Board - Dependencies (Soft-links).

  5. Next step would be to identify and assess the risks using the Risks module.
  6. Use the Board - Reports to monitor the sprint execution and the work planned vs capacity.
  7. Use different modules to monitor program and to communicate with stakeholders. The following modules will help you to achieve that goal:
    1. Scope module - Interface overview,
    2. Reports module - Interface overview,
    3. Roadmap module - Interface overview,
    4. Risks module - Interface overview - Matrix.