Project Management
Plan, track, and coordinate software development projects effectively.
Task Breakdown
Work Decomposition
- •Break features into deliverable units (1-3 day effort)
- •Identify dependencies between tasks
- •Define clear acceptance criteria
- •Estimate complexity (not time)
Task Sizing (Story Points)
| Points | Description |
|---|---|
| 1 | Trivial change, well-understood |
| 2 | Small task, minor complexity |
| 3 | Medium task, some unknowns |
| 5 | Larger task, multiple components |
| 8 | Complex task, significant effort |
| 13 | Very complex, consider splitting |
Sprint Planning
Capacity Planning
code
Available capacity = Team size × Days × Focus factor (0.6-0.8) Recommended commitment = 70-80% of capacity Buffer = 20-30% for unknowns
Sprint Structure
- •Planning - Select and commit to sprint goals
- •Daily sync - Blockers, progress, coordination
- •Development - Execute on committed work
- •Review - Demo completed work
- •Retrospective - Process improvements
Dependency Analysis
Identify Dependencies
- •Technical: APIs, data schemas, libraries
- •Resource: People, environments, tools
- •External: Third-party services, approvals
Critical Path
- •Map all task dependencies
- •Identify longest path to completion
- •Prioritize critical path tasks
- •Monitor for delays
Progress Tracking
Key Metrics
- •Velocity: Points completed per sprint
- •Burn-down: Remaining work over time
- •Cycle time: Start to completion duration
- •Blocked time: Time waiting on dependencies
Status Categories
code
Not Started → In Progress → In Review → Done
↓
Blocked (note blocker)
Stakeholder Communication
Status Updates
code
## Project Status: [Project Name] **Date**: [Date] **Health**: [Green/Yellow/Red] ### Completed This Period - [Accomplishments] ### In Progress - [Current work] ### Upcoming - [Next priorities] ### Risks/Blockers - [Issues needing attention]
Escalation Triggers
- •Blocked for >2 days without resolution path
- •Scope change affecting timeline >20%
- •Critical dependency at risk
- •Resource conflicts
Risk Management
Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Description] | Low/Med/High | Low/Med/High | [Plan] |
Common Risks
- •Scope creep: Define clear boundaries, change process
- •Technical debt: Allocate capacity for maintenance
- •Key person dependency: Document, cross-train
- •Integration issues: Early integration testing
Team Coordination
Handoffs
- •Document context and decisions
- •Update task status and notes
- •Notify receiving party
- •Verify understanding
Conflict Resolution
- •Identify root cause (technical vs process)
- •Gather perspectives from all parties
- •Focus on project goals, not positions
- •Document decision and rationale