-
Notifications
You must be signed in to change notification settings - Fork 0
Add the AzureLocal PMO board standard #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| --- | ||
| title: Project Management | ||
| description: AzureLocal rules for tracker-authoritative planning and reusable PMO boards. | ||
| --- | ||
|
|
||
| # Project Management | ||
|
|
||
| This page is the AzureLocal overlay for the HCS | ||
| [project-management standard](https://platform.hybridsolutions.cloud/standards/project-management/). | ||
| Only AzureLocal-specific differences are defined here. | ||
|
|
||
| ## Authoritative source | ||
|
|
||
| GitHub Issues and the AzureLocal organization Project are the primary intake and work-tracking | ||
| surfaces. Issues may synchronize into HCS Azure DevOps under the existing split-source rules, but | ||
| operators author and update GitHub-native issue data in GitHub. | ||
|
|
||
| The reusable PMO board is a read-only snapshot of those issues. It MUST NOT store browser edits or | ||
| write changes back to GitHub. Every displayed item links to its authoritative issue. | ||
|
|
||
| ## Scope selection | ||
|
|
||
| AzureLocal uses the per-repository project model unless `registry.yaml` explicitly assigns a | ||
| shared project. A board SHOULD represent one repository. A cross-repository portfolio board MAY | ||
| use the organization Project when its configuration names that scope explicitly. | ||
|
|
||
| ## Publication | ||
|
|
||
| Generated snapshots stay under ignored `.artifacts/pmo/`. Scheduled automation publishes an | ||
| authenticated workflow artifact. Claude or Codex publication remains owner-only or | ||
| workspace-restricted unless the repository owner explicitly approves public access. | ||
|
Comment on lines
+29
to
+31
|
||
|
|
||
| See also [Repository Management](repository-management.md) and the HCS | ||
| [work-item sync standard](https://platform.hybridsolutions.cloud/standards/work-item-sync/). | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The repository does not currently ignore this path:
.gitignorecontains no.artifactsrule, andgit check-ignore .artifacts/pmo/test.jsonreports it as unignored. When the documented board generator runs locally or in a checkout, its snapshots will therefore appear as untracked files and can be committed accidentally, contrary to this publication rule; add the corresponding ignore entry or remove the claim that the directory is ignored.Useful? React with 👍 / 👎.