{Misc.} Add scrum master's playbook #32627
Merged
+111
−0
Conversation
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
necusjz
requested review from
jiasli,
jsntcy,
kairu-ms and
yanzhudd
as code owners
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Collaborator
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds comprehensive documentation for the Azure CLI Scrum Master role by introducing a new playbook that outlines ongoing responsibilities and the release process workflow. The documentation includes detailed instructions for managing three phases of releases, monitoring CI pipelines, and coordinating with various teams.
Changes:
- Added "Scrum Master's Playbook" documentation with release process guidance
- Included supporting screenshot images (7 PNG files) for visual reference
Reviewed changes
Copilot reviewed 1 out of 20 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| doc/scrum-master's-playbook.md | Main playbook documentation covering Scrum Master responsibilities, release phases, and process workflows |
| doc/assets/phase2-7.png | Screenshot asset for Phase 2 Homebrew publishing step |
| doc/assets/phase2-6.png | Screenshot asset for Phase 2 email communication step |
| doc/assets/phase2-5.png | Screenshot asset for Phase 2 partner communication step |
| doc/assets/phase2-1.png | Screenshot asset for Phase 2 initial steps |
| doc/assets/batched-ci.png | Screenshot showing Batched CI monitoring interface |
| doc/assets/calendar-sample.png | Screenshot example of release meeting scheduling |
| doc/assets/phase1.5-*.png | Multiple screenshot assets for Phase 1.5 steps (7 images total) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
yanzhudd
approved these changes
Jan 14, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Related command
Description
Thanks to https://microsoftapc.sharepoint.com/:fl:/g/contentstorage/x8FNO-xtskuCRX2_fMTHLYQwOaSqoKBEi_kZgSAHMWs/IQBx-LHFpc1CQbVj_h96OOo9Ac4xqZ54HVpdTvaBsROqeR8?e=853yp2&nav=cz0lMkZjb250ZW50c3RvcmFnZSUyRng4Rk5PLXh0c2t1Q1JYMl9mTVRITFlRd09hU3FvS0JFaV9rWmdTQUhNV3MmZD1iJTIxbmNHNGFLV3pBa3VHcDlRR1RoMS1mYU96bFNVeVZtWkFzSHY0ZHkzdU92bHZJS0txZWt3T1JyRUhGa3ZtMTFiRiZmPTAxRElGNklIVFI3Q1k0TEpPTklKQTNLWTc2RDU1RFIyUjUmYz0lMkY%3D, made some minor optimizations based on that.
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.