Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Dashboard quickly shows key data for some lean metrics, reports and delivery date forecast. Please use the global filter to select the issues in scope for the dashboard. A key setting is also the SW factory statuses. They are configured either in the dashboard settings or lean tab.

...

Work In Progress (WIP)

The number of issues worked in parallel in the SW Factory. To many WIP is a clear indication that your team is multitasking which is negatively impacting productivity. The WIP should be stable and at a low level typically 2-3 per developer.

Flow Efficiency

This is an efficiency indicator. It shows how much time your issues are spent in waiting statues. As in a real factory the team is more efficient the less waiting time the issues are having. Which statuses are waiting are configured in the "Lean Tab" under the chart "Flow Efficiency Scatter Plot".

Bug Density

This is a quality indicator with the calculation (all new bugs / all issues closed) during the last two weeks. So it puts your bug inflow against all your output. As an example a 20% bug density means that for each 10 issues you deliver you get 2 bugs back. Please note that this metric is not related to the SW factory. A issue is closed once it is closed in Jira configurable in the global setting.

Issue Cycle Time

Answer the question, how long time it takes for one issue to pass through your the SW factory with a probability. This is very often the key indicator for your team and a low number means that they deliver value frequently. Default is too count all days with ignoring non-buisness days configurable in settings.

SW Factory

The issue statuses that are within your SW factory configurable in this settings. A good best practice is to have the "backlog" and the "on production" statuses outside the SW factory and the rest within. With this you measure the cycle time from when your teams start until the issues are on production.

Forecast How Many

How many issues/story points are expected to complete within 30 days with probability (The Monte Carlo simulations uses last 30 days throughput)