By role / Engineering

Engineering manager

ReportInSite for engineering managers

“What are our real cycle times, and how often do we deploy?”

Cycle time and the four DORA keys usually sit in different tools. ReportInSite takes the deployment, pull request, work item and change exports and reports them against your own targets.

The reports that answer it

Flow & DORA review

Cycle time, work item age, cumulative flow, throughput and the four DORA keys, with a flow & DORA review PDF.

Open it on sample data →

Steering scorecard

Targets on every metric, red / amber / green status, trends, and the steering pack and executive one-pager PDFs.

Open it on sample data →

Where the data usually comes from

These recipes are the usual starting points. Each one has export steps, a sample query and sample data to try first.

RecipeFeeds
Deployment Frequency report from GitHubDORA › Deployment Frequency
Lead Time for Changes report from GitHubDORA › Lead Time for Changes
Deployment Frequency report from GitLabDORA › Deployment Frequency
Deployment Frequency report from Azure PipelinesDORA › Deployment Frequency
Change Failure Rate report from ServiceNowDORA › Change Failure Rate
Time to Restore Service report from ServiceNowDORA › Time to Restore Service
Cycle Time (85th percentile) report from Azure DevOpsFlow › Cycle Time (85th percentile)
Cycle Time (85th percentile) report from LinearFlow › Cycle Time (85th percentile)
Cycle Time (85th percentile) report from JiraFlow › Cycle Time (85th percentile)
Test Pass Rate report from Azure Test Plans / TestRail / Xray / ZephyrQuality › Test Pass Rate

Anything else that exports a table works too, through the custom mapper or a Magic report. See all reports or Data from any app in the Playbook.

Your data stays with you

ReportInSite runs in your browser. Files are read on your device and reports are not uploaded. See Security & data.

Other roles

Free to start. Nothing to install.