Task Divergence Engine, Jira, Linear & GitHub

Ensure your sprint backlog actually reflects the contract you signed.

Every ticket and pull request is mapped to a contracted milestone. Work that maps to nothing is marked Scope Drift, with the nearest clause and an hour range, before the sprint commits to it.

Start free trial Explore the sandbox

Read-only by default. No per-developer metrics, ever.

SDL-SAAS sprint creep, last 6 sprints

Sundial Sprint 12 peaked at 21% after an admin import slipped in. Two signed change orders brought Sprint 14 back to 8%.

Sprint board overlay

Three tickets nobody quoted, in plain sight.

Toggle the overlay, select a Scope Drift ticket, and resolve it. Watch the sprint creep score move as tickets are mapped, marked in scope or queued for a change order.

HFX board/Sprint 14, 6 to 19 Nov

TWINJAM overlay

Sprint creep score

47%

Uncontracted points

21 / 45

3 unresolved drift tickets

Queued for change orders

0 pts

To do 4

In progress 2

In review 1

Done 2

Capabilities

Contract coverage for every ticket, issue and pull request.

GitHub PR Inspector

Reads pull request metadata, migration files and dependency manifests to catch uncontracted database schema expansions and new third-party services. The commercial conversation happens before merge, not after launch.

Migrations, new services and excluded SDKs
Source is processed in memory and never stored

agency/halvorsen-app, pull request 412

Add invoice paymentsOpen

package.json

+ "stripe": "^18.2.0",

db/migrations/0042_payments.sql

+ CREATE TABLE payments (

+ CREATE TABLE payment_methods (

Excluded by SOW § 7.3

Payment processing and PCI scope are excluded. Est. 40 to 56 h if built.

Sent to PM and delivery lead only. No comment posted on the PR.

Backlog Scope Audit

Flags tickets in Jira, Linear, Asana or ClickUp that do not map to an explicit SOW milestone, with the nearest clause and why it does not fit.

NRD-118Dark mode for marketing site§ 4.1 single theme
HFX-238Offline mode for depot scannersAppendix A online
CVN-77Homepage concepts, round 3§ 5.2 two rounds

Sprint Creep Score

A real-time ratio of contracted to uncontracted points in the active sprint, tracked sprint over sprint so delivery leads can see drift build before the budget shows it.

The formula

One number your sprint review can argue about productively.

Teams use the score in planning, not as a scorecard for people. Above 15%, most delivery leads pause new uncontracted tickets until a change order is signed.

sprint_creep_score =

points on unmapped tickets

total points in sprint

Under 10%: Healthy. Normal clarification work.
10 to 20%: Watch. Raise open flags in standup.
Over 20%: Act. Change order before more work.

FAQ

Questions PMs and founders ask

Not by default. The connection is read-only. If you opt in, TWINJAM can add a single scope-drift label or internal comment to flagged issues so your existing filters pick them up. It never changes status, assignee, estimates or sprint membership.

Story points (or estimates) in the active sprint on tickets that do not map to a contracted milestone, divided by total points in the sprint. Tickets resolved as in scope or mapped to a milestone drop out; tickets covered by a signed change order count as contracted from the moment of signature.

No. It reads PR metadata, changed file paths, migration files and dependency manifests to spot structural scope changes such as new tables or new third-party services. Flags go to the PM, not the PR author, and there are no per-developer metrics anywhere in TWINJAM.

That is the normal starting point. TWINJAM proposes a mapping from epics, Linear projects, labels and ticket text to SOW milestones after parsing the contract. A delivery lead confirms it once, and new tickets inherit it automatically.

More of the platform

Audit your current Jira backlog.

Connect one Jira or Linear project and one SOW during your 14-day free production trial. The first audit runs in minutes.

Start free trial Run a free SOW audit