This evening I attending the monthly Agile Leadership Network event. I noticed a very familiar slide on Waste In Software Projects. It looks familiar because I have it in my training deck as well! Yes, my Introduction to Agile class has a slide that credits the Standish Group Study reported at XP2002 by Jim Johnson, Chairman. In reviewing software systems, Jim Johnston, Chairman of the Standish Group, determined that in systems defined and delivered using a traditional / waterfall style approach almost half of all features developed and paid for are never used. The question this evening was, for the 45% of the features that were never used, what was the cost incurred? Well, I can tell you it's probably a lot more than 45% of the budget! What if the features that were never used were actually the most costly as well? The rule we should learn here is we should eliminate the waste at the source, before it makes it all the way to the Production environment. If a feature or product is never used, it's waste. But, since XP2002, have we learned our lessons? Are we still delivering features that customers will never use? I figured I would create a quick Google Doc that would collect some data. After giving it some thought, I decided to remove the link to the Google Doc. The collection of data was just a distraction from the actual blog post. Thank you to those to participated.
Metrics
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.
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
Enterprise Insights, Jira Align, Metrics, Tableau
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.
