Skill-Details
project-management
Direct software project management covering Agile, Scrum, Kanban, and tracking.
Vor Nutzung prüfen
Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.
SKILL.md
Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.
---
name: project-management
description: Agile methodologies, issue tracking, and team collaboration tools
domain: tools-integrations
version: 1.0.0
tags: [agile, scrum, kanban, jira, github-projects, linear]
triggers:
keywords:
primary: [agile, scrum, kanban, jira, linear, sprint, backlog]
secondary: [issue, story point, velocity, retrospective, standup, epic]
context_boost: [team, planning, roadmap, tracking]
context_penalty: [code, implementation, api]
priority: medium
---
# Project Management
## Overview
Software project management methodologies, issue tracking systems, and team collaboration practices.
---
## Agile Methodologies
### Scrum Framework
```
┌─────────────────────────────────────────────────────────────────┐
│ Scrum Framework │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Product Sprint Sprint Sprint │
│ Backlog → Planning → Execution → Review/Retro │
│ │ │ │
│ ▼ ▼ │
│ Sprint Daily Standup │
│ Backlog (15 min) │
│ │
│ Roles: │
│ • Product Owner: Backlog priority, stakeholder voice │
│ • Scrum Master: Process facilitation, impediment removal │
│ • Development Team: Self-organizing, cross-functional │
│ │
│ Artifacts: │
│ • Product Backlog: Prioritized feature list │
│ • Sprint Backlog: Committed sprint work │
│ • Increment: Potentially shippable product │
│ │
│ Events: │
│ • Sprint Planning: What & How for sprint │
│ • Daily Standup: Sync & impediments │
│ • Sprint Review: Demo to stakeholders │
│ • Sprint Retrospective: Process improvement │
└─────────────────────────────────────────────────────────────────┘
```
### Kanban Board
```
┌──────────────┬──────────────┬──────────────┬──────────────┬──────────────┐
│ Backlog │ To Do │ In Progress │ Review │ Done │
│ │ (WIP: 5) │ (WIP: 3) │ (WIP: 2) │ │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │
│ │ Feature │ │ │ Bug fix │ │ │ API │ │ │ Login │ │ │ Auth │ │
│ │ Request │ │ │ #123 │ │ │ endpoint │ │ │ page │ │ │ module │ │
│ └──────────┘ │ └──────────┘ │ │ @alice │ │ │ @bob │ │ └──────────┘ │
│ ┌──────────┐ │ ┌──────────┐ │ └──────────┘ │ └──────────┘ │ ┌──────────┐ │
│ │ Tech │ │ │ Refactor │ │ ┌──────────┐ │ │ │ Database │ │
│ │ Debt │ │ │ auth │ │ │ Tests │ │ │ │ migration│ │
│ └──────────┘ │ └──────────┘ │ │ @charlie │ │ │ └──────────┘ │
│ │ │ └──────────┘ │ │ │
└──────────────┴──────────────┴──────────────┴──────────────┴──────────────┘
Key Principles:
• Visualize work
• Limit Work In Progress (WIP)
• Manage flow
• Make policies explicit
• Implement feedback loops
• Improve collaboratively
```
### User Stories
```markdown
# User Story Format
As a [type of user]
I want [goal/desire]
So that [benefit/value]
# Example
As a registered user
I want to reset my password via email
So that I can regain acceVollständige Quelle auf GitHub lesen (öffnet externe Seite)