Merge pull request #1 from arilivigni/pm-process-docs

Pm process docs

Author: arilivigni

.devcontainer/devcontainer.json

@@ -0,0 +1,31 @@
+{
+  "name": "Python 3",
+  "image": "mcr.microsoft.com/vscode/devcontainers/python:3.13",
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "GitHub.copilot",
+        "ms-python.python",
+        "ms-python.debugpy",
+        "ms-vscode.live-server",
+        "mechatroner.rainbow-csv"
+      ],
+      "settings": {
+        "livePreview.openPreviewTarget": "External Browser",
+        "chat.implicitContext.suggestedContext": false,
+
+        // These are defaults but keeping them here for clarity and explicitness
+        "github.copilot.chat.codeGeneration.useInstructionFiles": true,
+        "chat.promptFilesLocations": {
+          ".github/prompts": true
+        },
+        "chat.instructionsFilesLocations": {
+          ".github/instructions": true
+        },
+        "chat.modeFilesLocations": {
+          ".github/chatmodes": true
+        }
+      }
+    }
+  }
+}

.github/steps/1-step.md

@@ -1,27 +1,47 @@
-## Step 1: (replace-me: STEP-NAME)
+## Step 1: Create a Copilot Space
 
-(replace-me: OPTIONAL Brief story or scenario to introduce the step)
+You've just been hired as a project manager at OctoAcme, a growing tech company. Your team is struggling with scattered project management knowledge - processes are documented in different places, tribal knowledge exists only in people's heads, and new team members have trouble getting up to speed. You've heard about GitHub Copilot Spaces and want to use it to centralize and democratize your team's project management knowledge.
 
-### 📖 Theory: (replace-me: Theory title)
+### 📖 Theory: Understanding Copilot Spaces
 
-<!-- GitHub-styled notifications can be used outside of ordered lists. Available options are: NOTE, IMPORTANT, WARNING, TIP, CAUTION -->
-<!--
-> [!NOTE]
-> (Important note or additional information relevant to this section)
- -->
+GitHub Copilot Spaces is a collaborative workspace that allows you to ground Copilot's knowledge in your specific context. By creating a dedicated Space, you can:
+
+- **Centralize knowledge**: Bring together documentation, code, and processes in one place
+- **Add contextual sources**: Include repositories, documentation, and other resources that inform Copilot about your work
+- **Enable focused conversations**: Use Copilot with deep understanding of your specific domain and processes
+- **Scale expertise**: Make tribal knowledge accessible to everyone on your team
+
+Spaces help transform scattered information into an organized, searchable, and intelligent knowledge base that grows with your team.
 
-(replace-me: Optional theory or background information relevant to this step)
+### ⌨️ Activity: Create Your Project Management Copilot Space
+
+1. Navigate to GitHub Copilot Spaces in your GitHub account
+1. Click "Create new Space" or the equivalent option
+1. Name your Space: "OctoAcme Project Management Hub"
+1. Add a description: "Centralizing and democratizing project management knowledge for the OctoAcme team"
+1. Set the Space visibility according to your organization's policies
+1. Create the Space
+
+> [!NOTE]
+> If you don't have access to Copilot Spaces yet, you can simulate this step by taking notes on what you would include in your Space setup.
 
-### ⌨️ Activity: (replace-me: Activity title)
+### ⌨️ Activity: Add Source Repositories
 
-1. (replace-me: First instruction)
-1. (replace-me: Second instruction)
-1. (replace-me: Additional instructions as needed)
+1. In your newly created Copilot Space, look for "Sources" or "Add Source" section
+1. Add this exercise repository as a source:
+   - Repository URL: `https://github.com/<your-username>/<repo-name>`  
+     (Replace `<your-username>` with your GitHub username and `<repo-name>` with the name of your fork or copy of this repository. For example: `https://github.com/octocat/project-management-hub`)
+   - This gives Copilot access to the project management documentation and processes
+1. Wait for the repository to be indexed (this may take a few minutes)
+1. Verify the repository appears in your sources list
+1. (Optional) If you have other project management repositories or documentation, add them as additional sources
 
 <details>
 <summary>Having trouble? 🤷</summary><br/>
 
-- (replace-me: Troubleshooting tip or hint)
-- (replace-me: Additional troubleshooting tips as needed)
+- Make sure you have access to GitHub Copilot Spaces (currently in beta/limited access)
+- The repository should be publicly accessible for Copilot to index it
+- If you can't access Copilot Spaces, you can continue by manually exploring the repository structure and documentation
+- Repository indexing can take 5-10 minutes depending on size
 
 </details>

.github/steps/2-step.md

@@ -1,27 +1,41 @@
-## Step 2: (replace-me: STEP-NAME)
+## Step 2: Explain the Project Management process docs
 
-(replace-me: OPTIONAL Brief story or scenario to introduce the step)
+Now that you have the repository added as a source, it's time to explore OctoAcme's project management processes. All the documentation is stored in the `docs` folder, and you need to understand what processes are currently in place.
 
-### 📖 Theory: (replace-me: Theory title)
+### 📖 Theory: Process Documentation Analysis
 
-<!-- GitHub-styled notifications can be used outside of ordered lists. Available options are: NOTE, IMPORTANT, WARNING, TIP, CAUTION -->
-<!--
-> [!NOTE]
-> (Important note or additional information relevant to this section)
- -->
+Effective project management relies on well-documented, consistent processes. Documentation serves as the foundation for:
+- Onboarding new team members
+- Ensuring consistent execution across projects
+- Identifying gaps and improvement opportunities
+- Scaling practices across growing teams
 
-(replace-me: Optional theory or background information relevant to this step)
+When analyzing process documentation, look for:
+- Clear step-by-step procedures
+- Defined roles and responsibilities  
+- Decision-making frameworks
+- Communication protocols
+- Quality gates and checkpoints
 
-### ⌨️ Activity: (replace-me: Activity title)
+### ⌨️ Activity: Summarize Project Management Processes
 
-1. (replace-me: First instruction)
-1. (replace-me: Second instruction)
-1. (replace-me: Additional instructions as needed)
+1. Browse to the `docs` folder in this repository
+2. Review all the project management process documents
+3. Using GitHub Copilot (or manual analysis), create a comprehensive summary
+4. In the comments of this issue, provide a summary that includes:
+   - Overview of the current project management approach
+   - Key processes documented in the `docs/` folder
+   - Primary roles and responsibilities mentioned
+   - Any gaps or areas that seem unclear
+
+Your summary should be 3-4 paragraphs covering the main processes OctoAcme uses for project management.
 
 <details>
 <summary>Having trouble? 🤷</summary><br/>
 
-- (replace-me: Troubleshooting tip or hint)
-- (replace-me: Additional troubleshooting tips as needed)
+- Look for files like `project-lifecycle.md`, `roles-responsibilities.md`, `communication-plan.md` in the docs folder
+- Focus on understanding the overall workflow rather than memorizing every detail
+- If using Copilot, try asking: "Summarize the project management processes in the docs folder"
 
 </details>
+

.github/steps/3-step.md

@@ -1,27 +1,40 @@
-## Step 3: (replace-me: STEP-NAME)
+## Step 3: Add a chat mode project management process deep dive
 
-(replace-me: OPTIONAL Brief story or scenario to introduce the step)
+Time to create a specialized chat mode that will help you dive deeper into OctoAcme's project management processes. Custom chat modes allow you to focus Copilot's capabilities on specific topics and workflows.
 
-### 📖 Theory: (replace-me: Theory title)
+### 📖 Theory: Custom Chat Modes in Copilot Spaces
 
-<!-- GitHub-styled notifications can be used outside of ordered lists. Available options are: NOTE, IMPORTANT, WARNING, TIP, CAUTION -->
-<!--
-> [!NOTE]
-> (Important note or additional information relevant to this section)
- -->
+Custom chat modes are specialized conversation contexts that guide Copilot to focus on specific domains, use cases, or expertise areas. They work by:
+- Providing domain-specific context and vocabulary
+- Establishing conversation patterns and question types
+- Focusing responses on particular aspects of your work
+- Enabling more targeted and relevant assistance
 
-(replace-me: Optional theory or background information relevant to this step)
+For project management, a custom chat mode can help with:
+- Process analysis and improvement
+- Gap identification
+- Best practice recommendations
+- Role and responsibility clarification
 
-### ⌨️ Activity: (replace-me: Activity title)
+### ⌨️ Activity: Create and Use Project Management Deep Dive Chat Mode
 
-1. (replace-me: First instruction)
-1. (replace-me: Second instruction)
-1. (replace-me: Additional instructions as needed)
+1. Create a new file at `.github/chatmodes/project-management-deepdive.md`
+2. Add content that defines a chat mode focused on project management process analysis
+3. Use this custom chat mode to ask the following three questions:
+   - "Are there any gaps in the process?"
+   - "Suggest improvements to OctoAcme's project management process"
+   - "What other roles/personas should OctoAcme account for?"
+4. Document the responses in the comments of this issue
+5. Include insights about what the chat mode revealed about your processes
+
+> [!TIP]
+> If you can't create the actual chat mode, simulate the deep dive by manually analyzing the documentation and answering those three questions based on your review.
 
 <details>
 <summary>Having trouble? 🤷</summary><br/>
 
-- (replace-me: Troubleshooting tip or hint)
-- (replace-me: Additional troubleshooting tips as needed)
+- The chat mode file should include instructions for Copilot to focus on project management analysis
+- Think about what specific guidance would help someone analyze project management processes
+- Consider including context about OctoAcme's goals and constraints
 
 </details>

.github/steps/4-step.md

@@ -0,0 +1,46 @@
+## Step 4: Update the repository with new information
+
+Based on your analysis in the previous step, it's time to improve OctoAcme's project management processes. You'll update the repository with new information and improvements discovered through your Copilot Spaces deep dive.
+
+### 📖 Theory: Iterative Process Improvement
+
+Project management is inherently iterative. The best practices include:
+- Regular review and analysis of existing processes
+- Identifying gaps and improvement opportunities  
+- Implementing changes based on insights and feedback
+- Documenting improvements for team adoption
+- Measuring impact and continuing the cycle
+
+Effective process improvement involves:
+- **Analysis**: Understanding current state and identifying gaps
+- **Design**: Developing solutions and improvements
+- **Implementation**: Making changes and updating documentation
+- **Communication**: Ensuring team awareness and adoption
+
+### ⌨️ Activity: Implement Process Improvements
+
+Based on your analysis from Step 3, make improvements to the repository:
+
+1. Update existing files in the `docs/` folder to address identified gaps
+2. Add new documentation files for missing processes or roles
+3. Create or enhance process diagrams, templates, or checklists
+4. Ensure your changes reference the insights discovered in Step 3
+5. Commit your changes with a descriptive message that mentions "process improvements"
+
+Your updates should include at least:
+- One improvement to an existing process document
+- One new file addressing a gap you identified
+- Clear documentation of the changes made and why
+
+> [!IMPORTANT]
+> Make sure your commit message includes "process improvements" so the workflow can detect your changes.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Focus on the most impactful improvements identified in your analysis
+- Consider adding templates, checklists, or clarifying existing processes
+- Common improvements include: role clarification, communication protocols, decision-making frameworks
+- Even small improvements like adding examples or clarifying steps can be valuable
+
+</details>

.github/steps/x-review.md

@@ -1,16 +1,29 @@
 ## Review
 
-_Congratulations, you've completed this exercise and learned a lot about (replace-me: feature/product that was taught in this exercise)
+_Congratulations, you've completed this exercise and learned a lot about democratizing tribal knowledge using GitHub Copilot Spaces!_
 
 <img src="https://octodex.github.com/images/jetpacktocat.png" alt="celebrate" width=200 align=right>
 
 Here's a recap of your accomplishments:
 
-- (replace-me: Accomplishment #1)
-- (replace-me: Accomplishment #N)
+- **Set up a knowledge hub** by adding a repository as a source to Copilot Spaces
+- **Analyzed existing processes** by exploring and summarizing project management documentation
+- **Created specialized tooling** with custom chat modes for deep process analysis
+- **Implemented improvements** by updating documentation based on insights discovered
+- **Experienced the full cycle** of knowledge democratization: capture, analyze, improve, and share
+
+You've successfully used GitHub Copilot Spaces to transform tribal knowledge into accessible, improvable documentation that your entire team can benefit from. This approach scales beyond project management to any domain where knowledge needs to be captured and shared effectively.
 
 ### What's next?
 
-- (replace-me: Natural follow up Skills exercise - if there is one)
-- (replace-me: Documentation link to learn more about the feature)
-- (replace-me: Other resources or calls to action)
+- **Explore more chat modes**: Try creating specialized modes for different aspects of your work (code review, architecture decisions, etc.)
+- **Scale the approach**: Apply this pattern to other areas where your team has tribal knowledge
+- **Learn more about Copilot Spaces**: [GitHub Copilot Spaces Documentation](https://docs.github.com/en/copilot)
+- **Share with your team**: Introduce this workflow to help democratize knowledge across your organization
+
+### Key Takeaways
+
+- Copilot Spaces can serve as powerful knowledge management platforms
+- Custom chat modes enable focused, domain-specific assistance
+- Regular analysis and improvement of processes leads to better team outcomes
+- Documentation becomes more valuable when it's easily accessible and continuously improved

README.md

@@ -1,31 +1,31 @@
-# (replace-me: Exercise title)
+# Democratize Tribal Knowledge Using Copilot Spaces
 
-_(replace-me: One-line description of the exercise)_
+_Learn how to use GitHub Copilot Spaces to centralize and democratize project management knowledge within your team_
 
 ## Welcome
 
-- **Who is this for**: (replace-me: Target audience description)
-- **What you'll learn**: (replace-me: Learning objectives)
-- **What you'll build**: (replace-me: Description of what the learner will create)
+- **Who is this for**: Project managers, team leads, and developers looking to streamline knowledge sharing
+- **What you'll learn**: How to leverage GitHub Copilot Spaces to capture, organize, and improve project management processes
+- **What you'll build**: A comprehensive knowledge management system using Copilot Spaces with custom chat modes
 - **Prerequisites**:
-  - (replace-me: Prerequisite skill/exercise)
-  - (replace-me: Other prerequisites)
+  - Basic familiarity with GitHub repositories
+  - Access to GitHub Copilot Spaces
+  - Beginner-level project management concepts
 
-- **How long**: This exercise takes less than (replace-me: estimated time) to complete.
+- **How long**: This exercise takes less than 30 minutes to complete.
 
 In this exercise, you will:
 
-1. (replace-me: Learning objective step #1)
-1. (replace-me: Learning objective step #2)
-1. (replace-me: Learning objective step #N)
-
+1. Add a repository as a source to your Copilot Space
+2. Explore and summarize project management process documentation
+3. Create and use custom chat modes for deep process analysis
+4. Update repository documentation based on insights discovered
 
 ### How to start this exercise
 
 Simply copy the exercise to your account, then give your favorite Octocat (Mona) **about 20 seconds** to prepare the first lesson, then **refresh the page**.
 
-<!--  (replace-me: Make sure to edit the URL with proper template_owner, template_name, repo name and description)  -->
-[![](https://img.shields.io/badge/Copy%20Exercise-%E2%86%92-1f883d?style=for-the-badge&logo=github&labelColor=197935)](https://github.com/new?template_owner=skills&template_name=exercise-template&owner=%40me&name=skills-<replace-me>&description=Exercise:+Replace+me&visibility=public)
+[![](https://img.shields.io/badge/Copy%20Exercise-%E2%86%92-1f883d?style=for-the-badge&logo=github&labelColor=197935)](https://github.com/new?template_owner=arilivigni&template_name=democratize-tribal-knowledge-using-copilot-spaces&owner=%40me&name=democratize-tribal-knowledge-using-copilot-spaces&description=Exercise:+Democratize+Tribal+Knowledge+Using+Copilot+Spaces&visibility=public)
 
 <details>
 <summary>Having trouble? 🤷</summary><br/>

docs/octoacme-execution-and-tracking.md

@@ -0,0 +1,40 @@
+# OctoAcme — Execution & Tracking
+
+## Purpose
+Guidance for managing day-to-day execution and tracking progress toward project milestones.
+
+## Team Rhythm
+- Daily standups (15 min) — focus on progress, blockers, dependencies
+- Weekly delivery sync — show progress, updates, and flagged risks
+- Demo/Review at the end of each sprint or milestone
+
+## Workflows
+- Use the project board (e.g., GitHub Projects) with columns: Backlog, Ready, In Progress, In Review, QA, Done
+- Pull Request workflow:
+  - Small PRs (<= 400 lines when possible)
+  - Include issue link and acceptance criteria in PR description
+  - Run automated tests and linting in CI before requesting review
+  - Require at least one approval before merging (or team-defined policy)
+
+## Quality & Testing
+- Unit tests for new logic
+- Integration tests where applicable
+- End-to-end smoke tests for critical flows before release
+- Security scanning in CI
+- Manual QA for feature acceptance when needed
+
+## Reporting & Metrics
+- Track velocity and burndown
+- Monitor success metrics identified in the Project One-pager
+- Use dashboards for key signals (errors, latency, usage)
+
+## Blocker Escalation
+- Level 1: Team-level triage in daily standup
+- Level 2: PM escalates to Product Lead and dependent teams
+- Level 3: Sponsor-level escalation for business-impacting issues
+
+## Execution Checklist
+- [ ] Branching and PR conventions documented in repo
+- [ ] CI configured for tests and lint
+- [ ] Regular demos scheduled
+- [ ] Risk register updated weekly