...
| Expand | ||
|---|---|---|
| ||
In short, not really. We recommend leaving the work item in the column where it is blocked and then adding a “Blocked” attribute or tag to the item. This allows you to measure total time blocked without disrupting your workflow. Additionally, the Flow Efficiency Chart uses this information and can tell you how much time items spend waiting versus actually being worked on. |
| Expand | ||
|---|---|---|
| ||
ActionableAgile looks for a label called “blocked” on a work item. The case doesn’t matter. ActionableAgile tracks how long it had the label (in days) and if it currently has the label. We count partial days except in the case in which it is blocked and unblocked in the same day. |
| Expand | ||
|---|---|---|
| ||
If you have a well-defined workflow, Analytics can help you regardless of your methodology. The most important thing is deciding when work starts and when it finishes--that’s all we need to determine the key metrics of WIP, Cycle Time, Throughput, and Age. We’ll load other information about your work and workflow from the data you give us, but starting and finishing work is by far the most important thing.  After your data is loaded into Analytics, you can use the Workflow Stages control to select the parts of your workflow you want to use. Work is considered to be started when it enters the first enabled workflow stage, and it’s done when it enters the last selected stage, so checking and unchecking boxes will change all your metrics. Since the data is already loaded, it’s fast, so feel free to play around with different settings and filters. |
...