---
title: "KB: Use case - 2026-09-29 – SUPPORT-272574"
canonical: "https://support.appfire.com/space/SUPPORT/3711827981/KB%3A%20Use%20case%20-%202026-09-29%20%E2%80%93%20SUPPORT-272574"
format: markdown
---
# Knowledge Base Article: Long-Term Scenario Planning in BigPicture

## Summary

This article covers multiple use cases for performing long-term, high-level visual planning and "what-if" modeling in BigPicture without cluttering the live Jira backlog. It addresses the needs of Project Managers who need to plan future work that is not yet committed or ready to be created as Jira issues.

## Use Case 1: Planning without Jira Issues (Basic Tasks)

**Problem/Context:**  
Product Owners or teams may want to keep the Jira backlog clean, limiting it only to committed work for the immediate future (e.g., one quarter ahead). Project Managers, however, need to visualize and plan for future phases that should not yet exist in Jira.

**Solution:**  
Use **Basic Tasks** in BigPicture. Basic tasks exist exclusively within the BigPicture database and are not synchronized with Jira.

- **Timeline & Hierarchy:** You can use them in the Gantt module to define timelines, dependencies, estimates, and hierarchies.
- **Conversion:** Once a future phase is approved and ready for execution, these basic tasks can be converted into standard Jira issues.
- **Reference:** [BigPicture Documentation - Basic Tasks](https://support.appfire.com/space/DLP/2211352313/Basic+tasks)

## Use Case 2: "What-If" Modeling (Scenario Mode)

**Problem/Context:**  
Project Managers need to simulate different planning outcomes or date shifts without affecting the live data in Jira.

**Solution:**  
Utilize **Scenario Mode** on the Gantt chart.

- **Simulation:** This mode allows you to create alternative planning scenarios.
- **Isolation:** You can simulate date shifts and dependency changes without pushing these updates to live Jira fields.
- **Merging:** Changes only affect the live Jira backlog if and when the scenario is explicitly merged.
- **Reference:** [BigPicture Documentation - Scenarios](https://support.appfire.com/space/SPM/1918634045/Scenarios)

## Use Case 3: High-Level Strategic Planning (Boxes & Goals)

**Problem/Context:**  
Organizations need to communicate operational targets and strategic alignment across agile timeboxes (like Program Increments or Sprints) without necessarily linking every item to a specific Jira issue immediately.

**Solution:**  
Structure planning using **Boxes** and the **Goals module**.

- **Hierarchy:** Use upper-level Boxes (e.g., *Portfolio → Program / Initiative → Stage / Iteration*) to organize work.
- **Target Tracking:** Use the Goals module to define, track, and communicate operational targets across these timeboxes.
- **Reference:** [BigPicture Documentation - Box Goals](https://support.appfire.com/space/SPM/1918797418/Box+goals+%28Goals+module%29)

---

**Note on Trial Extensions:**  
If you are evaluating these features and your trial has expired, please provide your **SEN (Support Entitlement Number)** or **Entitlement Number** to the support team to request an extension.

- [How to find the Entitlement Number (Cloud)](https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/2549612545)
- [How to find the SEN (Server/Data Center)](https://appfire.atlassian.net/wiki/x/voDiLQ)