Why us (for procurement department)

Why us (for procurement department)

What you're evaluating. A single Atlassian Marketplace app that consolidates delivery reporting, forecasting, and flow analytics - running natively on Atlassian's infrastructure, licensed through the Marketplace, and supporting all three Jira hosting models without forcing a migration.

Quick facts

 

 

 

 

Chart families

9

Delivery metrics

30+ (see full list below)

Pre-built templates

38

Atlassian products

Jira Software · Jira Product Discovery · Jira Service Management · Confluence

Hosting

Jira Cloud · Server 8.20.0 - 10.6.1 · Data Center 8.20.0 - 11.3.4

Marketplace rating

3.5 / 4

Trial

30 days, no credit card


30+ Delivery Metrics

Category

Metrics

Category

Metrics

Sprint tracking

Initial Commitment, Final Commitment, Added Work, Removed Work, Estimation Change, Not Completed Work, Rollover, Rollover Count, Issue Sprint Count, Total Scope Change, Individual Sprint Metrics

Flow analysis

Cycle Time, Lead Time, Time in Status (Absolute, Ratio, Average per Issue), Velocity / Throughput / Completed, Arrived / Created, Burnup / Departed / Resolved, Completion Rate, Work in Progress, Transition Count

Forecasting

Completed Work Date Forecast (When), How Many Until The Date, Forecast vs Projection

Delivery health

Say / Do Ratio, Benchmarking Sprint Metrics, Benchmarking Throughput

Scope & progress

Burndown / Remaining Work, Total Work, Ideal Slope, Initial Scope Slope, Epic Remaining Work Estimate


Commercial terms

 

 

 

 

Licensing model

User-tier licensing through the Atlassian Marketplace

Billing

Single invoice via Atlassian's standard billing cycle

Renewal

Annual or monthly via Atlassian, aligned to the existing Atlassian billing relationship

Trial

30 days, no credit card, installable directly from the Marketplace

Upgrade path

Standard Edition → Advanced Edition

Cancellation

Standard Atlassian Marketplace terms

External data processors

None - the app runs on Atlassian's infrastructure only

Additional integrations

None required - live against Jira data, no BI / ETL setup


Governance and assurance

image-20260511-141943.png
  • Runs on Atlassian - customer data remains on Atlassian's infrastructure; no external SaaS in the data path.

  • Cloud Fortified - meets Atlassian's elevated bar for reliability, scalability, security, and support.

  • SOC 2 compliant - audit-ready controls for security, availability, and confidentiality.

  • Data residency - aligned with Atlassian region controls (EU, US, AU tenancy).

  • Forge-native on Cloud - runs inside Atlassian's sandboxed execution environment. Same product on Cloud and Data Center; version support is maintained in line with Atlassian's lifecycle.

  • Audit trail - event-based Cycle and Lead Time rules are deterministic, transparent, and auditable against Jira workflow history.

  • Continuity on exit - no proprietary data store. Removing the app leaves all Jira data in place; reinstalling rebuilds charts from the same data.

  • Cross-product scope - one analytics engine across Jira Software, Jira Product Discovery, Jira Service Management, and Confluence.


Service model

  • Onboarding - 30-minute onboarding session included with every paid plan.

  • Support - Partner Support and Cloud Migration Support included.

  • Advanced edition - adds an Operational SLA with priority-queue routing, strategic enablement sessions, and hands-on Server/DC -> Cloud migration assistance with configuration alignment and data validation.


Proof

Product scale. 9 chart families, 30+ delivery metrics, 38 templates, one analytics engine across four Atlassian products.

Customer voice (anonymized)

"This is exactly the missing piece we needed - being able to see many teams on a single graph and switch between metrics without creating separate charts for each one." - Agile Coach at a Fortune-500 manufacturing enterprise (20+ teams, SAFe)

"Upper management is always asking about cycle-time outliers. We needed tools that let us investigate and show actionable trends, not just raw numbers." - Technical Program Manager at a mid-market SaaS company (8 Scrum teams)

"Different teams estimate story points differently, so we compare Velocity by percentage, not by absolute numbers. Being able to group statuses and break them down on demand is exactly what we needed to scale agile across teams." - Release Train Engineer at a scaled-agile enterprise (7 to 16 teams, Scrum at Scale)

 


Frequently asked questions

Who is the data processor? Atlassian. No third-party SaaS is involved in the data path.

Do we need an additional DPA with Broken Build? Atlassian's standard data processing agreement covers the data path. Broken Build's supplementary terms are published via the Marketplace listing.

Where is customer data stored? Where the customer's Atlassian tenancy resides - EU, US, or AU, depending on Atlassian region configuration.

What happens to our data if we remove the app? Underlying Jira data stays in place. Removing the app deletes gadget configurations only. Reinstalling rebuilds charts from the same data.

Is there a migration path from Data Center to Cloud? Yes. ARG runs on all three Jira hosting models. Advanced-edition customers receive hands-on Server/DC -> Cloud migration assistance.

[[FAQ: Add any procurement-specific questions raised in live RFPs - e.g., penetration-test evidence, GDPR DSR handling, full sub-processor list. Confirm authoritative answers with CS / CEO.]]


Next steps