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

Steps

Free Communications Management Plan Template

Communications Management PlanI participated in a Communication Working Group session for the PMO today. Imagine a dozen people sitting around a table laughing for 10 minutes, when they realized I had shaved off my goatee. After the excitement subsided, we rolled up our sleeves and got to work. It was really quite refreshing to see how excited everyone was to be there. (We only had 4 people for the prior meeting) Ishikawa diagrams littered the walls and the smell of Scripto markers filled the air. I can't stress enough how important it is to have a Communications Management Plan.  Feel free to download my template.  If not, I recommend following the next 7 steps to write your own.

  1. List the project stakeholders and their associated roles and responsibilities
  2. Specify contact information for each stakeholder
  3. For each stakeholder identified, specify the information required to keep stakeholders informed and enable them to fulfill their project roles and responsibilities. Also, specify the timeframe, frequency, or trigger for distribution of the information.
  4. List the information that must be collected, summarized, and reported in order to produce the communication outputs that fulfill the stakeholder information requirements. Specify the associated collection and reporting details.
  5. List each report or document to be produced and distributed as a communication output to fulfill the stakeholder information requirements. Specify the associated distribution, storage, and disposition details.
  6. List and describe the distribution groups that will be used to distribute project information.
  7. Last, define all terms and acronyms required to interpret the Communication Management Plan properly.