| Chart type |
Where to find it |
Required data |
Best for |
Project burndown (based on total effort)
changing chart type... |
- Backlog
- Dashboard
- Project details
|
- estimated effort for stories,
- planned velocity for iterations
|
As it does not require any initial estimation it’s best for some research projects or exploratory work where stories are invented based on the results from the recent iterations.
 You can read more in "Burning down, climbing up..." |
Project burndown (based on initial effort)
changing chart type... |
- Backlog
- Dashboard
- Project details
|
- estimated effort for stories,
- planned velocity for iterations
|
Good for projects with some initial vision represented in the backlog and estimated at the beginning (at least as the epic stories). Good also for projects with fixed-price contract as then we usually have an initial estimation and we want to watch it burned according to a planned velocity.
You can read more in "Burning down, climbing up..." |
Project burnup
changing chart type... |
- Backlog
- Dashboard
- Project details
|
- estimated effort for stories,
- planned velocity for iterations
|
Good for all types of projects. Shows most of the interesting patterns in all kinds of projects and it's easy to maintain even on the white board.
You can read more in "Burning down, climbing up..." |
Iteration burndown ("User stories")
 |
|
- estimated effort for stories
|
This chart is good for projects with lot of small stories that do not span whole iteration, but are rather finished within 1-2 days. Only then this chart can provide a good level of detail on iteration state changes. |
Iteration burndown ("Tasks")
 |
|
- some tasks for user stories
- estimated effort on tasks (optional)
|
Very good when your stories get bigger and you start adding more tasks for each story but you still don't want to play with Timesheet. This chart depends only on tasks and can also use their estimates. But even if you don't use tasks estimation then tinyPM treats all tasks as equal and until you finish the tasks quickly the chart provides a very good insight on iteration progress. |
Iteration burndown ("Effort left")
 |
|
- estimated effort on tasks
- time left in the Timesheet for each task (optional)
|
This chart is done in the original Scrum way. It requires entering time left for each task regularly in the Timesheet. It also requires that you do your task estimation in time units so it corresponds to time left in the timesheet.
On the other hand it's the only chart that can nicely show scope creep on tasks during the iteration as well as all unexpected issues that appeared during the iteration (it may go up instead of burning down, which suggests trouble).
Provides best level of detail. If you don't enter time left values it will look same like "Tasks" burndown, as tinyPM will use estimated effort also for this chart. |
Project budget tracking
 |
- Backlog
- Dashboard
- Project details
|
- estimated effort for stories
- time spent in the Timesheet for tasks
- budget defined in project settings
|
Very easy to use and good to track not only project progress in therms of scope, but also in terms of budget left. Requires tracking time spent on tasks by all team members in the Timesheet.
You can read more in "We are in the right truck!" |
If this documentation doesn't solve your problem or has left you with any questions, please don't hesitate to contact us at support@tinypm.com
