e-volv

Planning playbook

SprintScopeDriftReport

Weekly comparison of current sprint tickets against the committed set, reporting unplanned additions and silently dropped work.

Weekly, compares the tickets currently in the sprint against the set committed at sprint start, surfaces what was added mid-sprint and by whom, what was silently dropped, and what grew in scope after work began, and reports the percentage of sprint capacity consumed by unplanned work with the trend across recent sprints.

Identifier
sprint-scope-drift-report
Version
1.0.0
Steps
4
Triggers
1
  • sprint
  • scope
  • drift
  • planning
  • report
  • automated

When it runs

Scheduleschedule.weekly
Schedule
Every Monday at 09:00 UTC 0 9 * * 1
Timezone
UTC

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

React Flow
  1. 01
    Weekly Schedule (Monday 09:00 UTC)trigger

    The event that starts the run.

  2. 02
    List Current Sprint Ticketsticket.list

    Queries the tracker for a set of tickets.

  3. 03
    Analyze Sprint Scope Driftagent.run

    One agent works the task with its toolkit.

  4. 04
    File Drift Report Ticketticket.create

    Opens a ticket on the connected tracker.

The agent

Sprint Scope Drift Analyst

Base type
Product Manager
Temperature
0.2
Max iterations
30
Tools
6

Tickets · 3

  • list_ticketsList Tickets · read
  • read_ticketRead Ticket · read
  • create_ticketCreate Ticket · write

Memory · 2

  • memory_writeWrite Memory · write
  • memory_readRead Memory · read

Status · 1

  • update_statusUpdate Status · write