Agile Frameworks/Methodologies · Topic 4 of 4
Adaptive Artifacts and Task Management
CAPM adaptive controls and tasks: backlogs, boards, burndown and burnup charts, Definition of Done, success criteria and prioritizing with MoSCoW.
- 4 min
- Artifacts: product and iteration backlogs, task board, burndown, burnup, cumulative flow, Definition of Done.
- Burndown: work left; burnup: work done against total scope.
- Acceptance criteria are per item; the Definition of Done applies to all items.
What it is
Adaptive projects control work through visible artifacts rather than long reports. Backlogs, task boards and charts show everyone the real state of the work every day. Task management means breaking work into tasks, prioritizing them and knowing when each is truly done.
How it works
Common adaptive artifacts
| Artifact | What it shows |
|---|---|
| Product backlog | All desired work, ordered by priority |
| Iteration (sprint) backlog | The items and tasks selected for the current iteration |
| Task board or Kanban board | Each item's status in columns, for example To do, In progress, Done |
| Burndown chart | Work remaining over time; the line should fall toward zero |
| Burnup chart | Work completed over time against total scope; shows scope changes clearly |
| Cumulative flow diagram | Items in each state over time; widening bands reveal bottlenecks |
| Velocity chart | Work completed per iteration |
| Definition of Done (DoD) | The shared checklist for when an item is complete |
| Product roadmap and release plan | When groups of features are expected |
| Information radiator | Any large, visible display of project information, such as a board on the wall |
Reading a burndown chart
| Pattern | Meaning |
|---|---|
| Actual line above the ideal line | Behind plan |
| Actual line below the ideal line | Ahead of plan |
| Flat line for several days | No work being completed, or work not being updated |
| Line goes up | Scope was added or work was re-estimated upward |
Success criteria for a task
A task or story is finished when it meets its acceptance criteria and the team's Definition of Done.
- Acceptance criteria are specific to one item: what it must do to be accepted, often written as "Given ... when ... then ...".
- The Definition of Done applies to all items: for example coded, tested, reviewed, documented and integrated.
- Some teams also use a Definition of Ready: an item is clear and small enough to start.
Prioritizing tasks
| Technique | How it works |
|---|---|
| MoSCoW | Must have, Should have, Could have, Won't have this time |
| Business value | Highest value items first |
| Risk | Tackle high-risk items early to learn sooner |
| Dependencies | Items others depend on come first |
| Kano model | Classifies features as basic, performance or delighters |
| Minimum viable product (MVP) | The smallest product that delivers value and lets the team learn |
The product owner sets the priority of backlog items; the team breaks items into tasks and decides who does them.
Task management steps
- Take the highest priority items into the iteration.
- Break each item into tasks.
- Team members pull tasks; show them on the board.
- Update the board and burndown daily; raise blockers at the standup.
- Check each item against its acceptance criteria and the Definition of Done.
- Demonstrate completed items at the review; reflect at the retrospective.
A burndown that rises usually means scope was added. A burnup makes this easier to see because it shows total scope as a separate line.
How the exam asks about this
- "What does MoSCoW stand for?" Must have, Should have, Could have, Won't have.
- "Which chart shows work remaining in the iteration?" A burndown chart.
- "When is a user story done?" When it meets its acceptance criteria and the Definition of Done.
What to remember for the exam
- Artifacts: product and iteration backlogs, task board, burndown, burnup, cumulative flow, Definition of Done.
- Burndown: work left; burnup: work done against total scope.
- Acceptance criteria are per item; the Definition of Done applies to all items.
- MoSCoW: Must, Should, Could, Won't.
- The product owner prioritizes; the team plans the tasks.
Do not mark an item done because the code is written. It must meet the acceptance criteria and the Definition of Done.
Common mistakes
Confusing burndown and burnup. Burndown falls toward zero; burnup rises toward total scope.
Mixing acceptance criteria with the Definition of Done. One is item specific; the other is shared.
Letting the project manager assign every task. Agile teams pull work.
Check yourself
What is an information radiator?
A large, visible display of project information, such as a task board or burndown chart.
What is the difference between acceptance criteria and the Definition of Done?
Acceptance criteria are specific to one item; the Definition of Done is a shared standard for every item.
Who prioritizes the product backlog?
The product owner.
Topic 4 of 4 in Agile Frameworks/Methodologies
Test yourself on Agile Frameworks/Methodologies
The full PMI CAPM question bank has 1,049 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.