Skip to content

Add engineering leadership demo: review throughput and backlog burn-down - #175

Open
devin-ai-integration[bot] wants to merge 2 commits into
mainfrom
devin/1785183032-engineering-leadership-review-demo
Open

Add engineering leadership demo: review throughput and backlog burn-down#175
devin-ai-integration[bot] wants to merge 2 commits into
mainfrom
devin/1785183032-engineering-leadership-review-demo

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Summary

demos/ previously covered four job functions (data engineering, security, migration, application development). Engineering managers / delivery leads had nothing to watch. This adds that fifth category with one facilitator-led demo whose centerpiece is Devin Review as a standing reviewer across four repos, not a footnote step.

New file: demos/engineering-leadership/review-throughput-and-backlog-demo.md (579 lines, single linear thread, ToC with anchors, Key Takeaways).

The thread, in order:

  1. Write the review standard down — the demo's first step creates REVIEW.md at the root of otterworks, timesheet-app, eventflow-order-service, and petclinic-angular (verified: none of the four has one on main today), then promotes the cross-repo rules into a Knowledge note and a playbook source alongside the repo's existing .workshop/playbooks/synthetic-testdata-generation.devin.md. This is the management artifact the rest of the doc leans on, and it is inherently multi-repo work.
  2. Devin Review on a human PR — a real edit to services/api-gateway/internal/middleware/ratelimit.go with ratelimit_test.go deliberately left untouched, so the coverage-gap finding is the expected output. Followed by a cross-repo review-load report (docs/REVIEW_LOAD.md).
  3. The loop closes on an agent PR — pagination on services/document-service/app/api/comments.py, then a review finding handed back as a PR comment and fixed on the same branch.
  4. Backlog burn-down — triage into READY TO DELEGATE / NEEDS SPECIFICATION / HUMAN JUDGMENT, then six child sessions, six branches, six separate PRs, one ledger.
  5. Event-driven leg — a .github/workflows/review-sweep.yml stale-PR sweep (cron + workflow_dispatch, per-run session cap, needs-human-review escalation) built to follow the conventions of the repo's existing sast-auto-remediate.yml, plus a Jira Ready for Dev + agent-ready transition automation with its payload spelled out.
  6. Cost and capacity — ACU consumption shape per step and a delegate-vs-keep-human table. Figures are explicitly labeled illustrative.
  7. What Still Needs a Human — merge approval, production access, specification, prioritization, and the fact that review depth tracks how well a repo documents its conventions.

Also updates catalog/field-kit-offerings.md demo counts, which were stale before this change:

-| 4 | **Demos** | ... | 11 (3 categories) | ...
+| 4 | **Demos** | ... | 19 (5 categories) | ...

-11 showcases across data-engineering, migration, and security.
+19 showcases across application-development, data-engineering, engineering-leadership, migration, and security.

(The tree already held 18 demos against a documented count of 11; recounted rather than incremented.)

Every repo, path, workflow filename, Makefile target, service count, and line count in the doc was verified against the referenced repos' main branches. No demos/README.md exists, so none was created.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/66e22b9d09e841aab72aab6b0666ac84

@bsmitches bsmitches self-assigned this Jul 27, 2026
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant