Workable backlog shows the number of tasks that should be done(tasks scheduled in the do-week), could be done (tasks without constraints), will be done (tasks committed in do-week) and did (tasks completed) in the do-week.
To know more, read 4.19 Workable Backlog (Lookahead) article.
A real-time reflection of effective planning and execution of the project, this data provides brief insights about the performance of the project such as constraint management, site readiness, percent plan complete and plan reliability.
1. Workable Backlogs (Overview)
Graph 1: Weekly Workable Backlog
Graph 1 shows workable backlog numbers for each week in the project. For example, in the image above, for the week of 2nd October 2018,
"should do tasks" = 118, this means that there were 118 tasks that should have been done in that week.
"can do tasks" = 117, it indicates one of them had a constraint and so it could not be done in that week.
"will do tasks" = 104, it shows that out of 117 tasks that could have been done, the project team committed to do only 104 of them.
"did tasks" = 78, this means that out of the 104 tasks that were committed to the do-list only 78 were done as planned and remaining were either delayed or extended.
This charts also give an overall view of how tasks are being committed and done over the course of a time. It can be seen that the number of should , can, will and did tasks have increased gradually between 22 May 2018 and 2 Oct 2018. This graph provides insights on the project team's performance and commitment levels allowing them to improve further on the same as evident here.
Notes: Exceptions for the Workable Backlog Numbers
Can Do numbers are not affected to the tasks which cannot be committed due to dependencies from tasks from other activities (cross dependencies), but its has no dependency or constraint directly applied to it or its parent activity. See the below scenario for an example.
In this example, the task Not counted in 'Can Do' has a constraint. Therefore, it is not counted in "Can Do". It has a SS0 successor to the task Counted in Can Do. Thus, the task Counted in Can Do cannot be committed - however it is still counted as "Can Do" in the Workable Backlog. Only if it has a predecessor that has not started, or a constraint applied to it or its activity, it will not be counted in Can Do.