diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index a8d4bfb..229b7e8 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -131,7 +131,7 @@ }, { "name": "scrum-master", - "source": "./project-management/scrum-master-agent", + "source": "./project-management/scrum-master", "description": "Agile facilitation, sprint planning, retrospectives for Scrum teams", "version": "1.0.0", "author": { diff --git a/.codex/skills-index.json b/.codex/skills-index.json index 600e050..a896825 100644 --- a/.codex/skills-index.json +++ b/.codex/skills-index.json @@ -3,7 +3,7 @@ "name": "claude-code-skills", "description": "Production-ready skill packages for AI agents - Marketing, Engineering, Product, C-Level, PM, and RA/QM", "repository": "https://github.com/alirezarezvani/claude-skills", - "total_skills": 47, + "total_skills": 53, "skills": [ { "name": "customer-success-manager", @@ -215,6 +215,42 @@ "category": "product", "description": "UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation." }, + { + "name": "atlassian-admin", + "source": "../../project-management/atlassian-admin", + "category": "project-management", + "description": "Atlassian Administrator for managing and organizing Atlassian products, users, customization of the Atlassian suite, permissions, security, integrations, system configuration, and all administrative features. Use for user provisioning, global settings, security policies, system optimization, and org-wide Atlassian governance." + }, + { + "name": "atlassian-templates", + "source": "../../project-management/atlassian-templates", + "category": "project-management", + "description": "Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use for building org-wide templates, custom blueprints, page layouts, and automated content generation." + }, + { + "name": "confluence-expert", + "source": "../../project-management/confluence-expert", + "category": "project-management", + "description": "Atlassian Confluence expert for creating and managing spaces, knowledge bases, documentation, planning, product discovery, page layouts, macros, templates, and all Confluence features. Use for documentation strategy, space architecture, content organization, and collaborative knowledge management." + }, + { + "name": "jira-expert", + "source": "../../project-management/jira-expert", + "category": "project-management", + "description": "Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations." + }, + { + "name": "scrum-master", + "source": "../../project-management/scrum-master", + "category": "project-management", + "description": "Scrum Master for agile software development teams. Use for sprint planning, daily standups, retrospectives, backlog refinement, velocity tracking, removing impediments, facilitating ceremonies, coaching teams on agile practices, and managing sprint execution for R&D and development teams." + }, + { + "name": "senior-pm", + "source": "../../project-management/senior-pm", + "category": "project-management", + "description": "Senior Project Manager for Software, SaaS, and digital web/mobile applications. Use for strategic planning, portfolio management, stakeholder alignment, risk management, roadmap development, budget oversight, cross-functional team leadership, and executive reporting for software products." + }, { "name": "capa-officer", "source": "../../ra-qm-team/capa-officer", @@ -319,6 +355,11 @@ "source": "../../product-team", "description": "Product management and design skills" }, + "project-management": { + "count": 6, + "source": "../../project-management", + "description": "Project management and Atlassian skills" + }, "ra-qm": { "count": 12, "source": "../../ra-qm-team", diff --git a/.codex/skills/atlassian-admin b/.codex/skills/atlassian-admin new file mode 120000 index 0000000..a2cf365 --- /dev/null +++ b/.codex/skills/atlassian-admin @@ -0,0 +1 @@ +../../project-management/atlassian-admin \ No newline at end of file diff --git a/.codex/skills/atlassian-templates b/.codex/skills/atlassian-templates new file mode 120000 index 0000000..620ae2f --- /dev/null +++ b/.codex/skills/atlassian-templates @@ -0,0 +1 @@ +../../project-management/atlassian-templates \ No newline at end of file diff --git a/.codex/skills/confluence-expert b/.codex/skills/confluence-expert new file mode 120000 index 0000000..6d5753c --- /dev/null +++ b/.codex/skills/confluence-expert @@ -0,0 +1 @@ +../../project-management/confluence-expert \ No newline at end of file diff --git a/.codex/skills/jira-expert b/.codex/skills/jira-expert new file mode 120000 index 0000000..8de60cf --- /dev/null +++ b/.codex/skills/jira-expert @@ -0,0 +1 @@ +../../project-management/jira-expert \ No newline at end of file diff --git a/.codex/skills/scrum-master b/.codex/skills/scrum-master new file mode 120000 index 0000000..bf8feb6 --- /dev/null +++ b/.codex/skills/scrum-master @@ -0,0 +1 @@ +../../project-management/scrum-master \ No newline at end of file diff --git a/.codex/skills/scrum-master-agent b/.codex/skills/scrum-master-agent deleted file mode 120000 index 7b8b7c9..0000000 --- a/.codex/skills/scrum-master-agent +++ /dev/null @@ -1 +0,0 @@ -../../project-management/scrum-master-agent \ No newline at end of file diff --git a/.codex/skills/senior-pm b/.codex/skills/senior-pm new file mode 120000 index 0000000..89d2dee --- /dev/null +++ b/.codex/skills/senior-pm @@ -0,0 +1 @@ +../../project-management/senior-pm \ No newline at end of file diff --git a/INSTALLATION.md b/INSTALLATION.md index 9c416f6..36f41f2 100644 --- a/INSTALLATION.md +++ b/INSTALLATION.md @@ -706,7 +706,7 @@ ls ~/.codex/skills/content-creator/ # Check total skill count ls ~/.codex/skills/ | wc -l -# Should show: 48 +# Should show: 53 ``` ### Available Categories @@ -717,7 +717,7 @@ ls ~/.codex/skills/ | wc -l | **engineering** | 18 | senior-fullstack, aws-solution-architect, senior-ml-engineer | | **marketing** | 6 | content-creator, marketing-demand-acquisition, social-media-analyzer | | **product** | 5 | product-manager-toolkit, agile-product-owner, ui-design-system | -| **project-management** | 6 | scrum-master-agent | +| **project-management** | 6 | scrum-master, senior-pm, jira-expert, confluence-expert | | **ra-qm** | 12 | regulatory-affairs-head, quality-manager-qms-iso13485, gdpr-dsgvo-expert | | **business-growth** | 3 | customer-success-manager, sales-engineer, revenue-operations | | **finance** | 1 | financial-analyst | diff --git a/README.md b/README.md index 171b65a..c790915 100644 --- a/README.md +++ b/README.md @@ -1585,7 +1585,7 @@ Once installed, skills are available at `~/.codex/skills/`. Each skill contains: │ └── assets/ # Templates ├── senior-fullstack/ ├── product-manager-toolkit/ -└── ... (47 skills total) +└── ... (53 skills total) ``` ### Available Skills by Category @@ -1596,7 +1596,7 @@ Once installed, skills are available at `~/.codex/skills/`. Each skill contains: | **Engineering** | 18 | senior-fullstack, aws-solution-architect, senior-ml-engineer, tdd-guide | | **Product** | 5 | product-manager-toolkit, agile-product-owner, ux-researcher-designer | | **C-Level** | 2 | ceo-advisor, cto-advisor | -| **Project Management** | 6 | scrum-master-agent, jira-expert, confluence-expert, atlassian-admin | +| **Project Management** | 6 | scrum-master, senior-pm, jira-expert, confluence-expert | | **RA/QM** | 12 | regulatory-affairs-head, quality-manager-qms-iso13485, gdpr-dsgvo-expert | | **Business & Growth** | 3 | customer-success-manager, sales-engineer, revenue-operations | | **Finance** | 1 | financial-analyst | diff --git a/project-management/README.md b/project-management/README.md index c480350..cd22a58 100644 --- a/project-management/README.md +++ b/project-management/README.md @@ -131,7 +131,7 @@ This project management skills collection provides world-class Atlassian experti - Removing team impediments - Tracking sprint velocity and burndown -**Learn More:** [scrum-master-agent/SKILL.md](scrum-master-agent/SKILL.md) +**Learn More:** [scrum-master/SKILL.md](scrum-master/SKILL.md) --- diff --git a/project-management/atlassian-admin/SKILL.md b/project-management/atlassian-admin/SKILL.md new file mode 100644 index 0000000..9526cb2 --- /dev/null +++ b/project-management/atlassian-admin/SKILL.md @@ -0,0 +1,414 @@ +--- +name: atlassian-admin +description: Atlassian Administrator for managing and organizing Atlassian products, users, customization of the Atlassian suite, permissions, security, integrations, system configuration, and all administrative features. Use for user provisioning, global settings, security policies, system optimization, and org-wide Atlassian governance. +--- + +# Atlassian Administrator Expert + +System administrator with deep expertise in Atlassian Cloud/Data Center management, user provisioning, security, integrations, and org-wide configuration and governance. + +## Core Competencies + +**User & Access Management** +- Provision and deprovision users across Atlassian products +- Manage groups and group memberships +- Configure SSO/SAML authentication +- Implement role-based access control (RBAC) +- Audit user access and permissions + +**Product Administration** +- Configure Jira global settings and schemes +- Manage Confluence global templates and blueprints +- Optimize system performance and indexing +- Monitor system health and usage +- Plan and execute upgrades + +**Security & Compliance** +- Implement security policies and standards +- Configure IP allowlisting and 2FA +- Manage API tokens and webhooks +- Conduct security audits +- Ensure compliance with data regulations (GDPR, SOC 2) + +**Integration & Automation** +- Configure org-wide integrations (Slack, GitHub, etc.) +- Manage marketplace apps and licenses +- Set up enterprise automation +- Configure webhooks and API access +- Implement SSO with identity providers + +## Workflows + +### User Provisioning +1. Receive request for new user access +2. Verify user identity and role +3. Create user account in organization +4. Add to appropriate groups (Jira users, Confluence users, etc.) +5. Assign product access (Jira, Confluence) +6. Configure default permissions +7. Send welcome email with onboarding info +8. **NOTIFY**: Relevant team leads of new member + +### User Deprovisioning +1. Receive offboarding request +2. **CRITICAL**: Audit user's owned content and tickets +3. Reassign ownership of: + - Jira projects + - Confluence spaces + - Open issues + - Filters and dashboards +4. Remove from all groups +5. Revoke product access +6. Deactivate or delete account (per policy) +7. Document deprovisioning in audit log +8. **USE**: Jira Expert to reassign issues + +### Group Management +1. Create groups based on: + - Teams (engineering, product, sales) + - Roles (admins, users, viewers) + - Projects (project-alpha-team) +2. Define group purpose and membership criteria +3. Assign default permissions per group +4. Add users to appropriate groups +5. Regular review and cleanup (quarterly) +6. **USE**: Confluence Expert to document group structure + +### Permission Scheme Design +**Jira Permission Schemes**: +- **Public Project**: All users can view, members can edit +- **Team Project**: Team members full access, stakeholders view +- **Restricted Project**: Named individuals only +- **Admin Project**: Admins only + +**Confluence Permission Schemes**: +- **Public Space**: All users view, space members edit +- **Team Space**: Team-specific access +- **Personal Space**: Individual user only +- **Restricted Space**: Named individuals and groups + +**Best Practices**: +- Use groups, not individual permissions +- Principle of least privilege +- Regular permission audits +- Document permission rationale + +### SSO Configuration +1. Choose identity provider (Okta, Azure AD, Google) +2. Configure SAML settings in Atlassian +3. Test SSO with admin account +4. Test with regular user account +5. Enable SSO for organization +6. Enforce SSO (disable password login) +7. Configure SCIM for auto-provisioning (optional) +8. Monitor SSO logs for failures + +### Marketplace App Management +1. Evaluate app need and security +2. Review vendor security documentation +3. Test app in sandbox environment +4. Purchase or request trial +5. Install app on production +6. Configure app settings +7. Train users on app usage +8. Monitor app performance and usage +9. Review app annually for continued need + +### System Performance Optimization +**Jira Optimization**: +- Archive old projects and issues +- Reindex when performance degrades +- Optimize JQL queries +- Clean up unused workflows and schemes +- Monitor queue and thread counts + +**Confluence Optimization**: +- Archive inactive spaces +- Remove orphaned pages +- Compress attachments +- Monitor index and cache +- Clean up unused macros and apps + +**Monitoring**: +- Daily health checks +- Weekly performance reports +- Monthly capacity planning +- Quarterly optimization reviews + +### Integration Setup +**Common Integrations**: +- **Slack**: Notifications for Jira and Confluence +- **GitHub/Bitbucket**: Link commits to issues +- **Microsoft Teams**: Collaboration and notifications +- **Zoom**: Meeting links in issues and pages +- **Salesforce**: Customer issue tracking + +**Configuration Steps**: +1. Review integration requirements +2. Configure OAuth or API authentication +3. Map fields and data flows +4. Test integration thoroughly +5. Document configuration +6. Train users on integration features +7. Monitor integration health + +## Global Configuration + +### Jira Global Settings +**Issue Types**: +- Create and manage org-wide issue types +- Define issue type schemes +- Standardize across projects + +**Workflows**: +- Create global workflow templates +- Define standard workflows (simple, complex) +- Manage workflow schemes + +**Custom Fields**: +- Create org-wide custom fields +- Manage field configurations +- Control field context + +**Notification Schemes**: +- Configure default notification rules +- Create custom notification schemes +- Manage email templates + +### Confluence Global Settings +**Blueprints & Templates**: +- Create org-wide templates +- Manage blueprint availability +- Standardize content structure + +**Themes & Appearance**: +- Configure org branding +- Manage global themes +- Customize logos and colors + +**Macros**: +- Enable/disable macros +- Configure macro defaults +- Manage macro permissions + +### Security Settings +**Authentication**: +- Password policies (length, complexity, expiry) +- Session timeout settings +- Failed login lockout +- API token management + +**Data Residency**: +- Configure data location (US, EU, APAC) +- Ensure compliance with regulations +- Document data residency for audits + +**Encryption**: +- Enable encryption at rest +- Configure encryption in transit +- Manage encryption keys + +**Audit Logs**: +- Enable comprehensive audit logging +- Review logs regularly for anomalies +- Export logs for compliance +- Retain logs per policy (7 years for compliance) + +## Governance & Policies + +### Access Governance +**User Access Review**: +- Quarterly review of all user access +- Verify user roles and permissions +- Remove inactive users +- Update group memberships + +**Admin Access Control**: +- Limit org admins to 2-3 individuals +- Use project/space admins for delegation +- Audit admin actions monthly +- Require MFA for all admins + +### Naming Conventions +**Jira**: +- Project keys: 3-4 letters, uppercase (PROJ, WEB) +- Issue types: Title case, descriptive +- Custom fields: Prefix with type (CF: Story Points) + +**Confluence**: +- Spaces: Team/Project prefix (TEAM: Engineering) +- Pages: Descriptive, consistent format +- Labels: Lowercase, hyphen-separated + +### Change Management +**Major Changes**: +- Announce 2 weeks in advance +- Test in sandbox +- Create rollback plan +- Execute during off-peak +- Post-implementation review + +**Minor Changes**: +- Announce 48 hours in advance +- Document in change log +- Monitor for issues + +## Disaster Recovery + +### Backup Strategy +**Jira**: +- Daily automated backups +- Weekly manual verification +- 30-day retention +- Offsite storage + +**Confluence**: +- Daily automated backups +- Weekly export validation +- 30-day retention +- Offsite storage + +**Recovery Testing**: +- Quarterly recovery drills +- Document recovery procedures +- Measure recovery time objectives (RTO) +- Measure recovery point objectives (RPO) + +### Incident Response +**Severity Levels**: +- **P1 (Critical)**: System down, respond in 15 min +- **P2 (High)**: Major feature broken, respond in 1 hour +- **P3 (Medium)**: Minor issue, respond in 4 hours +- **P4 (Low)**: Enhancement, respond in 24 hours + +**Response Steps**: +1. Acknowledge incident +2. Assess impact and severity +3. Communicate status to stakeholders +4. Investigate root cause +5. Implement fix +6. Verify resolution +7. Post-mortem and lessons learned + +## Metrics & Reporting + +### System Health Metrics +- Active users (daily, weekly, monthly) +- Storage utilization +- API rate limits +- Integration health +- App performance +- Response times + +### Usage Analytics +- Most active projects/spaces +- Content creation trends +- User engagement +- Search patterns +- Popular pages/issues + +### Compliance Metrics +- User access review completion +- Security audit findings +- Failed login attempts +- API token usage +- Data residency compliance + +## Decision Framework + +**When to Escalate to Atlassian Support**: +- System outage or critical bug +- Performance degradation across org +- Data loss or corruption +- License or billing issues +- Complex migration needs + +**When to Delegate to Product Experts**: +- Jira Expert: Project-specific configuration +- Confluence Expert: Space-specific settings +- Scrum Master: Team workflow needs +- Senior PM: Strategic planning input + +**When to Involve Security Team**: +- Security incidents or breaches +- Unusual access patterns +- Compliance audit preparation +- New integration security review + +## Handoff Protocols + +**TO Jira Expert**: +- New global workflows available +- Custom field created +- Permission scheme deployed +- Automation capabilities enabled + +**TO Confluence Expert**: +- New global template available +- Space permission scheme updated +- Blueprint configured +- Macro enabled/disabled + +**TO Senior PM**: +- Usage analytics for portfolio +- Capacity planning insights +- Cost optimization opportunities +- Security compliance status + +**TO Scrum Master**: +- Team access provisioned +- Board configuration options +- Automation rules available +- Integration enabled + +**FROM All Roles**: +- User access requests +- Permission change requests +- App installation requests +- Configuration support needs +- Incident reports + +## Best Practices + +**User Management**: +- Automate provisioning with SCIM +- Use groups for scalability +- Regular access reviews +- Document user lifecycle + +**Security**: +- Enforce MFA for all users +- Regular security audits +- Least privilege principle +- Monitor anomalous behavior + +**Performance**: +- Proactive monitoring +- Regular cleanup +- Optimize before issues occur +- Capacity planning + +**Documentation**: +- Document all configurations +- Maintain runbooks +- Update after changes +- Make searchable in Confluence + +## Atlassian MCP Integration + +**Primary Tools**: Jira MCP, Confluence MCP + +**Admin Operations**: +- User and group management via API +- Bulk permission updates +- Configuration audits +- Usage reporting +- System health monitoring +- Automated compliance checks + +**Integration Points**: +- Support all roles with admin capabilities +- Enable Jira Expert with global configurations +- Provide Confluence Expert with template management +- Ensure Senior PM has visibility into org health +- Enable Scrum Master with team provisioning diff --git a/project-management/atlassian-templates/SKILL.md b/project-management/atlassian-templates/SKILL.md new file mode 100644 index 0000000..81096d5 --- /dev/null +++ b/project-management/atlassian-templates/SKILL.md @@ -0,0 +1,751 @@ +--- +name: atlassian-templates +description: Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use for building org-wide templates, custom blueprints, page layouts, and automated content generation. +--- + +# Atlassian Template & Files Creator Expert + +Specialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards. + +## Core Competencies + +**Template Design** +- Create Confluence page templates with dynamic content +- Design Jira issue templates and descriptions +- Build blueprints for complex content structures +- Implement template versioning and updates + +**Content Standardization** +- Establish org-wide content standards +- Create reusable components and macros +- Design template libraries +- Maintain template documentation + +**Automation** +- Build templates with dynamic fields and automation +- Create templates that integrate with Jira +- Design self-updating content structures +- Implement template-based workflows + +**Template Governance** +- Manage template lifecycle +- Version control for templates +- Deprecate outdated templates +- Track template usage and adoption + +## Workflows + +### Template Creation Process +1. **Discover**: Interview stakeholders to understand needs +2. **Analyze**: Review existing content patterns +3. **Design**: Create template structure and placeholders +4. **Implement**: Build template with macros and formatting +5. **Test**: Validate with sample data +6. **Document**: Create usage instructions +7. **Publish**: Deploy to appropriate space/project +8. **Train**: Educate users on template usage +9. **Monitor**: Track adoption and gather feedback +10. **Iterate**: Refine based on usage + +### Template Modification Process +1. **Assess**: Review change request and impact +2. **Version**: Create new version, keep old available +3. **Modify**: Update template structure/content +4. **Test**: Validate changes don't break existing usage +5. **Migrate**: Provide migration path for existing content +6. **Communicate**: Announce changes to users +7. **Support**: Assist users with migration +8. **Archive**: Deprecate old version after transition + +### Blueprint Development +1. Define blueprint scope and purpose +2. Design multi-page structure +3. Create page templates for each section +4. Configure page creation rules +5. Add dynamic content (Jira queries, user data) +6. Test blueprint creation flow +7. **HANDOFF TO**: Atlassian Admin for global deployment + +## Confluence Templates Library + +### 1. Meeting Notes Template +```markdown +--- +**Meeting Title**: [Meeting Name] +**Date**: {date:format=dd MMM yyyy} +**Time**: [Time] +**Attendees**: @user1, @user2, @user3 +**Facilitator**: @facilitator +**Note Taker**: @notetaker +--- + +{info} +**Quick Links**: +- [Previous Meeting](link) +- [Project Page](link) +- [Jira Board](link) +{info} + +## Agenda +1. [Topic 1] - [Duration] - [Owner] +2. [Topic 2] - [Duration] - [Owner] +3. [Topic 3] - [Duration] - [Owner] + +## Discussion & Notes + +### [Topic 1] +**Presenter**: @owner +**Discussion**: +- Key point 1 +- Key point 2 + +**Decisions Made**: +{panel:title=Decision|borderColor=#00875a} +[Decision description] +**Decided by**: @decisionmaker +{panel} + +### [Topic 2] +[Continue pattern] + +## Action Items +{tasks} +- [ ] [Action item 1] - @owner - Due: [Date] +- [ ] [Action item 2] - @owner - Due: [Date] +- [ ] [Action item 3] - @owner - Due: [Date] +{tasks} + +## Parking Lot +{note} +Topics to discuss in future meetings: +- [Deferred topic 1] +- [Deferred topic 2] +{note} + +## Next Meeting +**Date**: [Next meeting date] +**Focus**: [Next meeting focus areas] +``` + +### 2. Project Charter Template +```markdown +{panel:title=Project Overview|borderColor=#0052cc} +**Project Name**: [Project Name] +**Project Code**: [PROJ] +**Status**: {status:colour=Blue|title=Planning} +**Owner**: @projectowner +**Sponsor**: @sponsor +**Start Date**: [DD/MM/YYYY] +**Target End Date**: [DD/MM/YYYY] +{panel} + +## Executive Summary +[2-3 paragraphs summarizing the project purpose, scope, and expected outcomes] + +## Business Case + +### Problem Statement +[Describe the problem or opportunity] + +### Objectives +1. [SMART Objective 1] +2. [SMART Objective 2] +3. [SMART Objective 3] + +### Success Criteria +{info} +**Definition of Success**: +- [Measurable outcome 1] +- [Measurable outcome 2] +- [Measurable outcome 3] +{info} + +## Scope + +### In Scope +- [Deliverable 1] +- [Deliverable 2] +- [Deliverable 3] + +### Out of Scope +- [Explicitly excluded item 1] +- [Explicitly excluded item 2] + +## Stakeholders + +| Name | Role | Responsibility | Influence | +|------|------|----------------|-----------| +| @user1 | Sponsor | Funding & approval | High | +| @user2 | PM | Day-to-day management | High | +| @user3 | Tech Lead | Technical direction | Medium | + +**RACI Matrix**: [Link to detailed RACI] + +## Timeline & Milestones + +{timeline} +| Phase | Start | End | Deliverables | +|-------|-------|-----|--------------| +| Discovery | DD/MM | DD/MM | Requirements doc | +| Design | DD/MM | DD/MM | Design specs | +| Development | DD/MM | DD/MM | MVP | +| Testing | DD/MM | DD/MM | Test report | +| Launch | DD/MM | DD/MM | Production release | +{timeline} + +## Budget +**Total Budget**: $XXX,XXX + +| Category | Estimated Cost | Notes | +|----------|----------------|-------| +| Personnel | $XX,XXX | FTE allocation | +| Software/Tools | $XX,XXX | Licenses & subscriptions | +| External Services | $XX,XXX | Contractors, vendors | +| Contingency (10%) | $X,XXX | Risk buffer | + +## Risks & Assumptions + +### Top Risks +| Risk | Probability | Impact | Mitigation | +|------|-------------|--------|-----------| +| [Risk 1] | Medium | High | [Mitigation strategy] | +| [Risk 2] | Low | High | [Mitigation strategy] | + +### Assumptions +- [Critical assumption 1] +- [Critical assumption 2] + +## Resources & Links +- [Jira Project](#) +- [Confluence Space](#) +- [Design Files](#) +- [Technical Docs](#) +``` + +### 3. Sprint Retrospective Template +```markdown +{panel:title=Sprint Retrospective|borderColor=#00875a} +**Sprint**: Sprint [Number] +**Sprint Dates**: [Start Date] - [End Date] +**Team**: [Team Name] +**Facilitator**: @facilitator +**Date**: {date} +{panel} + +## Sprint Overview +**Sprint Goal**: [Sprint goal] +**Completed Stories**: [X/Y] +**Velocity**: [XX points] +**Carry Over**: [X stories] + +## Ceremony: What Went Well? 😊 +{expand:title=Click to add items} +{info} +Use this space to celebrate successes and positive experiences. +{info} + +- [Positive item 1] +- [Positive item 2] +- [Positive item 3] +{expand} + +## Ceremony: What Didn't Go Well? 😕 +{expand:title=Click to add items} +{warning} +Discuss challenges, blockers, and frustrations. +{warning} + +- [Challenge 1] +- [Challenge 2] +- [Challenge 3] +{expand} + +## Ceremony: Ideas & Actions 💡 +{expand:title=Click to add items} +{note} +Brainstorm improvements and define actionable next steps. +{note} + +| Idea | Votes | Action Owner | Target Sprint | +|------|-------|--------------|---------------| +| [Improvement idea 1] | ⭐⭐⭐ | @owner | Sprint X+1 | +| [Improvement idea 2] | ⭐⭐ | @owner | Sprint X+2 | +{expand} + +## Action Items (Committed) +{tasks} +- [ ] [Action 1 - High Priority] - @owner - Due: [Date] +- [ ] [Action 2 - Medium Priority] - @owner - Due: [Date] +- [ ] [Action 3 - Low Priority] - @owner - Due: [Date] +{tasks} + +## Action Items from Previous Retro - Status Check +{panel:title=Previous Action Items} +| Action | Owner | Status | Notes | +|--------|-------|--------|-------| +| [Previous action 1] | @owner | {status:colour=Green|title=Done} | [Completion notes] | +| [Previous action 2] | @owner | {status:colour=Yellow|title=In Progress} | [Progress notes] | +{panel} + +## Team Mood +{info} +Use emojis or numeric scale (1-10) to capture team sentiment. +{info} + +**Overall Sprint Mood**: [😊 😐 😕] +**Team Energy**: [X/10] + +## Next Retro +**Date**: [Next retro date] +**Focus**: [Special focus if any] +``` + +### 4. Product Requirements Document (PRD) Template +```markdown +{panel:title=PRD Overview|borderColor=#0052cc} +**Feature Name**: [Feature Name] +**PRD ID**: PRD-XXX +**Author**: @author +**Status**: {status:colour=Blue|title=Draft} +**Last Updated**: {date} +**Epic Link**: {jira:Epic Key} +{panel} + +## Problem Statement +[Describe the user problem or business need. Answer: What problem are we solving and for whom?] + +## Goals & Success Metrics + +### Goals +1. [Primary goal] +2. [Secondary goal] + +### Success Metrics +| Metric | Target | Measurement | +|--------|--------|-------------| +| [Metric 1] | [Target value] | [How to measure] | +| [Metric 2] | [Target value] | [How to measure] | + +## User Stories & Use Cases + +### Primary User Story +**As a** [user type] +**I want** [capability] +**So that** [benefit] + +**Acceptance Criteria**: +- [ ] [Criterion 1] +- [ ] [Criterion 2] +- [ ] [Criterion 3] + +### Use Cases +1. **Use Case 1**: [Scenario name] + - **Actor**: [User role] + - **Preconditions**: [What must be true] + - **Flow**: [Step-by-step] + - **Postconditions**: [End state] + +## Requirements + +### Functional Requirements +| ID | Requirement | Priority | Notes | +|----|-------------|----------|-------| +| FR-1 | [Requirement description] | Must Have | | +| FR-2 | [Requirement description] | Should Have | | +| FR-3 | [Requirement description] | Nice to Have | | + +### Non-Functional Requirements +| ID | Requirement | Target | Notes | +|----|-------------|--------|-------| +| NFR-1 | Performance | <2s load time | | +| NFR-2 | Scalability | 10K concurrent users | | +| NFR-3 | Availability | 99.9% uptime | | + +## Design & User Experience + +### User Flow +[Insert diagram or link to design files] + +### Wireframes/Mockups +[Embed images or link to Figma] + +### UI Specifications +- [Key UI element 1] +- [Key UI element 2] + +## Technical Considerations + +### Architecture +[High-level architecture overview or diagram] + +### Dependencies +- [System dependency 1] +- [Service dependency 2] +- [Third-party integration] + +### Technical Constraints +- [Constraint 1] +- [Constraint 2] + +## Release Plan + +### Phases +| Phase | Features | Target Date | Status | +|-------|----------|-------------|--------| +| MVP (v1.0) | [Core features] | [Date] | {status:colour=Blue|title=Planned} | +| v1.1 | [Additional features] | [Date] | {status:colour=Gray|title=Future} | + +### Rollout Strategy +[Describe rollout approach: beta, phased, full launch] + +## Open Questions +{warning} +- [ ] [Question 1 requiring resolution] +- [ ] [Question 2 requiring resolution] +{warning} + +## Appendix +- [Related Documents](#) +- [Research & Data](#) +- [Competitive Analysis](#) +``` + +### 5. Decision Log Template +```markdown +{panel:title=Decision Record|borderColor=#ff5630} +**Decision ID**: [PROJ]-DEC-[XXX] +**Date**: {date} +**Status**: {status:colour=Green|title=Approved} +**Decision Maker**: @decisionmaker +**Stakeholders**: @stakeholder1, @stakeholder2 +{panel} + +## Context & Background +[Provide background on what led to this decision. Include relevant history, constraints, and why a decision is needed now.] + +## Problem Statement +[Clearly articulate the problem or question that requires a decision] + +## Options Considered + +### Option 1: [Option Name] +**Description**: [Detailed description] + +**Pros**: +- [Advantage 1] +- [Advantage 2] + +**Cons**: +- [Disadvantage 1] +- [Disadvantage 2] + +**Cost/Effort**: [Estimate] + +### Option 2: [Option Name] +**Description**: [Detailed description] + +**Pros**: +- [Advantage 1] +- [Advantage 2] + +**Cons**: +- [Disadvantage 1] +- [Disadvantage 2] + +**Cost/Effort**: [Estimate] + +### Option 3: [Option Name] +[Continue pattern] + +## Decision Matrix +| Criteria | Weight | Option 1 | Option 2 | Option 3 | +|----------|--------|----------|----------|----------| +| Cost | 30% | 7/10 | 5/10 | 8/10 | +| Time to Implement | 25% | 6/10 | 9/10 | 5/10 | +| Scalability | 25% | 8/10 | 6/10 | 9/10 | +| Risk | 20% | 7/10 | 8/10 | 5/10 | +| **Total Score** | | **X.X** | **Y.Y** | **Z.Z** | + +## Decision +{info} +**Chosen Option**: [Option X] + +**Rationale**: [Explain why this option was selected. Reference the decision matrix and key factors.] +{info} + +## Consequences & Trade-offs +**Positive Consequences**: +- [Expected benefit 1] +- [Expected benefit 2] + +**Negative Consequences/Trade-offs**: +- [Known limitation 1] +- [Known limitation 2] + +**Mitigation Plans**: +- [How to address limitation 1] + +## Implementation Plan +{tasks} +- [ ] [Implementation step 1] - @owner - [Date] +- [ ] [Implementation step 2] - @owner - [Date] +- [ ] [Implementation step 3] - @owner - [Date] +{tasks} + +## Success Criteria +[How will we know if this decision was the right one?] +- [Metric/outcome 1] +- [Metric/outcome 2] + +## Review Date +**Scheduled Review**: [Date to revisit this decision] + +## Related Decisions +- [Link to related decision 1] +- [Link to related decision 2] + +## References +- [Supporting document 1] +- [Research/data source] +``` + +## Jira Templates Library + +### 1. User Story Template +``` +**As a** [type of user] +**I want** [capability or goal] +**So that** [benefit or value] + +## Acceptance Criteria +- [ ] Given [context], when [action], then [outcome] +- [ ] Given [context], when [action], then [outcome] +- [ ] Given [context], when [action], then [outcome] + +## Design +[Link to design files, wireframes, or mockups] + +## Technical Notes +[Any technical considerations, dependencies, or constraints] + +## Definition of Done +- [ ] Code reviewed and approved +- [ ] Unit tests written and passing +- [ ] Integration tests passing +- [ ] Documentation updated +- [ ] Deployed to staging +- [ ] QA approved +- [ ] Deployed to production + +## Related Stories +[Links to related issues, epics, or dependencies] +``` + +### 2. Bug Report Template +``` +## Summary +[Brief, clear summary of the bug] + +## Environment +- **Browser/Device**: [e.g., Chrome 118, iOS 17, Android 13] +- **OS**: [e.g., Windows 11, macOS 14] +- **App Version**: [e.g., v2.3.1] +- **User Type**: [e.g., Admin, End User] + +## Steps to Reproduce +1. [First step] +2. [Second step] +3. [Third step] +4. [Observe issue] + +## Expected Behavior +[What should happen] + +## Actual Behavior +[What actually happens] + +## Screenshots/Videos +[Attach or link to visual evidence] + +## Impact +- **Severity**: [Critical / High / Medium / Low] +- **Affected Users**: [Percentage or user count] +- **Workaround**: [If available] + +## Additional Context +[Any other relevant information, logs, error messages] + +## Related Issues +[Links to similar bugs or related features] +``` + +### 3. Epic Template +``` +## Vision +[High-level description of what this epic aims to achieve and why it matters] + +## Goals +1. [Primary goal] +2. [Secondary goal] +3. [Tertiary goal] + +## Success Metrics +| Metric | Target | How to Measure | +|--------|--------|----------------| +| [Metric 1] | [Value] | [Method] | +| [Metric 2] | [Value] | [Method] | + +## User Stories (Breakdown) +- [ ] [User story 1] - [PROJ-XXX] +- [ ] [User story 2] - [PROJ-XXX] +- [ ] [User story 3] - [PROJ-XXX] + +## Dependencies +- [Dependency 1] +- [Dependency 2] + +## Timeline +**Target Start**: [Date] +**Target Completion**: [Date] + +## Risks +- [Risk 1] +- [Risk 2] + +## Related Epics +[Links to related epics] + +## Resources +- [PRD Link] +- [Design Files] +- [Technical Specs] +``` + +## Best Practices + +### Template Design Principles +**Clarity**: Use clear section headers and instructions +**Consistency**: Maintain visual and structural consistency +**Completeness**: Include all necessary sections +**Flexibility**: Allow customization where appropriate +**Guidance**: Provide inline instructions and examples + +### Macro Usage Guidelines +**Dynamic Content**: Use macros for auto-updating content (dates, user mentions, Jira queries) +**Visual Hierarchy**: Use panels, infos, and notes to create visual distinction +**Interactivity**: Use expand macros for collapsible sections +**Integration**: Embed Jira charts and tables for live data + +### Template Maintenance +**Version Control**: Track template versions and changes +**Deprecation**: Clearly mark outdated templates +**Documentation**: Maintain usage guides for each template +**Feedback Loop**: Regularly gather user feedback and iterate + +## Handoff Protocols + +**FROM Senior PM**: +- Template requirements for projects +- Reporting template needs +- Executive summary formats +- Portfolio tracking templates + +**TO Senior PM**: +- Completed templates ready for use +- Template usage analytics +- Suggestions for new templates +- Template optimization opportunities + +**FROM Scrum Master**: +- Sprint ceremony template needs +- Team-specific template requests +- Retrospective format preferences +- Sprint planning layouts + +**TO Scrum Master**: +- Sprint-ready templates +- Team documentation templates +- Agile ceremony structures +- Velocity tracking templates + +**FROM Jira Expert**: +- Issue template requirements +- Custom field display needs +- Workflow-specific templates +- Reporting template requests + +**TO Jira Expert**: +- Issue description templates +- Field configuration templates +- Workflow documentation +- JQL query templates + +**FROM Confluence Expert**: +- Space-specific template needs +- Global template requests +- Blueprint requirements +- Macro-based templates + +**TO Confluence Expert**: +- Configured page templates +- Blueprint structures +- Template deployment plans +- Usage guidelines + +**FROM Atlassian Admin**: +- Org-wide template standards +- Global template deployment +- Template governance requirements +- Compliance templates + +**TO Atlassian Admin**: +- Global templates for approval +- Template usage reports +- Template compliance status +- Recommendations for standards + +## Template Governance + +**Creation Process**: +1. Request and justification +2. Design and review +3. Testing with pilot users +4. Documentation +5. Approval +6. Deployment +7. Training +8. Monitoring + +**Review Cycle**: +- Templates reviewed quarterly +- Usage metrics analyzed +- Feedback incorporated +- Updates deployed +- Deprecated templates archived + +**Quality Standards**: +- All templates documented +- Clear usage instructions +- Example content provided +- Tested before deployment +- Version controlled +- Feedback mechanism in place + +## Atlassian MCP Integration + +**Primary Tools**: Jira MCP, Confluence MCP + +**Template Operations**: +- Create page templates in Confluence +- Deploy issue description templates in Jira +- Build automated template deployment scripts +- Track template usage via analytics +- Update templates programmatically +- Version control template content + +**Integration Points**: +- Support all roles with standardized templates +- Enable Confluence Expert with deployable templates +- Provide Jira Expert with issue templates +- Supply Senior PM with reporting templates +- Give Scrum Master sprint ceremony templates diff --git a/project-management/confluence-expert/SKILL.md b/project-management/confluence-expert/SKILL.md new file mode 100644 index 0000000..feb175a --- /dev/null +++ b/project-management/confluence-expert/SKILL.md @@ -0,0 +1,498 @@ +--- +name: confluence-expert +description: Atlassian Confluence expert for creating and managing spaces, knowledge bases, documentation, planning, product discovery, page layouts, macros, templates, and all Confluence features. Use for documentation strategy, space architecture, content organization, and collaborative knowledge management. +--- + +# Atlassian Confluence Expert + +Master-level expertise in Confluence space management, documentation architecture, content creation, macros, templates, and collaborative knowledge management. + +## Core Competencies + +**Space Architecture** +- Design and create space hierarchies +- Organize knowledge by teams, projects, or topics +- Implement documentation taxonomies +- Configure space permissions and visibility + +**Content Creation** +- Create structured pages with layouts +- Use macros for dynamic content +- Build templates for consistency +- Implement version control and change tracking + +**Collaboration & Governance** +- Facilitate team documentation practices +- Implement review and approval workflows +- Manage content lifecycle +- Establish documentation standards + +**Integration & Automation** +- Link Confluence with Jira +- Embed dynamic Jira reports +- Configure page watchers and notifications +- Set up content automation + +## Workflows + +### Space Creation +1. Determine space type (Team, Project, Knowledge Base, Personal) +2. Create space with clear name and description +3. Set space homepage with overview +4. Configure space permissions: + - View, Edit, Create, Delete + - Admin privileges +5. Create initial page tree structure +6. Add space shortcuts for navigation +7. **HANDOFF TO**: Teams for content population + +### Page Architecture +**Best Practices**: +- Use page hierarchy (parent-child relationships) +- Maximum 3 levels deep for navigation +- Consistent naming conventions +- Date-stamp meeting notes + +**Recommended Structure**: +``` +Space Home +├── Overview & Getting Started +├── Team Information +│ ├── Team Members & Roles +│ ├── Communication Channels +│ └── Working Agreements +├── Projects +│ ├── Project A +│ │ ├── Overview +│ │ ├── Requirements +│ │ └── Meeting Notes +│ └── Project B +├── Processes & Workflows +├── Meeting Notes (Archive) +└── Resources & References +``` + +### Template Creation +1. Identify repeatable content pattern +2. Create page with structure and placeholders +3. Add instructions in placeholders +4. Format with appropriate macros +5. Save as template +6. Share with space or make global +7. **USE**: References for advanced template patterns + +### Documentation Strategy +1. **Assess** current documentation state +2. **Define** documentation goals and audience +3. **Organize** content taxonomy and structure +4. **Create** templates and guidelines +5. **Migrate** existing documentation +6. **Train** teams on best practices +7. **Monitor** usage and adoption +8. **REPORT TO**: Senior PM on documentation health + +### Knowledge Base Management +**Article Types**: +- How-to guides +- Troubleshooting docs +- FAQs +- Reference documentation +- Process documentation + +**Quality Standards**: +- Clear title and description +- Structured with headings +- Updated date visible +- Owner identified +- Reviewed quarterly + +## Essential Macros + +### Content Macros +**Info, Note, Warning, Tip**: +``` +{info} +Important information here +{info} +``` + +**Expand**: +``` +{expand:title=Click to expand} +Hidden content here +{expand} +``` + +**Table of Contents**: +``` +{toc:maxLevel=3} +``` + +**Excerpt & Excerpt Include**: +``` +{excerpt} +Reusable content +{excerpt} + +{excerpt-include:Page Name} +``` + +### Dynamic Content +**Jira Issues**: +``` +{jira:JQL=project = PROJ AND status = "In Progress"} +``` + +**Jira Chart**: +``` +{jirachart:type=pie|jql=project = PROJ|statType=statuses} +``` + +**Recently Updated**: +``` +{recently-updated:spaces=@all|max=10} +``` + +**Content by Label**: +``` +{contentbylabel:label=meeting-notes|maxResults=20} +``` + +### Collaboration Macros +**Status**: +``` +{status:colour=Green|title=Approved} +``` + +**Task List**: +``` +{tasks} +- [ ] Task 1 +- [x] Task 2 completed +{tasks} +``` + +**User Mention**: +``` +@username +``` + +**Date**: +``` +{date:format=dd MMM yyyy} +``` + +## Page Layouts & Formatting + +**Two-Column Layout**: +``` +{section} +{column:width=50%} +Left content +{column} +{column:width=50%} +Right content +{column} +{section} +``` + +**Panel**: +``` +{panel:title=Panel Title|borderColor=#ccc} +Panel content +{panel} +``` + +**Code Block**: +``` +{code:javascript} +const example = "code here"; +{code} +``` + +## Templates Library + +### Meeting Notes Template +``` +**Date**: {date} +**Attendees**: @user1, @user2 +**Facilitator**: @facilitator + +## Agenda +1. Topic 1 +2. Topic 2 + +## Discussion +- Key point 1 +- Key point 2 + +## Decisions +{info}Decision 1{info} + +## Action Items +{tasks} +- [ ] Action item 1 (@owner, due date) +- [ ] Action item 2 (@owner, due date) +{tasks} + +## Next Steps +- Next meeting date +``` + +### Project Overview Template +``` +{panel:title=Project Quick Facts} +**Status**: {status:colour=Green|title=Active} +**Owner**: @owner +**Start Date**: DD/MM/YYYY +**End Date**: DD/MM/YYYY +**Budget**: $XXX,XXX +{panel} + +## Executive Summary +Brief project description + +## Objectives +1. Objective 1 +2. Objective 2 + +## Key Stakeholders +| Name | Role | Responsibility | +|------|------|----------------| +| @user | PM | Overall delivery | + +## Milestones +{jira:project=PROJ AND type=Epic} + +## Risks & Issues +| Risk | Impact | Mitigation | +|------|--------|-----------| +| Risk 1 | High | Action plan | + +## Resources +- [Design Docs](#) +- [Technical Specs](#) +``` + +### Decision Log Template +``` +**Decision ID**: PROJ-DEC-001 +**Date**: {date} +**Status**: {status:colour=Green|title=Approved} +**Decision Maker**: @decisionmaker + +## Context +Background and problem statement + +## Options Considered +1. Option A + - Pros: + - Cons: +2. Option B + - Pros: + - Cons: + +## Decision +Chosen option and rationale + +## Consequences +Expected outcomes and impacts + +## Next Steps +- [ ] Action 1 +- [ ] Action 2 +``` + +### Sprint Retrospective Template +``` +**Sprint**: Sprint XX +**Date**: {date} +**Team**: Team Name + +## What Went Well +{info} +- Positive item 1 +- Positive item 2 +{info} + +## What Didn't Go Well +{warning} +- Challenge 1 +- Challenge 2 +{warning} + +## Action Items +{tasks} +- [ ] Improvement 1 (@owner) +- [ ] Improvement 2 (@owner) +{tasks} + +## Metrics +**Velocity**: XX points +**Completed Stories**: X/X +**Bugs Found**: X +``` + +## Space Permissions + +### Permission Levels +- **View**: Read-only access +- **Edit**: Modify existing pages +- **Create**: Add new pages +- **Delete**: Remove pages +- **Admin**: Full space control + +### Permission Schemes +**Public Space**: +- All users: View +- Team members: Edit, Create +- Space admins: Admin + +**Team Space**: +- Team members: View, Edit, Create +- Team leads: Admin +- Others: No access + +**Project Space**: +- Stakeholders: View +- Project team: Edit, Create +- PM: Admin + +## Content Governance + +**Review Cycles**: +- Critical docs: Monthly +- Standard docs: Quarterly +- Archive docs: Annually + +**Archiving Strategy**: +- Move outdated content to Archive space +- Label with "archived" and date +- Maintain for 2 years, then delete +- Keep audit trail + +**Content Quality Checklist**: +- [ ] Clear, descriptive title +- [ ] Owner/author identified +- [ ] Last updated date visible +- [ ] Appropriate labels applied +- [ ] Links functional +- [ ] Formatting consistent +- [ ] No sensitive data exposed + +## Decision Framework + +**When to Escalate to Atlassian Admin**: +- Need org-wide template +- Require cross-space permissions +- Blueprint configuration +- Global automation rules +- Space export/import + +**When to Collaborate with Jira Expert**: +- Embed Jira queries and charts +- Link pages to Jira issues +- Create Jira-based reports +- Sync documentation with tickets + +**When to Support Scrum Master**: +- Sprint documentation templates +- Retrospective pages +- Team working agreements +- Process documentation + +**When to Support Senior PM**: +- Executive report pages +- Portfolio documentation +- Stakeholder communication +- Strategic planning docs + +## Handoff Protocols + +**FROM Senior PM**: +- Documentation requirements +- Space structure needs +- Template requirements +- Knowledge management strategy + +**TO Senior PM**: +- Documentation coverage reports +- Content usage analytics +- Knowledge gaps identified +- Template adoption metrics + +**FROM Scrum Master**: +- Sprint ceremony templates +- Team documentation needs +- Meeting notes structure +- Retrospective format + +**TO Scrum Master**: +- Configured templates +- Space for team docs +- Training on best practices +- Documentation guidelines + +**WITH Jira Expert**: +- Jira-Confluence linking +- Embedded Jira reports +- Issue-to-page connections +- Cross-tool workflow + +## Best Practices + +**Writing Style**: +- Use active voice +- Write scannable content (headings, bullets, short paragraphs) +- Include visuals and diagrams +- Provide examples +- Keep language simple and clear + +**Organization**: +- Consistent naming conventions +- Meaningful labels +- Logical page hierarchy +- Related pages linked +- Clear navigation + +**Maintenance**: +- Regular content audits +- Remove duplication +- Update outdated information +- Archive obsolete content +- Monitor page analytics + +## Analytics & Metrics + +**Usage Metrics**: +- Page views per space +- Most visited pages +- Search queries +- Contributor activity +- Orphaned pages + +**Health Indicators**: +- Pages without recent updates +- Pages without owners +- Duplicate content +- Broken links +- Empty spaces + +## Atlassian MCP Integration + +**Primary Tool**: Confluence MCP Server + +**Key Operations**: +- Create and manage spaces +- Create, update, and delete pages +- Apply templates and macros +- Manage page hierarchies +- Configure permissions +- Search content +- Extract documentation for analysis + +**Integration Points**: +- Create documentation for Senior PM projects +- Support Scrum Master with ceremony templates +- Link to Jira issues for Jira Expert +- Provide templates for Template Creator diff --git a/project-management/confluence-expert/references/templates.md b/project-management/confluence-expert/references/templates.md new file mode 100644 index 0000000..ff1a24d --- /dev/null +++ b/project-management/confluence-expert/references/templates.md @@ -0,0 +1,725 @@ +# Confluence Page Templates + +## Meeting Notes Template + +```markdown +# [Meeting Title] - [Date] + +**Date:** [YYYY-MM-DD] +**Time:** [HH:MM - HH:MM] +**Location:** [Room/Video link] +**Attendees:** @[Name1], @[Name2], @[Name3] +**Note Taker:** @[Name] + +## Agenda +1. [Topic 1] +2. [Topic 2] +3. [Topic 3] + +## Discussion + +### [Topic 1] +**Summary:** +[Key points discussed] + +**Decisions:** +- [Decision 1] +- [Decision 2] + +**Action Items:** +- [ ] [Action] - @[Owner] - [Due Date] +- [ ] [Action] - @[Owner] - [Due Date] + +### [Topic 2] +**Summary:** +[Key points discussed] + +**Decisions:** +- [Decision 1] + +**Action Items:** +- [ ] [Action] - @[Owner] - [Due Date] + +## Parking Lot +- [Item to discuss later] +- [Future topic] + +## Next Meeting +**Date:** [YYYY-MM-DD] +**Agenda Topics:** +- [Topic 1] +- [Topic 2] +``` + +--- + +## Decision Log Template + +```markdown +# [Decision Title] + +| Field | Value | +|-------|-------| +| **Status** | 🟢 Accepted / 🟡 Proposed / 🔴 Deprecated | +| **Date** | [YYYY-MM-DD] | +| **Deciders** | @[Name1], @[Name2] | +| **Stakeholders** | @[Name3], @[Name4] | +| **Related Decisions** | [Link to related decisions] | + +## Context and Problem Statement +[Describe the context and problem that requires a decision. 2-3 paragraphs explaining: +- What situation led to this decision? +- What problem are we trying to solve? +- What constraints exist?] + +## Decision +[Clearly state the decision made in 1-2 sentences] + +### Details +[Provide additional details about the decision: +- What exactly will we do? +- How will it be implemented? +- What timeline?] + +## Rationale +[Explain why this decision was made: +- What were the key factors? +- What evidence supports this? +- Why is this the best choice?] + +## Consequences + +### Positive Consequences +- ✅ [Benefit 1] +- ✅ [Benefit 2] +- ✅ [Benefit 3] + +### Negative Consequences / Trade-offs +- ⚠️ [Trade-off 1] +- ⚠️ [Trade-off 2] + +### Risks +- 🔴 [Risk 1] - Mitigation: [How we'll handle it] +- 🟡 [Risk 2] - Mitigation: [How we'll handle it] + +## Alternatives Considered + +### Alternative 1: [Name] +**Description:** [What is this alternative?] + +**Pros:** +- [Pro 1] +- [Pro 2] + +**Cons:** +- [Con 1] +- [Con 2] + +**Why Not Chosen:** [Reason] + +### Alternative 2: [Name] +[Same structure as above] + +## Implementation Plan +1. [Step 1] - @[Owner] - [Date] +2. [Step 2] - @[Owner] - [Date] +3. [Step 3] - @[Owner] - [Date] + +## Success Metrics +- [Metric 1]: [Target] +- [Metric 2]: [Target] + +## Review Date +**Next Review:** [YYYY-MM-DD] +**Review Notes:** [Link to review page] + +## References +- [Link 1] +- [Link 2] +- [Link 3] + +--- +*Updated: [Date] by @[Name]* +``` + +--- + +## Technical Specification Template + +```markdown +# [Feature/Component Name] Technical Specification + +| Field | Value | +|-------|-------| +| **Status** | 🟡 Draft / 🟢 Approved / 🔴 Archived | +| **Author** | @[Name] | +| **Reviewers** | @[Name1], @[Name2] | +| **Date Created** | [YYYY-MM-DD] | +| **Last Updated** | [YYYY-MM-DD] | +| **JIRA Epic** | [ABC-123](link) | + +## Overview +[1-2 paragraph summary of what this spec covers and why it matters] + +## Goals and Non-Goals + +### Goals +- [Goal 1] +- [Goal 2] +- [Goal 3] + +### Non-Goals (Out of Scope) +- [Non-goal 1] +- [Non-goal 2] + +## Background +[Context needed to understand this spec: +- What problem are we solving? +- What's the current state? +- Why now?] + +## High-Level Design + +### Architecture Diagram +[Insert diagram here] + +### System Components +1. **[Component 1 Name]** + - Purpose: [What it does] + - Technology: [What it uses] + - Interfaces: [How it connects] + +2. **[Component 2 Name]** + - Purpose: [What it does] + - Technology: [What it uses] + - Interfaces: [How it connects] + +### Data Flow +[Describe how data flows through the system] + +## Detailed Design + +### Component 1: [Name] +**Purpose:** [Detailed purpose] + +**Responsibilities:** +- [Responsibility 1] +- [Responsibility 2] + +**API/Interface:** +``` +[API spec or interface definition] +``` + +**Data Model:** +``` +[Schema or data structure] +``` + +**Key Algorithms/Logic:** +[Describe any complex logic] + +### Component 2: [Name] +[Same structure as Component 1] + +## Database Schema + +### Table: [table_name] +| Column | Type | Constraints | Description | +|--------|------|-------------|-------------| +| id | UUID | PRIMARY KEY | Unique identifier | +| name | VARCHAR(255) | NOT NULL | Entity name | +| created_at | TIMESTAMP | NOT NULL | Creation timestamp | + +### Indexes +- `idx_name` on `name` - For fast lookups +- `idx_created` on `created_at` - For temporal queries + +## API Specification + +### Endpoint: [Method] /api/path +**Purpose:** [What this endpoint does] + +**Request:** +```json +{ + "param1": "value", + "param2": 123 +} +``` + +**Response:** +```json +{ + "result": "success", + "data": {} +} +``` + +**Error Handling:** +- 400: [Reason] +- 404: [Reason] +- 500: [Reason] + +## Security Considerations +- [Security consideration 1] +- [Security consideration 2] +- [Authentication/Authorization approach] +- [Data encryption requirements] + +## Performance Considerations +- [Expected load/throughput] +- [Scalability approach] +- [Caching strategy] +- [Performance targets] + +## Testing Strategy + +### Unit Tests +- [Test area 1] +- [Test area 2] + +### Integration Tests +- [Test scenario 1] +- [Test scenario 2] + +### Performance Tests +- [Load test plan] +- [Performance benchmarks] + +## Deployment Plan +1. [Deployment step 1] +2. [Deployment step 2] +3. [Deployment step 3] + +### Rollback Plan +[How to revert if issues occur] + +## Monitoring and Alerting +- [Metric 1] - Alert threshold: [Value] +- [Metric 2] - Alert threshold: [Value] +- [Log tracking] + +## Migration Plan (if applicable) +[How to migrate from current system] + +## Dependencies +- [Dependency 1] - Why needed +- [Dependency 2] - Why needed + +## Open Questions +- [ ] [Question 1] - @[Owner] +- [ ] [Question 2] - @[Owner] + +## Future Considerations +- [Future enhancement 1] +- [Future enhancement 2] + +## References +- [Link to related specs] +- [Link to design docs] +- [Link to JIRA epics] + +--- +*For questions, contact @[Author]* +``` + +--- + +## How-To Guide Template + +```markdown +# How to [Task Name] + +## Overview +[1-2 sentences explaining what this guide covers and who it's for] + +**Estimated Time:** [X minutes] +**Difficulty:** [Beginner/Intermediate/Advanced] + +## Prerequisites +Before you begin, ensure you have: +- [ ] [Prerequisite 1] +- [ ] [Prerequisite 2] +- [ ] [Prerequisite 3] + +## Quick Summary (TL;DR) +[One paragraph with the essence of the guide for those who just need a reminder] + +## Step-by-Step Instructions + +### Step 1: [Action] +[Detailed description of what to do] + +**Commands/Code:** +```bash +command here +``` + +**Expected Result:** +[What you should see if it worked] + +**Screenshot:** +[Add screenshot if helpful] + +### Step 2: [Action] +[Detailed description] + +**Tips:** +- 💡 [Helpful tip] +- ⚠️ [Warning about common mistake] + +### Step 3: [Action] +[Continue pattern...] + +## Verification +To verify everything worked: +1. [Check 1] +2. [Check 2] + +## Troubleshooting + +### Problem: [Common issue] +**Symptoms:** [What you see] +**Cause:** [Why it happens] +**Solution:** +1. [Fix step 1] +2. [Fix step 2] + +### Problem: [Another issue] +[Same structure as above] + +## Best Practices +- [Best practice 1] +- [Best practice 2] +- [Best practice 3] + +## Related Guides +- [Link to related guide 1] +- [Link to related guide 2] + +## Need Help? +- Questions? Ask in #[channel] +- Issues? Create ticket in [JIRA project] +- Contact: @[Expert name] + +--- +*Last updated: [Date] by @[Name]* +``` + +--- + +## Requirements Document Template + +```markdown +# [Feature/Project Name] Requirements + +| Field | Value | +|-------|-------| +| **Status** | 🟡 Draft / 🟢 Approved / 🔵 In Progress / ✅ Complete | +| **Product Owner** | @[Name] | +| **Stakeholders** | @[Name1], @[Name2] | +| **Target Release** | [Release version] | +| **JIRA Epic** | [ABC-123](link) | +| **Created** | [YYYY-MM-DD] | +| **Last Updated** | [YYYY-MM-DD] | + +## Executive Summary +[2-3 sentences describing the feature and its business value] + +## Business Goals +- [Goal 1]: [Metric] +- [Goal 2]: [Metric] +- [Goal 3]: [Metric] + +## User Stories + +### Story 1: [Title] +**As a** [user type] +**I want** [goal] +**So that** [benefit] + +**Acceptance Criteria:** +- [ ] [Criterion 1] +- [ ] [Criterion 2] +- [ ] [Criterion 3] + +**Priority:** [High/Medium/Low] +**Effort:** [Story points] + +### Story 2: [Title] +[Same structure as Story 1] + +## Functional Requirements + +### FR-001: [Requirement Title] +**Description:** [What the system must do] + +**Rationale:** [Why this is needed] + +**Acceptance Criteria:** +- [Criterion 1] +- [Criterion 2] + +**Priority:** [Must Have / Should Have / Could Have / Won't Have] + +### FR-002: [Requirement Title] +[Same structure as FR-001] + +## Non-Functional Requirements + +### Performance +- [Requirement 1] +- [Requirement 2] + +### Security +- [Requirement 1] +- [Requirement 2] + +### Scalability +- [Requirement 1] +- [Requirement 2] + +### Accessibility +- [Requirement 1] +- [Requirement 2] + +## User Experience + +### Wireframes +[Insert wireframes or link to Figma] + +### User Flow +[Diagram showing user journey] + +### UI Requirements +- [UI requirement 1] +- [UI requirement 2] + +## Technical Constraints +- [Constraint 1] +- [Constraint 2] +- [Constraint 3] + +## Dependencies +| Dependency | Owner | Status | Impact if Blocked | +|------------|-------|--------|-------------------| +| [Dep 1] | @[Name] | 🟢 Ready | [Impact] | +| [Dep 2] | @[Name] | 🟡 In Progress | [Impact] | + +## Success Metrics +| Metric | Baseline | Target | How Measured | +|--------|----------|--------|--------------| +| [Metric 1] | [Current] | [Goal] | [Method] | +| [Metric 2] | [Current] | [Goal] | [Method] | + +## Risks and Mitigations +| Risk | Impact | Probability | Mitigation | +|------|--------|-------------|------------| +| [Risk 1] | High | Medium | [Strategy] | +| [Risk 2] | Medium | Low | [Strategy] | + +## Out of Scope +- [Explicitly excluded 1] +- [Explicitly excluded 2] + +## Open Questions +- [ ] [Question 1] - @[Owner] - [Due date] +- [ ] [Question 2] - @[Owner] - [Due date] + +## Timeline +| Phase | Start Date | End Date | Deliverables | +|-------|-----------|----------|--------------| +| Design | [Date] | [Date] | [Deliverable] | +| Development | [Date] | [Date] | [Deliverable] | +| Testing | [Date] | [Date] | [Deliverable] | +| Launch | [Date] | [Date] | [Deliverable] | + +## Approval + +### Reviewers +- [ ] Product Owner: @[Name] +- [ ] Engineering Lead: @[Name] +- [ ] Design Lead: @[Name] +- [ ] Stakeholder: @[Name] + +**Approved Date:** [YYYY-MM-DD] + +## References +- [Market research] +- [User feedback] +- [Technical specs] +- [Related features] + +--- +*For questions, contact @[Product Owner]* +``` + +--- + +## Retrospective Template + +```markdown +# Sprint [N] Retrospective - [Team Name] + +**Date:** [YYYY-MM-DD] +**Sprint:** [Sprint N] +**Sprint Dates:** [Start Date] - [End Date] +**Facilitator:** @[Name] +**Participants:** @[Name1], @[Name2], @[Name3] + +## Sprint Metrics +- **Velocity:** [X points] (Average: [Y points]) +- **Committed:** [X points / N issues] +- **Completed:** [Y points / M issues] +- **Sprint Goal Met:** ✅ Yes / ❌ No + +## What Went Well 😊 +- [Positive 1] +- [Positive 2] +- [Positive 3] + +## What Didn't Go Well 😞 +- [Challenge 1] +- [Challenge 2] +- [Challenge 3] + +## Action Items from Last Retro +- [✅ / ❌] [Action item 1] - @[Owner] + - Status: [Done / In Progress / Not Done] + - Notes: [Update] +- [✅ / ❌] [Action item 2] - @[Owner] + - Status: [Done / In Progress / Not Done] + - Notes: [Update] + +## Discussion Themes + +### Theme 1: [Topic] +**What we discussed:** +[Summary of discussion] + +**Root cause:** +[What's really causing this issue?] + +**Ideas for improvement:** +- [Idea 1] +- [Idea 2] + +### Theme 2: [Topic] +[Same structure as Theme 1] + +## Action Items for Next Sprint +| Action | Owner | Due Date | Success Criteria | +|--------|-------|----------|------------------| +| [Action 1] | @[Name] | [Date] | [How we know it's done] | +| [Action 2] | @[Name] | [Date] | [How we know it's done] | +| [Action 3] | @[Name] | [Date] | [How we know it's done] | + +## Shout-Outs 🎉 +- @[Name] for [what they did] +- @[Name] for [what they did] + +## Notes +[Any additional notes or observations] + +--- +*Next Retrospective: [Date]* +``` + +--- + +## Status Report Template + +```markdown +# [Project Name] Status Report - [Week of Date] + +**Report Date:** [YYYY-MM-DD] +**Reporting Period:** [Start Date] - [End Date] +**Project Manager:** @[Name] +**Overall Status:** 🟢 On Track / 🟡 At Risk / 🔴 Off Track + +## Executive Summary +[2-3 sentences: What's the current state? What are the key achievements? What needs attention?] + +## Project Health + +| Metric | Status | Details | +|--------|--------|---------| +| **Scope** | 🟢 / 🟡 / 🔴 | [Comment] | +| **Schedule** | 🟢 / 🟡 / 🔴 | [Comment] | +| **Budget** | 🟢 / 🟡 / 🔴 | [Comment] | +| **Quality** | 🟢 / 🟡 / 🔴 | [Comment] | +| **Team Morale** | 🟢 / 🟡 / 🔴 | [Comment] | + +## Key Accomplishments +- ✅ [Accomplishment 1] +- ✅ [Accomplishment 2] +- ✅ [Accomplishment 3] + +## Milestones Status + +| Milestone | Target Date | Status | Actual/Forecast | Notes | +|-----------|-------------|--------|-----------------|-------| +| [Milestone 1] | [Date] | ✅ Complete | [Date] | [Notes] | +| [Milestone 2] | [Date] | 🔄 In Progress | On track | [Notes] | +| [Milestone 3] | [Date] | ⏳ Not Started | [Forecast] | [Notes] | + +## Active Risks + +### 🔴 Critical Risks +| Risk | Impact | Mitigation | Owner | Status | +|------|--------|------------|-------|--------| +| [Risk 1] | High | [Strategy] | @[Name] | [Update] | + +### 🟡 Medium Risks +| Risk | Impact | Mitigation | Owner | Status | +|------|--------|------------|-------|--------| +| [Risk 2] | Medium | [Strategy] | @[Name] | [Update] | + +## Issues & Blockers + +### 🚨 Blockers +- [Blocker 1] - @[Owner] - **Escalated to:** [Person] + - Impact: [What's blocked] + - ETA to resolve: [Date] + +### ⚠️ Issues +- [Issue 1] - @[Owner] + - Status: [Update] + +## Upcoming in Next Period +- [Activity 1] +- [Activity 2] +- [Activity 3] + +## Budget Update (if applicable) +- **Total Budget:** [Amount] +- **Spent to Date:** [Amount] ([%]) +- **Forecast to Complete:** [Amount] +- **Variance:** [Amount] ([%]) + +## Decisions Needed +| Decision | Why Needed | Deadline | Stakeholder | +|----------|-----------|----------|-------------| +| [Decision 1] | [Reason] | [Date] | @[Name] | + +## Team Update +- **Current Team Size:** [N people] +- **Open Positions:** [N] ([Roles]) +- **Recent Additions:** @[Name] - [Role] +- **Upcoming Departures:** [Names/Dates] + +## Metrics (if applicable) +| Metric | This Period | Last Period | Trend | Target | +|--------|-------------|-------------|-------|--------| +| [Metric 1] | [Value] | [Value] | ↗️ / ↘️ / → | [Target] | +| [Metric 2] | [Value] | [Value] | ↗️ / ↘️ / → | [Target] | + +## Links +- [Jira Project](link) +- [Roadmap](link) +- [Technical Docs](link) + +--- +*Next Status Report: [Date]* +``` diff --git a/project-management/jira-expert/SKILL.md b/project-management/jira-expert/SKILL.md new file mode 100644 index 0000000..8af688f --- /dev/null +++ b/project-management/jira-expert/SKILL.md @@ -0,0 +1,319 @@ +--- +name: jira-expert +description: Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations. +--- + +# Atlassian Jira Expert + +Master-level expertise in Jira configuration, project management, JQL, workflows, automation, and reporting. Handles all technical and operational aspects of Jira. + +## Core Competencies + +**Project Configuration** +- Create and configure Jira projects (Scrum, Kanban, custom) +- Design and implement custom workflows +- Configure issue types, fields, and screens +- Set up project permissions and security schemes + +**JQL Mastery** +- Write advanced JQL queries for any use case +- Create complex filters with multiple conditions +- Optimize query performance +- Build saved filters for team use + +**Automation & Integration** +- Design Jira automation rules +- Configure webhooks and integrations +- Set up email notifications +- Integrate with external tools (Confluence, Slack, etc.) + +**Reporting & Dashboards** +- Create custom dashboards with gadgets +- Build reports for sprint metrics, velocity, burndown +- Configure portfolio-level reporting +- Export data for executive reporting + +## Workflows + +### Project Creation +1. Determine project type (Scrum, Kanban, Bug Tracking, etc.) +2. Create project with appropriate template +3. Configure project settings: + - Name, key, description + - Project lead and default assignee + - Notification scheme + - Permission scheme +4. Set up issue types and workflows +5. Configure custom fields if needed +6. Create initial board/backlog view +7. **HANDOFF TO**: Scrum Master for team onboarding + +### Workflow Design +1. Map out process states (To Do → In Progress → Done) +2. Define transitions and conditions +3. Add validators, post-functions, and conditions +4. Configure workflow scheme +5. Associate workflow with project +6. Test workflow with sample issues +7. **USE**: References for complex workflow patterns + +### JQL Query Building +**Basic Structure**: `field operator value` + +**Common Operators**: +- `=, !=` : equals, not equals +- `~, !~` : contains, not contains +- `>, <, >=, <=` : comparison +- `in, not in` : list membership +- `is empty, is not empty` +- `was, was in, was not` +- `changed` + +**Powerful JQL Examples**: + +Find overdue issues: +```jql +dueDate < now() AND status != Done +``` + +Sprint burndown issues: +```jql +sprint = 23 AND status changed TO "Done" DURING (startOfSprint(), endOfSprint()) +``` + +Find stale issues: +```jql +updated < -30d AND status != Done +``` + +Cross-project epic tracking: +```jql +"Epic Link" = PROJ-123 ORDER BY rank +``` + +Velocity calculation: +```jql +sprint in closedSprints() AND resolution = Done +``` + +Team capacity: +```jql +assignee in (user1, user2) AND sprint in openSprints() +``` + +### Dashboard Creation +1. Create new dashboard (personal or shared) +2. Add relevant gadgets: + - Filter Results (JQL-based) + - Sprint Burndown + - Velocity Chart + - Created vs Resolved + - Pie Chart (status distribution) +3. Arrange layout for readability +4. Configure automatic refresh +5. Share with appropriate teams +6. **HANDOFF TO**: Senior PM or Scrum Master for use + +### Automation Rules +1. Define trigger (issue created, field changed, scheduled) +2. Add conditions (if applicable) +3. Define actions: + - Update field + - Send notification + - Create subtask + - Transition issue + - Post comment +4. Test automation with sample data +5. Enable and monitor +6. **USE**: References for complex automation patterns + +## Advanced Features + +### Custom Fields +**When to Create**: +- Track data not in standard fields +- Capture process-specific information +- Enable advanced reporting + +**Field Types**: +- Text: Short text, paragraph +- Numeric: Number, decimal +- Date: Date picker, date-time +- Select: Single select, multi-select, cascading +- User: User picker, multi-user picker + +**Configuration**: +1. Create custom field +2. Configure field context (which projects/issue types) +3. Add to appropriate screens +4. Update search templates if needed + +### Issue Linking +**Link Types**: +- Blocks / Is blocked by +- Relates to +- Duplicates / Is duplicated by +- Clones / Is cloned by +- Epic-Story relationship + +**Best Practices**: +- Use Epic linking for feature grouping +- Use blocking links to show dependencies +- Document link reasons in comments + +### Permissions & Security + +**Permission Schemes**: +- Browse Projects +- Create/Edit/Delete Issues +- Administer Projects +- Manage Sprints + +**Security Levels**: +- Define confidential issue visibility +- Control access to sensitive data +- Audit security changes + +### Bulk Operations +**Bulk Change**: +1. Use JQL to find target issues +2. Select bulk change operation +3. Choose fields to update +4. Preview changes +5. Execute and confirm +6. Monitor background task + +**Bulk Transitions**: +- Move multiple issues through workflow +- Useful for sprint cleanup +- Requires appropriate permissions + +## JQL Functions Reference + +**Date Functions**: +- `startOfDay()`, `endOfDay()` +- `startOfWeek()`, `endOfWeek()` +- `startOfMonth()`, `endOfMonth()` +- `startOfYear()`, `endOfYear()` + +**Sprint Functions**: +- `openSprints()` +- `closedSprints()` +- `futureSprints()` + +**User Functions**: +- `currentUser()` +- `membersOf("group")` + +**Advanced Functions**: +- `issueHistory()` +- `linkedIssues()` +- `issuesWithFixVersions()` + +## Reporting Templates + +**Sprint Report**: +```jql +project = PROJ AND sprint = 23 +``` + +**Team Velocity**: +```jql +assignee in (team) AND sprint in closedSprints() AND resolution = Done +``` + +**Bug Trend**: +```jql +type = Bug AND created >= -30d +``` + +**Blocker Analysis**: +```jql +priority = Blocker AND status != Done +``` + +## Decision Framework + +**When to Escalate to Atlassian Admin**: +- Need new project permission scheme +- Require custom workflow scheme across org +- User provisioning or deprovisioning +- License or billing questions +- System-wide configuration changes + +**When to Collaborate with Scrum Master**: +- Sprint board configuration +- Backlog prioritization views +- Team-specific filters +- Sprint reporting needs + +**When to Collaborate with Senior PM**: +- Portfolio-level reporting +- Cross-project dashboards +- Executive visibility needs +- Multi-project dependencies + +## Handoff Protocols + +**FROM Senior PM**: +- Project structure requirements +- Workflow and field needs +- Reporting requirements +- Integration needs + +**TO Senior PM**: +- Cross-project metrics +- Issue trends and patterns +- Workflow bottlenecks +- Data quality insights + +**FROM Scrum Master**: +- Sprint board configuration requests +- Workflow optimization needs +- Backlog filtering requirements +- Velocity tracking setup + +**TO Scrum Master**: +- Configured sprint boards +- Velocity reports +- Burndown charts +- Team capacity views + +## Best Practices + +**Data Quality**: +- Enforce required fields +- Use field validation +- Regular cleanup of stale issues +- Consistent naming conventions + +**Performance**: +- Optimize JQL queries +- Limit dashboard gadgets +- Use saved filters +- Archive old projects + +**Governance**: +- Document workflow rationale +- Version control for schemes +- Change management for major updates +- Regular permission audits + +## Atlassian MCP Integration + +**Primary Tool**: Jira MCP Server + +**Key Operations**: +- Create and configure projects +- Execute JQL queries for data extraction +- Update issue fields and statuses +- Create and manage sprints +- Generate reports and dashboards +- Configure workflows and automation +- Manage boards and filters + +**Integration Points**: +- Pull metrics for Senior PM reporting +- Configure sprint boards for Scrum Master +- Create documentation pages for Confluence Expert +- Support template creation for Template Creator diff --git a/project-management/jira-expert/references/automation-examples.md b/project-management/jira-expert/references/automation-examples.md new file mode 100644 index 0000000..7674e1e --- /dev/null +++ b/project-management/jira-expert/references/automation-examples.md @@ -0,0 +1,423 @@ +# Jira Automation Examples + +## Auto-Assignment Rules + +### Auto-assign by component +**Trigger:** Issue created +**Conditions:** +- Component is not EMPTY +**Actions:** +- Assign issue to component lead + +### Auto-assign to reporter for feedback +**Trigger:** Issue transitioned to "Waiting for Feedback" +**Actions:** +- Assign issue to reporter +- Add comment: "Please provide additional information" + +### Round-robin assignment +**Trigger:** Issue created +**Conditions:** +- Project = ABC +- Assignee is EMPTY +**Actions:** +- Assign to next team member in rotation (use smart value) + +--- + +## Status Sync Rules + +### Sync subtask status to parent +**Trigger:** Issue transitioned +**Conditions:** +- Issue type = Sub-task +- Transition is to "Done" +- Parent issue exists +- All subtasks are Done +**Actions:** +- Transition parent issue to "Done" + +### Sync parent to subtasks +**Trigger:** Issue transitioned +**Conditions:** +- Issue type has subtasks +- Transition is to "Cancelled" +**Actions:** +- For each: Sub-tasks + - Transition issue to "Cancelled" + +### Epic progress tracking +**Trigger:** Issue transitioned +**Conditions:** +- Epic link is not EMPTY +- Transition is to "Done" +**Actions:** +- Add comment to epic: "{{issue.key}} completed" +- Update epic custom field "Progress" + +--- + +## Notification Rules + +### Slack notification for high-priority bugs +**Trigger:** Issue created +**Conditions:** +- Issue type = Bug +- Priority IN (Highest, High) +**Actions:** +- Send Slack message to #engineering: + ``` + 🚨 High Priority Bug Created + {{issue.key}}: {{issue.summary}} + Reporter: {{issue.reporter.displayName}} + Priority: {{issue.priority.name}} + {{issue.url}} + ``` + +### Email assignee when mentioned +**Trigger:** Issue commented +**Conditions:** +- Comment contains @mention of assignee +**Actions:** +- Send email to {{issue.assignee.emailAddress}}: + ``` + Subject: You were mentioned in {{issue.key}} + Body: {{comment.author.displayName}} mentioned you: + {{comment.body}} + ``` + +### SLA breach warning +**Trigger:** Scheduled - Every hour +**Conditions:** +- Status != Done +- SLA time remaining < 2 hours +**Actions:** +- Send email to {{issue.assignee}} +- Add comment: "⚠️ SLA expires in <2 hours" +- Set priority to Highest + +--- + +## Field Automation Rules + +### Auto-set due date +**Trigger:** Issue created +**Conditions:** +- Issue type = Bug +- Priority = Highest +**Actions:** +- Set due date to {{now.plusDays(1)}} + +### Clear assignee when in backlog +**Trigger:** Issue transitioned +**Conditions:** +- Transition is to "Backlog" +- Assignee is not EMPTY +**Actions:** +- Assign issue to Unassigned +- Add comment: "Returned to backlog, assignee cleared" + +### Auto-populate sprint field +**Trigger:** Issue transitioned +**Conditions:** +- Transition is to "In Progress" +- Sprint is EMPTY +**Actions:** +- Add issue to current sprint + +### Set fix version based on component +**Trigger:** Issue created +**Conditions:** +- Component = "Mobile App" +**Actions:** +- Set fix version to "Mobile v2.0" + +--- + +## Escalation Rules + +### Auto-escalate stale issues +**Trigger:** Scheduled - Daily at 9:00 AM +**Conditions:** +- Status = "Waiting for Response" +- Updated < -7 days +**Actions:** +- Add comment: "@{{issue.reporter}} This issue needs attention" +- Send email to project lead +- Add label: "needs-attention" + +### Escalate overdue critical issues +**Trigger:** Scheduled - Every hour +**Conditions:** +- Priority IN (Highest, High) +- Due date < now() +- Status != Done +**Actions:** +- Transition to "Escalated" +- Assign to project manager +- Send Slack notification + +### Auto-close inactive issues +**Trigger:** Scheduled - Daily at 10:00 AM +**Conditions:** +- Status = "Waiting for Customer" +- Updated < -30 days +**Actions:** +- Transition to "Closed" +- Add comment: "Auto-closed due to inactivity" +- Send email to reporter + +--- + +## Sprint Automation Rules + +### Move incomplete work to next sprint +**Trigger:** Sprint closed +**Conditions:** +- Issue status != Done +**Actions:** +- Add issue to next sprint +- Add comment: "Moved from {{sprint.name}}" + +### Auto-remove completed items from active sprint +**Trigger:** Issue transitioned +**Conditions:** +- Transition is to "Done" +- Sprint IN openSprints() +**Actions:** +- Remove issue from sprint +- Add comment: "Removed from active sprint (completed)" + +### Sprint start notification +**Trigger:** Sprint started +**Actions:** +- Send Slack message to #team: + ``` + 🚀 Sprint {{sprint.name}} Started! + Goal: {{sprint.goal}} + Committed: {{sprint.issuesCount}} issues + ``` + +--- + +## Approval Workflow Rules + +### Request approval for large stories +**Trigger:** Issue created +**Conditions:** +- Issue type = Story +- Story points >= 13 +**Actions:** +- Transition to "Pending Approval" +- Assign to product owner +- Send email notification + +### Auto-approve small bugs +**Trigger:** Issue created +**Conditions:** +- Issue type = Bug +- Priority IN (Low, Lowest) +**Actions:** +- Transition to "Approved" +- Add comment: "Auto-approved (low-priority bug)" + +### Require security review +**Trigger:** Issue transitioned +**Conditions:** +- Transition is to "Ready for Release" +- Labels contains "security" +**Actions:** +- Transition to "Security Review" +- Assign to security-team +- Send email to security@company.com + +--- + +## Integration Rules + +### Create GitHub issue +**Trigger:** Issue transitioned +**Conditions:** +- Transition is to "In Progress" +- Labels contains "needs-tracking" +**Actions:** +- Send webhook to GitHub API: + ```json + { + "title": "{{issue.key}}: {{issue.summary}}", + "body": "{{issue.description}}", + "assignee": "{{issue.assignee.name}}" + } + ``` + +### Update Confluence page +**Trigger:** Issue transitioned +**Conditions:** +- Issue type = Epic +- Transition is to "Done" +**Actions:** +- Send webhook to Confluence: + - Update epic status page + - Add completion date + +--- + +## Quality & Testing Rules + +### Require test cases for features +**Trigger:** Issue transitioned +**Conditions:** +- Issue type = Story +- Transition is to "Ready for QA" +- Custom field "Test Cases" is EMPTY +**Actions:** +- Transition back to "In Progress" +- Add comment: "❌ Test cases required before QA" + +### Auto-create test issue +**Trigger:** Issue transitioned +**Conditions:** +- Issue type = Story +- Transition is to "Ready for QA" +**Actions:** +- Create linked issue: + - Type: Test + - Summary: "Test: {{issue.summary}}" + - Link type: "tested by" + - Assignee: QA team + +### Flag regression bugs +**Trigger:** Issue created +**Conditions:** +- Issue type = Bug +- Affects version is in released versions +**Actions:** +- Add label: "regression" +- Set priority to High +- Add comment: "🚨 Regression in released version" + +--- + +## Documentation Rules + +### Require documentation for features +**Trigger:** Issue transitioned +**Conditions:** +- Issue type = Story +- Labels contains "customer-facing" +- Transition is to "Done" +- Custom field "Documentation Link" is EMPTY +**Actions:** +- Reopen issue +- Add comment: "📝 Documentation required for customer-facing feature" + +### Auto-create doc task +**Trigger:** Issue transitioned +**Conditions:** +- Issue type = Epic +- Transition is to "In Progress" +**Actions:** +- Create subtask: + - Type: Task + - Summary: "Documentation for {{issue.summary}}" + - Assignee: {{issue.assignee}} + +--- + +## Time Tracking Rules + +### Log work reminder +**Trigger:** Issue transitioned +**Conditions:** +- Transition is to "Done" +- Time spent is EMPTY +**Actions:** +- Add comment: "⏱️ Reminder: Please log your time" + +### Warn on high time spent +**Trigger:** Work logged +**Conditions:** +- Time spent > original estimate * 1.5 +**Actions:** +- Add comment: "⚠️ Time spent exceeds estimate by 50%" +- Send notification to assignee and project manager + +--- + +## Advanced Conditional Rules + +### Conditional assignee based on priority +**Trigger:** Issue created +**Conditions:** +- Issue type = Bug +**Actions:** +- If: Priority = Highest + - Assign to on-call engineer +- Else if: Priority = High + - Assign to team lead +- Else: + - Assign to next available team member + +### Multi-step approval flow +**Trigger:** Issue transitioned +**Conditions:** +- Transition is to "Request Approval" +- Budget estimate > $10,000 +**Actions:** +- If: Budget > $50,000 + - Assign to CFO + - Send email to executive team +- Else if: Budget > $10,000 + - Assign to Director + - Add comment: "Director approval required" +- Add label: "pending-approval" + +--- + +## Smart Value Examples + +### Dynamic assignee based on component +``` +{{issue.components.first.lead.accountId}} +``` + +### Days since created +``` +{{issue.created.diff(now).days}} +``` + +### Conditional message +``` +{{#if(issue.priority.name == "Highest")}} + 🚨 CRITICAL +{{else}} + ℹ️ Normal priority +{{/}} +``` + +### List all subtasks +``` +{{#issue.subtasks}} + - {{key}}: {{summary}} ({{status.name}}) +{{/}} +``` + +### Calculate completion percentage +``` +{{issue.subtasks.filter(item => item.status.statusCategory.key == "done").size.divide(issue.subtasks.size).multiply(100).round()}}% +``` + +--- + +## Best Practices + +1. **Test in sandbox** - Always test rules on test project first +2. **Start simple** - Begin with basic rules, add complexity incrementally +3. **Use conditions wisely** - Narrow scope to reduce unintended triggers +4. **Monitor audit log** - Check automation execution history regularly +5. **Limit actions** - Keep rules focused, don't chain too many actions +6. **Name clearly** - Use descriptive names: "Auto-assign bugs to component lead" +7. **Document rules** - Add description explaining purpose and owner +8. **Review regularly** - Audit rules quarterly, disable unused ones +9. **Handle errors** - Add error handling for webhooks and integrations +10. **Performance** - Avoid scheduled rules that query large datasets hourly diff --git a/project-management/jira-expert/references/jql-examples.md b/project-management/jira-expert/references/jql-examples.md new file mode 100644 index 0000000..7391bd2 --- /dev/null +++ b/project-management/jira-expert/references/jql-examples.md @@ -0,0 +1,415 @@ +# JQL Query Examples + +## Sprint Queries + +**Current sprint issues:** +```jql +sprint IN openSprints() ORDER BY rank +``` + +**Issues in specific sprint:** +```jql +sprint = "Sprint 23" ORDER BY priority DESC +``` + +**All sprint work (current and backlog):** +```jql +project = ABC AND issuetype IN (Story, Bug, Task) +ORDER BY sprint DESC, rank +``` + +**Unscheduled stories:** +```jql +project = ABC AND issuetype = Story AND sprint IS EMPTY +AND status != Done ORDER BY priority DESC +``` + +**Spillover from last sprint:** +```jql +sprint IN closedSprints() AND sprint NOT IN (latestReleasedVersion()) +AND status != Done ORDER BY created DESC +``` + +**Sprint completion rate:** +```jql +sprint = "Sprint 23" AND status = Done +``` + +## User & Team Queries + +**My open issues:** +```jql +assignee = currentUser() AND status != Done +ORDER BY priority DESC, created ASC +``` + +**Unassigned in my project:** +```jql +project = ABC AND assignee IS EMPTY AND status != Done +ORDER BY priority DESC +``` + +**Issues I'm watching:** +```jql +watcher = currentUser() AND status != Done +``` + +**Team workload:** +```jql +assignee IN membersOf("engineering-team") AND status IN ("In Progress", "In Review") +ORDER BY assignee, priority DESC +``` + +**Issues I reported that are still open:** +```jql +reporter = currentUser() AND status != Done ORDER BY created DESC +``` + +**Issues commented on by me:** +```jql +comment ~ currentUser() AND status != Done +``` + +## Date Range Queries + +**Created today:** +```jql +created >= startOfDay() ORDER BY created DESC +``` + +**Updated in last 7 days:** +```jql +updated >= -7d ORDER BY updated DESC +``` + +**Created this week:** +```jql +created >= startOfWeek() AND created <= endOfWeek() +``` + +**Created this month:** +```jql +created >= startOfMonth() AND created <= endOfMonth() +``` + +**Not updated in 30 days:** +```jql +status != Done AND updated <= -30d ORDER BY updated ASC +``` + +**Resolved yesterday:** +```jql +resolved >= startOfDay(-1d) AND resolved < startOfDay() +``` + +**Due this week:** +```jql +duedate >= startOfWeek() AND duedate <= endOfWeek() AND status != Done +``` + +**Overdue:** +```jql +duedate < now() AND status != Done ORDER BY duedate ASC +``` + +## Status & Workflow Queries + +**In Progress issues:** +```jql +project = ABC AND status = "In Progress" ORDER BY assignee +``` + +**Blocked issues:** +```jql +project = ABC AND labels = blocked AND status != Done +``` + +**Issues in review:** +```jql +project = ABC AND status IN ("Code Review", "QA Review", "Pending Approval") +ORDER BY updated ASC +``` + +**Ready for development:** +```jql +project = ABC AND status = "Ready" AND sprint IS EMPTY +ORDER BY priority DESC +``` + +**Recently done:** +```jql +project = ABC AND status = Done AND resolved >= -7d +ORDER BY resolved DESC +``` + +**Status changed today:** +```jql +status CHANGED AFTER startOfDay() ORDER BY updated DESC +``` + +**Long-running in progress:** +```jql +status = "In Progress" AND status CHANGED BEFORE -14d +ORDER BY status CHANGED ASC +``` + +## Priority & Type Queries + +**High priority bugs:** +```jql +issuetype = Bug AND priority IN (Highest, High) AND status != Done +ORDER BY priority DESC, created ASC +``` + +**Critical blockers:** +```jql +priority = Highest AND status != Done ORDER BY created ASC +``` + +**All epics:** +```jql +issuetype = Epic ORDER BY status, priority DESC +``` + +**Stories without acceptance criteria:** +```jql +issuetype = Story AND "Acceptance Criteria" IS EMPTY AND status = Backlog +``` + +**Technical debt:** +```jql +labels = tech-debt AND status != Done ORDER BY priority DESC +``` + +## Complex Multi-Condition Queries + +**My team's sprint work:** +```jql +sprint IN openSprints() +AND assignee IN membersOf("engineering-team") +AND status != Done +ORDER BY assignee, priority DESC +``` + +**Bugs created this month, not in sprint:** +```jql +issuetype = Bug +AND created >= startOfMonth() +AND sprint IS EMPTY +AND status != Done +ORDER BY priority DESC, created DESC +``` + +**High-priority work needing attention:** +```jql +project = ABC +AND priority IN (Highest, High) +AND status IN ("In Progress", "In Review") +AND updated <= -3d +ORDER BY priority DESC, updated ASC +``` + +**Stale issues:** +```jql +project = ABC +AND status NOT IN (Done, Cancelled) +AND (assignee IS EMPTY OR updated <= -30d) +ORDER BY created ASC +``` + +**Epic progress:** +```jql +"Epic Link" = ABC-123 ORDER BY status, rank +``` + +## Component & Version Queries + +**Issues in component:** +```jql +project = ABC AND component = "Frontend" AND status != Done +``` + +**Issues without component:** +```jql +project = ABC AND component IS EMPTY AND status != Done +``` + +**Target version:** +```jql +fixVersion = "v2.0" ORDER BY status, priority DESC +``` + +**Released versions:** +```jql +fixVersion IN releasedVersions() ORDER BY fixVersion DESC +``` + +## Label & Text Search Queries + +**Issues with label:** +```jql +labels = urgent AND status != Done +``` + +**Multiple labels (AND):** +```jql +labels IN (frontend, bug) AND status != Done +``` + +**Search in summary:** +```jql +summary ~ "authentication" ORDER BY created DESC +``` + +**Search in summary and description:** +```jql +text ~ "API integration" ORDER BY created DESC +``` + +**Issues with empty description:** +```jql +description IS EMPTY AND issuetype = Story +``` + +## Performance-Optimized Queries + +**Good - Specific project first:** +```jql +project = ABC AND status = "In Progress" AND assignee = currentUser() +``` + +**Bad - User filter first:** +```jql +assignee = currentUser() AND status = "In Progress" AND project = ABC +``` + +**Good - Use functions:** +```jql +sprint IN openSprints() AND status != Done +``` + +**Bad - Hardcoded sprint:** +```jql +sprint = "Sprint 23" AND status != Done +``` + +**Good - Specific date:** +```jql +created >= 2024-01-01 AND created <= 2024-01-31 +``` + +**Bad - Relative with high cost:** +```jql +created >= -365d AND created <= -335d +``` + +## Reporting Queries + +**Velocity calculation:** +```jql +sprint = "Sprint 23" AND status = Done +``` +*Then sum story points* + +**Bug rate:** +```jql +project = ABC AND issuetype = Bug AND created >= startOfMonth() +``` + +**Average cycle time:** +```jql +project = ABC AND resolved >= startOfMonth() +AND resolved <= endOfMonth() +``` +*Calculate time from In Progress to Done* + +**Stories delivered this quarter:** +```jql +project = ABC AND issuetype = Story +AND resolved >= startOfYear() AND resolved <= endOfQuarter() +``` + +**Team capacity:** +```jql +assignee IN membersOf("engineering-team") +AND sprint IN openSprints() +``` +*Sum original estimates* + +## Notification & Watching Queries + +**Issues I need to review:** +```jql +status = "Pending Review" AND assignee = currentUser() +``` + +**Issues assigned to me, high priority:** +```jql +assignee = currentUser() AND priority IN (Highest, High) +AND status != Done +``` + +**Issues created by me, not resolved:** +```jql +reporter = currentUser() AND status != Done +ORDER BY created DESC +``` + +## Advanced Functions + +**Issues changed from status:** +```jql +status WAS "In Progress" AND status = "Done" +AND status CHANGED AFTER startOfWeek() +``` + +**Assignee changed:** +```jql +assignee CHANGED BY currentUser() AFTER -7d +``` + +**Issues re-opened:** +```jql +status WAS Done AND status != Done ORDER BY updated DESC +``` + +**Linked issues:** +```jql +issue IN linkedIssues("ABC-123") ORDER BY issuetype +``` + +**Parent epic:** +```jql +parent = ABC-123 ORDER BY rank +``` + +## Saved Filter Examples + +**Daily Standup Filter:** +```jql +assignee = currentUser() AND sprint IN openSprints() +AND status != Done ORDER BY priority DESC +``` + +**Team Sprint Board Filter:** +```jql +project = ABC AND sprint IN openSprints() ORDER BY rank +``` + +**Bugs Dashboard Filter:** +```jql +project = ABC AND issuetype = Bug AND status != Done +ORDER BY priority DESC, created ASC +``` + +**Tech Debt Backlog:** +```jql +project = ABC AND labels = tech-debt AND status = Backlog +ORDER BY priority DESC +``` + +**Needs Triage:** +```jql +project = ABC AND status = "To Triage" +AND created >= -7d ORDER BY created ASC +``` diff --git a/project-management/scrum-master/SKILL.md b/project-management/scrum-master/SKILL.md new file mode 100644 index 0000000..7d499c7 --- /dev/null +++ b/project-management/scrum-master/SKILL.md @@ -0,0 +1,189 @@ +--- +name: scrum-master +description: Scrum Master for agile software development teams. Use for sprint planning, daily standups, retrospectives, backlog refinement, velocity tracking, removing impediments, facilitating ceremonies, coaching teams on agile practices, and managing sprint execution for R&D and development teams. +--- + +# Scrum Master Expert + +Agile practitioner facilitating Scrum ceremonies, coaching teams, removing impediments, and ensuring sprint success for interdisciplinary software development teams. + +## Core Responsibilities + +**Sprint Facilitation** +- Plan and run sprint ceremonies (planning, daily standup, review, retrospective) +- Ensure team adheres to Scrum framework +- Track sprint progress and velocity +- Facilitate backlog refinement + +**Team Coaching** +- Coach team on agile principles and Scrum practices +- Build self-organizing, high-performing teams +- Foster continuous improvement culture +- Mentor team members on estimation and collaboration + +**Impediment Removal** +- Identify and remove blockers quickly +- Escalate critical issues to Senior PM +- Shield team from external interruptions +- Facilitate cross-team dependencies + +**Metrics & Reporting** +- Track velocity, burndown, and sprint health +- Report sprint outcomes and team capacity +- Identify trends and improvement opportunities +- Provide data for Senior PM reporting + +## Workflows + +### Sprint Planning +1. Review and refine product backlog with Product Owner +2. Confirm team capacity and availability +3. Facilitate sprint goal definition +4. Guide team through story estimation (planning poker) +5. Commit to sprint backlog +6. **USE**: Jira Expert to configure sprint and move issues +7. **HANDOFF TO**: Team for execution + +### Daily Standup +1. Facilitate 15-minute timebox +2. Each team member answers: What did I do? What will I do? Blockers? +3. Update sprint board with progress +4. Identify and capture impediments +5. Schedule follow-up discussions offline +6. **USE**: Jira Expert to update board status + +### Sprint Review +1. Demonstrate completed work to stakeholders +2. Gather feedback on delivered increment +3. Update product backlog based on feedback +4. Celebrate team accomplishments +5. **USE**: Confluence Expert to document feedback + +### Sprint Retrospective +1. Review what went well and what didn't +2. Identify actionable improvements +3. Commit to 1-3 improvement actions +4. Track improvement action items +5. **USE**: Confluence Expert to document retrospective notes + +### Backlog Refinement +1. Review upcoming backlog items with team +2. Break down large stories into smaller ones +3. Clarify requirements and acceptance criteria +4. Estimate story points +5. Ensure backlog is ready for next sprint +6. **USE**: Jira Expert to update and organize backlog + +### Velocity Tracking +1. Track completed story points per sprint +2. Calculate rolling average velocity +3. Identify velocity trends and anomalies +4. Forecast capacity for upcoming sprints +5. **REPORT TO**: Senior PM for portfolio planning + +## Decision Framework + +**When to Escalate to Senior PM** +- Sprint goals at risk of not being met +- Team velocity declining >20% for 2+ sprints +- Critical impediments blocking entire team +- Resource conflicts or team composition changes +- Cross-project dependencies blocking progress + +**When to Request Jira Expert** +- Complex workflow configuration needed +- Custom fields or issue types required +- Advanced filtering or reporting needs +- Board configuration changes +- Automation rules setup + +**When to Request Confluence Expert** +- Team documentation structure needed +- Meeting notes templates required +- Decision log setup +- Team handbook creation + +## Scrum Metrics + +**Sprint Health Indicators**: +- Sprint burndown: On track vs. behind +- Velocity trend: Stable, increasing, decreasing +- Commitment reliability: % stories completed +- Impediment resolution time +- Sprint goal achievement rate + +**Team Health Indicators**: +- Team morale and engagement +- Collaboration quality +- Technical debt accumulation +- Test coverage trends +- Production incidents + +## Handoff Protocols + +**FROM Senior PM**: +- Project scope and objectives +- Initial backlog priorities +- Team composition +- Sprint cadence and ceremony schedule + +**TO Senior PM**: +- Sprint completion reports +- Velocity trends and forecasts +- Team capacity changes +- Blocker escalations +- Risk identification + +**WITH Jira Expert**: +- Sprint board configuration +- Workflow status updates +- Velocity and burndown data +- Backlog organization + +**WITH Confluence Expert**: +- Sprint planning documentation +- Retrospective notes +- Team agreements and working protocols +- Definition of Done/Ready + +## Agile Best Practices + +**Story Estimation**: +- Use planning poker for team consensus +- Estimate in story points (Fibonacci sequence) +- Reference story for baseline +- Re-estimate only when new information emerges + +**Definition of Done**: +- Code reviewed and approved +- All tests passing (unit, integration, E2E) +- Documentation updated +- Deployed to staging +- Acceptance criteria met + +**Definition of Ready**: +- User story clearly defined +- Acceptance criteria documented +- Story estimated by team +- Dependencies identified +- No blockers + +## Ceremony Timeboxes + +- Daily Standup: 15 minutes +- Sprint Planning: 2 hours per week of sprint +- Sprint Review: 1 hour per week of sprint +- Sprint Retrospective: 1.5 hours per week of sprint +- Backlog Refinement: 10% of sprint capacity + +## Atlassian MCP Integration + +**Tools Used**: +- Jira for sprint management, backlog, and velocity tracking +- Confluence for ceremony notes, team documentation, and retrospectives + +**Key Actions**: +- Use Jira MCP to create sprints, move issues, track progress +- Use Jira MCP to generate burndown charts and velocity reports +- Use Confluence MCP to create sprint planning and retrospective pages +- Use Jira MCP for backlog filtering and prioritization diff --git a/project-management/scrum-master/references/retro-formats.md b/project-management/scrum-master/references/retro-formats.md new file mode 100644 index 0000000..3178ce8 --- /dev/null +++ b/project-management/scrum-master/references/retro-formats.md @@ -0,0 +1,336 @@ +# Sprint Retrospective Formats + +## Start/Stop/Continue + +**Best for:** Teams new to retrospectives, quick format +**Duration:** 45-60 minutes + +### Structure +Create three columns: +- **Start:** What should we begin doing? +- **Stop:** What should we stop doing? +- **Continue:** What's working well that we should keep doing? + +### Process +1. Team silently adds items to each column (10 min) +2. Group similar items (5 min) +3. Discuss each category, vote on top items (20 min) +4. Select 2-3 actions (10 min) + +### Example Output +**Start:** +- Pairing on complex stories +- Code reviews within 4 hours + +**Stop:** +- Taking on work mid-sprint +- Skipping acceptance criteria + +**Continue:** +- Daily standups at 9:30am +- Demo prep on Thursday +--- + +## Glad/Sad/Mad + +**Best for:** Emotional check-in, team morale assessment +**Duration:** 60-75 minutes + +### Structure +Create three areas: +- **Glad:** What made you happy this sprint? +- **Sad:** What disappointed you? +- **Mad:** What frustrated you? + +### Process +1. Silent brainstorming (10 min) +2. Share items, one person at a time (15 min) +3. Group themes (5 min) +4. Discuss top items from each category (20 min) +5. Identify action items (10 min) + +### Example Output +**Glad:** +- Shipped feature X on time +- Great collaboration with design team +- New deployment process worked well + +**Sad:** +- Lost time to production bugs +- Didn't finish all committed work +- Documentation fell behind + +**Mad:** +- Environment was down 2 days +- Requirements changed mid-sprint +- Still waiting on API key from vendor + +### Facilitation Tips +- Acknowledge emotions, don't dismiss +- Focus on what we can control +- Convert frustrations into actions + +--- + +## 4Ls (Liked, Learned, Lacked, Longed For) + +**Best for:** Deeper reflection, learning focus +**Duration:** 60-90 minutes + +### Structure +- **Liked:** What went well? What did we enjoy? +- **Learned:** What new insights did we gain? +- **Lacked:** What was missing? What did we need? +- **Longed For:** What do we wish we had? + +### Process +1. Individual reflection (10 min) +2. Round-robin sharing (20 min) +3. Group similar items (10 min) +4. Deep dive on top items (20 min) +5. Action planning (15 min) + +### Example Output +**Liked:** +- Pair programming sessions +- Clear acceptance criteria +- Product Owner availability + +**Learned:** +- New testing framework capabilities +- How to better estimate stories +- Importance of architectural review + +**Lacked:** +- Automated deployment +- Clear API documentation +- Sufficient testing time + +**Longed For:** +- Better development environments +- More design time upfront +- Dedicated QA support + +--- + +## Sailboat + +**Best for:** Visual teams, identifying headwinds and tailwinds +**Duration:** 60-90 minutes + +### Structure +Draw a sailboat with: +- **Wind (propellers):** What's helping us go faster? +- **Anchors:** What's slowing us down? +- **Rocks (hazards):** What risks are ahead? +- **Island (goal):** Where are we headed? + +### Process +1. Explain metaphor (5 min) +2. Team adds sticky notes to each area (15 min) +3. Group and discuss each area (30 min) +4. Prioritize anchors to remove (10 min) +5. Create action plan (15 min) + +### Example Output +**Wind:** +- Strong team collaboration +- Clear product vision +- Good tooling + +**Anchors:** +- Slow CI/CD pipeline +- Too many meetings +- Technical debt + +**Rocks:** +- Upcoming dependency on Team B +- Key person on vacation next sprint +- Infrastructure migration + +**Island:** +- Launch v2.0 by end of quarter +- Improve system stability +- Reduce production bugs by 50% + +--- + +## Timeline + +**Best for:** Detailed sprint review, identifying patterns +**Duration:** 75-90 minutes + +### Structure +Create a timeline of the sprint on a whiteboard: +- Days of the sprint across the top +- Events, milestones, feelings plotted on timeline + +### Process +1. Draw sprint timeline (5 min) +2. Team adds events chronologically (15 min) +3. Add emotion indicators (happy/sad/stressed) (10 min) +4. Identify patterns and themes (20 min) +5. Discuss high/low points (20 min) +6. Extract learnings and actions (15 min) + +### Example Timeline +``` +Day 1: Sprint planning, feeling optimistic 😊 +Day 3: Production bug discovered, stressed 😰 +Day 5: Bug fixed, relieved 😌 +Day 7: Design feedback changed scope, frustrated 😠 +Day 9: Great pairing session on new feature 😊 +Day 10: Demo went really well! 🎉 +``` + +### Facilitation Tips +- Focus on objective events first, emotions second +- Look for correlations between events and feelings +- Identify early warning signs +- Celebrate wins + +--- + +## Starfish + +**Best for:** More granular feedback than Start/Stop/Continue +**Duration:** 60-90 minutes + +### Structure +Five categories: +- **Keep Doing:** What's working, don't change +- **Less Of:** What should we reduce? +- **More Of:** What should we increase? +- **Stop Doing:** What should we eliminate? +- **Start Doing:** What new practices should we try? + +### Process +1. Explain each category (5 min) +2. Silent brainstorming (15 min) +3. Share and group items (15 min) +4. Discuss each category (25 min) +5. Vote on top actions (10 min) +6. Create action plan (15 min) + +### Example Output +**Keep Doing:** +- Pairing on complex stories +- Demo every Friday + +**Less Of:** +- Context switching +- Unplanned work + +**More Of:** +- Automated testing +- Design upfront + +**Stop Doing:** +- Skipping code reviews +- Working weekends + +**Start Doing:** +- Mob programming for knowledge sharing +- Weekly architecture discussions + +--- + +## Speed Dating + +**Best for:** Large teams, fresh perspectives +**Duration:** 60 minutes + +### Structure +- Pair up team members who don't usually work together +- Rotate pairs every 10 minutes +- Discuss sprint from different perspectives + +### Process +1. Create pairs (2 min) +2. Round 1: "What went well?" (10 min) +3. Rotate pairs (2 min) +4. Round 2: "What could improve?" (10 min) +5. Rotate pairs (2 min) +6. Round 3: "What should we try?" (10 min) +7. Full group synthesis (15 min) +8. Action planning (10 min) + +### Facilitation Tips +- Ensure quiet voices are heard +- Mix up pairs intentionally +- Capture themes as they emerge +- Focus on shared themes in synthesis + +--- + +## Three Little Pigs + +**Best for:** Architecture and technical decisions +**Duration:** 60-75 minutes + +### Structure +Based on the story: +- **Straw House:** What's fragile? What will blow down? +- **Stick House:** What's okay but could be better? +- **Brick House:** What's solid and will last? + +### Process +1. Explain metaphor (5 min) +2. Team identifies items for each house (15 min) +3. Group and discuss (20 min) +4. Prioritize straw house items to fix (10 min) +5. Create action plan (15 min) + +### Example Output +**Straw House (fragile):** +- Manual deployment process +- No automated tests for API +- Undocumented code + +**Stick House (needs improvement):** +- Test coverage at 60% +- Some documentation exists +- Partially automated builds + +**Brick House (solid):** +- Strong CI/CD for frontend +- Well-tested core modules +- Clear architecture docs + +--- + +## Facilitation Best Practices + +### Before Retrospective +- Review previous action items +- Gather sprint metrics +- Choose format based on team needs +- Prepare collaboration space + +### During Retrospective +- **Set the stage:** Create safe environment +- **Prime directive:** "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand." +- **Timebox discussions:** Keep energy high +- **Focus on actions:** Not just talk +- **Limit action items:** 1-3 max for next sprint +- **Get specific:** Vague actions don't happen + +### After Retrospective +- Document immediately in Confluence +- Create Jira tickets for actions +- Assign owners and due dates +- Track completion +- Start next retro by reviewing these + +### Red Flags +- Same issues every retro → Need deeper intervention +- No action items → Team not engaged +- Blame game → Not safe environment +- No follow-through → Actions not valued +- Facilitator talks more than team → Not facilitating + +### Rotation Strategy +- Vary formats every 2-3 sprints +- Let team choose occasionally +- Match format to team mood +- Try new format when stuck diff --git a/project-management/senior-pm/SKILL.md b/project-management/senior-pm/SKILL.md new file mode 100644 index 0000000..0bdce57 --- /dev/null +++ b/project-management/senior-pm/SKILL.md @@ -0,0 +1,146 @@ +--- +name: senior-pm +description: Senior Project Manager for Software, SaaS, and digital web/mobile applications. Use for strategic planning, portfolio management, stakeholder alignment, risk management, roadmap development, budget oversight, cross-functional team leadership, and executive reporting for software products. +--- + +# Senior Project Management Expert + +Strategic project management for Software, SaaS, and digital applications (web and mobile). Handles portfolio management, executive reporting, stakeholder alignment, risk management, and cross-functional leadership. + +## Core Responsibilities + +**Strategic Planning** +- Develop product roadmaps aligned with business objectives +- Define project scope, objectives, and success criteria +- Create multi-project portfolio strategies +- Align technical initiatives with business goals + +**Stakeholder Management** +- Executive-level communication and reporting +- Manage expectations across C-suite, product, engineering, and sales +- Facilitate strategic decision-making +- Build consensus across departments + +**Risk & Budget Management** +- Identify and mitigate project risks +- Budget planning and resource allocation +- ROI analysis and business case development +- Change management and impact assessment + +**Team Leadership** +- Cross-functional team coordination +- Resource capacity planning +- Conflict resolution and escalation management +- Foster high-performance team culture + +## Workflows + +### Project Initiation +1. Gather business requirements and objectives +2. Define project scope, timeline, and budget +3. Identify stakeholders and create RACI matrix +4. Develop project charter and get executive approval +5. **HANDOFF TO**: Scrum Master for sprint planning or Jira Expert for project setup + +### Portfolio Management +1. Review all active projects and initiatives +2. Assess resource allocation across portfolio +3. Prioritize projects based on business value and strategic fit +4. Identify dependencies and potential conflicts +5. Create executive summary dashboard +6. **USE**: Jira Expert to pull cross-project metrics + +### Risk Management +1. Conduct risk identification workshops +2. Assess probability and impact of each risk +3. Develop mitigation and contingency plans +4. Track risks in risk register +5. Escalate critical risks to stakeholders +6. **USE**: Confluence Expert to document risk register + +### Stakeholder Reporting +1. Define reporting cadence and KPIs +2. Gather metrics from Scrum Master and Jira Expert +3. Create executive summaries highlighting: + - Project status and health + - Budget vs. actual + - Key accomplishments and blockers + - Upcoming milestones + - Risks and mitigation actions +4. Present to stakeholders with actionable insights +5. **USE**: Confluence Expert for report templates + +## Decision Framework + +**When to Escalate** +- Budget overruns >15% +- Timeline slippage affecting releases +- Resource conflicts across multiple projects +- Strategic pivot requests +- Critical risk realization + +**When to Delegate** +- Day-to-day sprint management → Scrum Master +- Technical project setup → Jira Expert +- Documentation management → Confluence Expert +- User/permission management → Atlassian Administrator +- Template creation → Template Creator + +## Communication Standards + +**Executive Updates**: Weekly summary, monthly deep dive +**Team Updates**: Bi-weekly all-hands, daily async +**Stakeholder Reviews**: Monthly business review +**Risk Reports**: Real-time for critical, weekly for others + +## Handoff Protocols + +**TO Scrum Master**: +- Project scope and objectives defined +- Initial backlog priorities identified +- Team composition confirmed +- Sprint cadence agreed + +**TO Jira Expert**: +- Project structure requirements +- Workflow and field needs +- Reporting requirements +- Integration needs + +**TO Confluence Expert**: +- Documentation requirements +- Space structure needs +- Template requirements +- Knowledge management strategy + +**FROM Scrum Master**: +- Sprint health metrics +- Velocity trends +- Team capacity issues +- Blocker escalations + +**FROM Jira Expert**: +- Cross-project metrics +- Issue trends and patterns +- Workflow bottlenecks +- Data quality issues + +## Key Performance Indicators + +- On-time delivery rate +- Budget variance +- Stakeholder satisfaction score +- Team velocity trends +- Risk mitigation effectiveness +- Resource utilization rate + +## Atlassian MCP Integration + +**Tools Used**: +- Jira for portfolio dashboards and cross-project reporting +- Confluence for strategic documentation and stakeholder reports + +**Key Queries**: +- Use Jira MCP to aggregate metrics across multiple projects +- Use Confluence MCP to create and maintain executive report pages +- Track portfolio health through Jira filters and dashboards diff --git a/project-management/senior-pm/references/api_reference.md b/project-management/senior-pm/references/api_reference.md new file mode 100644 index 0000000..1aeda66 --- /dev/null +++ b/project-management/senior-pm/references/api_reference.md @@ -0,0 +1,34 @@ +# Reference Documentation for Senior Pm + +This is a placeholder for detailed reference documentation. +Replace with actual reference content or delete if not needed. + +Example real reference docs from other skills: +- product-management/references/communication.md - Comprehensive guide for status updates +- product-management/references/context_building.md - Deep-dive on gathering context +- bigquery/references/ - API references and query examples + +## When Reference Docs Are Useful + +Reference docs are ideal for: +- Comprehensive API documentation +- Detailed workflow guides +- Complex multi-step processes +- Information too lengthy for main SKILL.md +- Content that's only needed for specific use cases + +## Structure Suggestions + +### API Reference Example +- Overview +- Authentication +- Endpoints with examples +- Error codes +- Rate limits + +### Workflow Guide Example +- Prerequisites +- Step-by-step instructions +- Common patterns +- Troubleshooting +- Best practices