Below you will find two charts that reflect the current and upcoming priorities for Biotics 6 and an estimated timeline for completing them. One chart is focused on the work that we plan to work on over the next few months and then below that is a larger project timeline. I have also included some definitions of some of our terminology and some additional information to better help you understand our current workplan.

In our Biotics 6 project, we use Jira to manage and track all the work being done by the team. To keep things structured and easy to follow, we break the work down into levels of detail:

At the highest level, we group our work into Deliverables. Each Deliverable represents a major outcome or goal we’re working toward. For example:

Think of Deliverables as the big-picture objectives we’re aiming to complete over the course of the project.

Within each Deliverable, we define a series of Epics—these are large chunks of work that represent key components or feature sets needed to achieve the Deliverable. For example, under Replicate Tracker Functionality, we have Epics like:

Epics are used to organize related work and help us understand what major features or functionality are required.

Each Epic is then broken down into individual issues, which we often refer to as tickets. These are the actionable items that developers, testers, and others work on daily:

These tickets are what team members work on directly.

As shown in the table above, we are attempting to map these Epics to timeframes, so we can visualize when each part of the work is expected to start and finish. Notes alongside each Epic help track dependencies and status (e.g., “waiting for spatial services,” “in progress,” or “pending UI work”).

The Biotics 6 project is a large and complex initiative with many interdependent components. While we’ve clearly defined our high-level Deliverables and grouped related work into Epics, many of these Epics do not yet have detailed Stories or Tasks written. This is intentional and expected at this stage of the project.

We are currently focused on planning and executing work within 1–2 deliverable cycles at a time (each cycle is roughly a month). This allows us to stay agile, focus on the most critical pieces, and avoid spending time scoping Epics that may shift based on dependencies or new discoveries.

As we progress:

Right now, it’s important to understand that timelines may shift as we learn more and finalize the scope of Epics. This is a normal part of complex software development, especially in projects with technical dependencies like spatial data services and legacy system replication.

Despite the unknowns, we’re making strong forward progress. Each cycle gives us better visibility, and we continue to de-risk the project by delivering incrementally.