Add engineering leadership demo: review throughput and backlog burn-down - #175
Open
devin-ai-integration[bot] wants to merge 2 commits into
Open
Add engineering leadership demo: review throughput and backlog burn-down#175devin-ai-integration[bot] wants to merge 2 commits into
devin-ai-integration[bot] wants to merge 2 commits into
Conversation
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
REVIEW.mdat the root ofotterworks,timesheet-app,eventflow-order-service, andpetclinic-angular(verified: none of the four has one onmaintoday), 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.services/api-gateway/internal/middleware/ratelimit.gowithratelimit_test.godeliberately left untouched, so the coverage-gap finding is the expected output. Followed by a cross-repo review-load report (docs/REVIEW_LOAD.md).services/document-service/app/api/comments.py, then a review finding handed back as a PR comment and fixed on the same branch..github/workflows/review-sweep.ymlstale-PR sweep (cron +workflow_dispatch, per-run session cap,needs-human-reviewescalation) built to follow the conventions of the repo's existingsast-auto-remediate.yml, plus a JiraReady for Dev+agent-readytransition automation with its payload spelled out.Also updates
catalog/field-kit-offerings.mddemo counts, which were stale before this change:(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'
mainbranches. Nodemos/README.mdexists, so none was created.Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/66e22b9d09e841aab72aab6b0666ac84