docs: update repository structure, add COO directories, and merge v2 proposal updates\n\n- Update main README.md repository structure to reflect current state\n- Remove context/ directory from databank as per new structure\n- Add COO sections to both databank/ and pmo/ directories\n- Create COO directories for transition to Albert\n- Add GLOSSARY.md template for project use\n- Update AGENTS.md to include COO transition information for Albert\n- Add rule requiring acronyms to be defined when first used\n- Add GLOSSARY requirement for all projects\n- Update PMO section to explain PMO (Project Management Office) acronym\n- Merge updates from PROPOSAL-AGENTS-v2.md into current AGENTS.md\n- Update version tracking in AGENTS.md to v8.0.0 reflecting COO changes\n- Add change tracking table to README.md\n- Reflect that project management artifacts stay local to projects with PMO linking to them\n- Update authority structure to include Albert's future role in COO transition
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
53
pmo/artifacts/projects/SAMPLE-001_DemoProject.md
Normal file
53
pmo/artifacts/projects/SAMPLE-001_DemoProject.md
Normal file
@@ -0,0 +1,53 @@
|
||||
# Sample Project: Demo Project
|
||||
|
||||
## Project Information
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| **Name** | Demo Project |
|
||||
| **ID** | SAMPLE-001 |
|
||||
| **Status** | Active |
|
||||
| **Priority** | Medium |
|
||||
| **Health** | Green |
|
||||
| **Last Updated** | 2025-10-24 10:00:00 |
|
||||
| **Tracking URL** | https://github.com/example/demo-project |
|
||||
| **Owner** | Project Owner |
|
||||
| **Dependencies** | None |
|
||||
| **Due Date** | 2025-12-31 |
|
||||
| **Progress** | 25% |
|
||||
| **Next Milestone** | Complete initial design phase |
|
||||
|
||||
## Project Details
|
||||
|
||||
### Description
|
||||
This is a sample project created to demonstrate the PMO project registry functionality. It serves as an example of how projects should be structured and tracked within the PMO system.
|
||||
|
||||
### Objectives
|
||||
- [x] Set up project structure
|
||||
- [ ] Complete initial design phase
|
||||
- [ ] Implement core features
|
||||
- [ ] Testing and validation
|
||||
- [ ] Project completion
|
||||
|
||||
### Milestones
|
||||
| Milestone | Target Date | Status |
|
||||
|-----------|-------------|--------|
|
||||
| Project Setup | 2025-10-20 | Completed |
|
||||
| Initial Design | 2025-11-15 | In Progress |
|
||||
| Feature Implementation | 2025-11-30 | Not Started |
|
||||
| Testing | 2025-12-15 | Not Started |
|
||||
| Project Completion | 2025-12-31 | Not Started |
|
||||
|
||||
### Resources
|
||||
- Team Members: Project Owner
|
||||
- Budget: $0 (Demo project)
|
||||
- Tools: GitHub, Documentation tools
|
||||
|
||||
### Risks
|
||||
| Risk | Impact | Mitigation Strategy |
|
||||
|------|--------|-------------------|
|
||||
| Scope creep | Medium | Clearly defined objectives and scope |
|
||||
| Resource availability | Low | Single owner, flexible timeline |
|
||||
|
||||
### Notes
|
||||
This is a demonstration project for the PMO system. It shows how projects should be documented and tracked according to the established schema.
|
||||
Reference in New Issue
Block a user