9.5 Manage Team
Lead the team day to day: track performance, resolve conflict, give feedback.
Executing / Resource · ← PMBOK reference · See it on the map
Why it matters
Unresolved conflict or unnoticed underperformance drags on quietly until it shows up as a missed deadline, by which point it is much harder to fix.
What done looks like
Team performance is actively tracked, and conflicts and feedback are being addressed.
First time tip
Address a conflict as soon as you notice it, not once it disrupts the work. A small disagreement left alone tends to harden into a lasting grudge.
What you need (Inputs)
- Resource Management Plan
How Scrum/Kanban projects satisfy this — counted from: project roles (driftless/models/agile.py:ProjectRole) — naming who holds each agile role (product owner, Scrum Master, developer, stakeholder proxy) is how an agile team plans its resources, in place of the stored prose plan a predictive project writes - Issue Log
How Scrum/Kanban projects satisfy this — counted from: impediments (driftless/models/agile.py:Impediment) — an impediment IS an issue raised against the team's progress; healthy once none are open or in progress - Lessons Learned Register
How Scrum/Kanban projects satisfy this — counted from: sprint retrospective evidence (driftless/models/delivery.py:Sprint) — a sprint closed with retrospective notes is a lesson captured, the way a predictive project files one as prose - Project Team Assignments
- Team Charter
- Work Performance Reports
How Scrum/Kanban projects satisfy this — counted from: sprint review evidence (driftless/models/delivery.py:Sprint) — a sprint closed with review notes is the periodic report the sprint's own cadence produces, fresh while the latest is inside the reporting window - Team Performance Assessments
How you do it (Tools & Techniques)
What you get (Outputs)
- Change Requests
- Issue Log
How Scrum/Kanban projects satisfy this — counted from: impediments (driftless/models/agile.py:Impediment) — an impediment IS an issue raised against the team's progress; healthy once none are open or in progress - Project Team Assignments
Worked example
Two weeks in, a volunteer coordinator and the site foreman are both directing the same helpers. It comes out at the Friday walk-through, and who directs whom is settled that day instead of being left to harden.
Common pitfalls
- Waiting for a conflict to disrupt the work before addressing it.
- Saving feedback for the end, when nothing can be done with it.
- Tracking the tasks closely and the people not at all.
How driftless helps
- Conflict Management can be run here.
- Issue Log can be created in the wizard.