Request demo

Release plans that keep up with the work.

Across runs the standup, keeps tickets current, and when a date slips, shows what moves and why.

Request a demo

release-4-2

  1. Sam Okafor

    API freeze is slipping to Wednesday. What moves in 4.2?

  2. Across

    I checked the 4.2 plan, three team boards, and the API calendar.

    Keep the commitments. Move the schema migration to 4.3.

  3. Sample release · 4.2

    Cut Friday
    • Orders schema migration DATA-208 · needs two days in staging Moves to 4.3
    • Bulk order edit DATA-214 · depends on the migration Moves to 4.3
    • Audit log export PLAT-390 · committed · ready Thursday Stays in 4.2

    Commitments unchanged. Owners review the replan.

    Replan sent to the platform and data leads.

    1. R-9 Schema migrations need two days in staging before the cut Data team runbook
    2. R-15 An item that moves takes its dependents with it Planning walkthrough
    3. R-4 Committed items keep their release unless product agrees Release policy, p. 2

Where a release breaks today.

The API freeze moves from Monday to Wednesday. Data and mobile work still start Tuesday, before the freeze, putting Friday’s release cut at risk.

The API freeze moves from Mon to Wed. The plan still starts Schema migration and SDK 3.1 build before the freeze.

1API freeze movesMon → Wed

2Dependents stay putData and Mobile still start Tue

3Release cut at risk4.2 cut: no replan yet

MonMTueTWedWThuTFriF
PlatformAPI freezeMon → Wed
DataSchema migrationStarts before the new freeze
MobileSDK 3.1 buildStarts before the new freeze
  1. MonThe freeze moves. The plan doesn’t.
  2. WedData lead hears at standup
  3. ThuBlocker raised, no context
  4. FriRisk shows up in the report

How Across replans this release.

Across rechecks every task that depends on the moved API freeze and applies your release rules. Here is release 4.2.

Release 4.2Cut Friday
Release 4.3Cut in two weeks

Platform

Release 4.2 · Cut Friday
PLAT-412API v2 freeze
Mon → Wed
PLAT-390Audit log export
R-4Committed · ready Thursday
PLAT-371SSO for admins
Committed
Release 4.3 · Cut in two weeks

Data

Release 4.2 · Cut Friday
Release 4.3 · Cut in two weeks
DATA-208Orders schema migration
R-9Moves to 4.3
DATA-214Bulk order edit
R-15Moves with DATA-208

Mobile

Release 4.2 · Cut Friday
MOB-77SDK 3.1
Builds Thursday
MOB-81Offline cart
Release 4.3 · Cut in two weeks

Replan drafted. Two items move to 4.3. Both commitments stay in 4.2. The platform and data leads review the replan.

Built from how you ship.

Much of how you ship lives with your leads, not in the tracker. The Architect reads your runbooks and past releases, then asks your leads about the gaps.

  1. Release calendar and policy, runbooks, past releases, and your leads’ answers.

    • Release calendar
    • Release policy
    • Team runbooks
    • Lead walkthroughs
    • Architect asks:What if an engineer is blocked for a day? Scrum lead answers:Tell the team lead, with the ticket and the blocker.

  2. The Architect drafts plain-language rules from those sources. Your engineering leads review them.

    • R-4 Release policy, p. 2 Committed items keep their release unless product agrees
    • R-9 Data team runbook Schema migrations need two days in staging before the cut
    • R-15 Planning walkthrough An item that moves takes its dependents with it
    • R-27 Scrum lead interview Blocked for a day: tell the team lead, with the ticket and the blocker

  3. A versioned graph that links each check to a draft change and an owner’s review.

    • Check Dependencies · Release rules · Commitments
    • Draft Revised cut · Owner notes · Ticket updates
    • Review Owners confirm · Product approves · Logged change

  4. The Operator catches rule changes. Past releases re-run before your team approves the change.

    • API freeze slips two days Replan drafted
    • Committed item at risk Sent to product
    • Ticket idle for a week Owner asked
    • Staging before the cut: was 2 days, now 1 day Past releases re-run ·Awaiting data lead approval

How we’ll measure the pilot.

Targets we agree with you before the build, scored on releases your leads already ran.

Every replan, ticket fix, and escalation records the rule and data behind it.

Apply a real rule change and re-run past releases without engineering work.

Questions to askCheck the answer against your own cases

Questions to ask any delivery AI.

  1. Does it know what isn’t in the tracker?

    Why it matters: Release rules, runbooks, and your leads’ judgment rarely live in tickets.

    Across: The rulebook is built from all of it, not just the board.

  2. Does it follow dependencies across teams?

    Why it matters: A slipped date usually breaks work on another team’s board.

    Across: It traces each dependency to the commitments it touches, across every board.

  3. Why it matters: Freeze windows and release rules change. Each change can’t become an engineering ticket.

    Across: Describe it in plain language. It’s tested on past releases and approved first.

    • Staging before the cut: 2 days to 1 day
    • DATA-208: moves to 4.3 to stays in 4.2
    • Past releases re-run , awaiting approval

  4. Does a person approve what it changes?

    Why it matters: A replan or a ticket fix changes someone else’s work.

    Across: It recommends. People approve the changes that count. Every write is tagged as Across and logged.

Start with a release that slipped.

A three-week pilot on your past releases, scoped to one program.

  1. Week 1
    • Release calendar, policy, and runbooks
    • Two or three past releases and the changes that hit them
    • Recorded walkthroughs with your leads
  2. Week 2
    • Writes the rulebook in plain language
    • Your engineering leads review it
    • Replays past changes through the workflow
  3. Week 3
    • Tested on held-out date changes
    • Your leads try it in a sandbox channel
    • Results against the agreed targets
  4. Your decision

    Use the results to decide whether to connect your tracker, calendars, and team channels.

What we need to start.

  • Release calendar Freezes, cuts, and maintenance windows
  • Release policy What counts as committed, and who can move it
  • Team runbooks Migration, testing, and rollout rules
  • Read access to boards Or exports, for the pilot program
  • Two or three past releases With the changes that hit them and what moved
  • Recorded walkthroughs With an engineering lead and a scrum lead
How it connectsPermissions, approvals, and your systems of record

Your tracker stays the record.

No new tool or ritual. Across reads your tracker under each person’s permissions, and a person approves anything sensitive.

Across
  1. Permissions Reads only what each person can see
  2. Sign-off A person approves anything sensitive
  3. Logged Every write is tagged as Across and recorded
  1. Ask in Slack, Teams, or Webex
  2. Read, under the user’s permissions Plan, boards, calendars
  3. Draft the replan back to the lead
  4. Update tickets, with sign-off where it matters, and log it
  1. ITCleared
  2. InfoSecCleared
  3. RiskCleared
  4. SOC 2Type II
  • Cleared by IT, InfoSec, and risk teams at a Fortune 100 technology company.
  • Runs in your cloud, containerized under your governance, or hosted by Across.
  • Runs on the models you approve and does not train on your data.
across / new run start here

Let us help you get work done.

Request a demo See customer stories