In today’s heterogeneous agile software development environments, teams often have the autonomy to select the tool of their choice to track the daily activity of development efforts. One popular tool is Jira Software, Atlassian’s issue-tracking platform that supports both Scrum and Kanban at the team level.

A serious limitation of using Jira Software is that it does not offer native support for enterprise-wide agile methodologies such as SAFe.

The concepts of strategic themes, lean budgeting, portfolio epics, value streams and agile release trains are not built-in to Jira Software’s default work item hierarchy, which results in several challenges.

Even when combined with additional Plugins, Jira Software often lacks the ability to plan and track large-scale, complex work spanning multiple Agile Release Trains and lean portfolio management practices. Targetprocess, a software platform for enterprise agility, tackles these challenges with the following solutions.

Jira Software has no ability to capture strategic planning budget decisions (lean budgets) in a portfolio kanban, which is the basis for funding the value streams that make up the SAFe portfolio. This means that the SAFe based strategic planning and allocations are not linked to the tactical execution of the teams performing the work.

The work done at the team level may very well be tracked accurately, but there is no automated way to roll up this team-level progress and status to verify that the tactical execution work is aligned with the desired solution portfolio and the associated value streams and lean budget allocations.

With no automated way to aggregate program and portfolio level status information from dozens or hundreds of teams using Jira Software, release train and portfolio managers resort to building these reports manually. They are often depicted using powerpoint presentations or spreadsheets, where the data is derived from multiple team-level reports or weekly status updates.

Other organizations may use PPM-based time tracking systems to aggregate time-based estimates and time spent on work items as a proxy for measuring value delivery and forecasting progress towards milestones. In either case, there is no direct connection between portfolio, program and roadmap views and the status of day-to-day Feature/User Story execution data tracked in Jira Software, resulting in reports that are out of date before they are even distributed.

Before and during Program Increment (PI) planning, development teams refine high-level estimates, break work into manageable chunks and sequence it across multiple iterations and teams based on their capacity and expertise. During this process, teams need to understand, discuss and easily visualize relationships and dependencies across the planned work.

These dependencies need to be visible at multiple levels (portfolio, program and team) within the organization. Targetprocess provides interactive visualizations that depict dependencies spanning multiple programs, large solutions or complex portfolios of work.

Connecting Targetprocess to Jira Software allows you to visualize and manage dependencies, track estimates, and perform lean budgeting and strategic planning in Targetprocess, while managing team-level execution data in Jira Software.

This ensures that team-level execution data remains in-sync with strategy, providing an accurate picture of plans, progress and execution status across the enterprise.

Using Targetprocess as the “single source of truth” in this fashion will allow development teams to use Jira Software to track their day-to-day work and manage code and releases.

And business leaders and RTE’s can keep track of cross-team dependencies, Feature and Epic progress as well as steer the progress based on up-to-date portfolio metrics from within Targetprocess.

The trademarks for the products described on this page belong to their respective owners.

All information on the page is provided in good faith based on the capabilities of the products described as of March 1, 2020. The descriptions and viewpoints described by this page have not been reviewed or endorsed by Atlassian. We make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability or completeness of any information on the page.