Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/standards/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ This repository follows the **org-wide AzureLocal standards** maintained on the
|----------|-----------|------------------|
| Documentation | [Documentation Standards](documentation) | [Full Reference](https://azurelocal.cloud/standards/documentation/documentation-standards) |
| Repository Management | [Repository Management Standard](repository-management) | [Full Reference](https://azurelocal.cloud/standards/repository-management/) |
| Project Management | [Project Management](project-management) | [HCS Base Standard](https://platform.hybridsolutions.cloud/standards/project-management/) |
| Scripting | [Scripting Standards](scripting) | [Full Reference](https://azurelocal.cloud/standards/scripting/scripting-standards) |
| Variables | [Variable Standards](variables) | [Full Reference](https://azurelocal.cloud/standards/variable-management/) |
| Naming Conventions | [Naming Conventions](naming) | [Full Reference](https://azurelocal.cloud/standards/documentation/naming-conventions) |
Expand Down
34 changes: 34 additions & 0 deletions docs/standards/project-management.md
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

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Actually ignore generated PMO snapshots

The repository does not currently ignore this path: .gitignore contains no .artifacts rule, and git check-ignore .artifacts/pmo/test.json reports 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 👍 / 👎.

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/).
Loading