Metrics
Derek Huether
Most Important Metric for an Enterprise

As an executive, you will be faced with the choice to do the pivot (if you can) or persevere (if you have no other choice). This will lead to a series of “bets”. You lead with a hypothesis that the things you change will allow you to operate at pre-event levels. But, how long will it actually take for you to validate your hypothesis and have a bet pay off with pre-event levels? If you run out of time to figure it out or run out of bets you can place, then you either lose your standing in the market or worse risk going out of business.

Derek Huether
How to identify dependencies with Tableau and ...

Regardless of the organization or institution, there will always be dependencies. The larger the organization, the greater chance of the existence of dependencies.
This template is available for download from Tableau Public

Video
Derek Huether
Value Stream Management

In the following interview (both video and audio), Dave Prior and I explore why Value Stream Management is so important, how it works, the connection to Value Stream Mapping, and how you can get started with it.

Derek Huether
Key Performance Indicators (KPIs)

Key performance indicators (KPIs) are metrics that are used to evaluate the performance of an organization or individual. They are used to measure progress towards achieving specific goals or objectives and to determine whether an organization or individual is meeting their targets.

Enterprise Insights, Jira Align, Metrics, Tableau
Derek Huether
How Atlassian Jira Align Supports Flow Metrics

I keep getting asked, does Jira Align support Flow Metrics, as defined in the Flow Framework and SAFe? The short answer is yes. If you believe these metrics will help unlock the potential of your teams, use this community post to see working examples of Tableau reports I have created using Jira Align and Enterprise Insights.

How Atlassian Jira Align Supports Flow Metrics

CD3

Cost of Delay is Important

A few days ago, I published an introduction to Cost of Delay over on the LeadingAgile blog. I asked some of my colleagues to check my numbers because the one thing I've noticed, people can be pretty unforgiving with spelling and math errors. The interest and response from both my colleagues and readers has been really positive. What I demonstrated in the blog post is, surprisingly, doing the most valuable feature first in your portfolio backlog is not always the best economic decision. Next time you prioritize your portfolio, do not just try to maximize value delivered. Limit your cost of delay. - See more at: http://www.leadingagile.com/2015/06/an-introduction-to-cost-of-delay/#sthash.ODrAFTyO.dpuf