I was recently tasked with the mission of finding the state of the art in RMM (Remote Monitoring and Management) and wanted to check in and report some of the very cool findings I’ve made. Long time Dashboard Spy readers know that I’m fond of the data visualization and dashboard work that the infrastructure side of the industry does. Network management, endpoint security, remote backup and recovery and patch management are some areas that can produce a lot of data and bring reporting challenges. I’ve always watched the vendors in this space for how they manage their dashboard reporting.
Enterprise Dashboard Digest readers know how I like to point out the ever-increasing adoption by the public of the dashboard layout as a design pattern. I’m always pointing out examples of dashboard-like layouts in popular software applications. I believe that the prevalence of the dashboard design is what makes today’s business intelligence dashboards so easy to adopt and embrace.
I just noticed that Youtube is now laying out “related videos” in a dashboard-like pattern at the end of their videos. Have you noticed what it now looks like? Take a look at these examples:
The marketing dashboard examples deals with a multiple channel scenario that crosses both online and offline efforts. Take a look. Good background on marketing dashboard approach (case study is of a health insurance company marketing across multiple channels interested in tracking conversion funnel metrics).
I had the pleasure of being shown the ins and outs of the latest dashboard software product, Klipfolio Dashboard for Web and Mobile. Freshly launched, this dashboard system is a model of clarity in design and usability. Klipfolio President and CEO, Allan Wille, personally takes us through the Klipfolio screens in this video:
This excellent article on Scrum best practices focuses on the use of project dashboards in an agile environment. Titled Agile Project Dashboards, this article focuses on providing a solid approach to Agile Project Dashboards.
The main indicators suggested for the project dashboard are:
Project Progress Schedule
Delivered Business Value
Product Release Burn Up Chart
Delivered Story Points
Overall Project Status (Red – Green – Yellow)
Read the article for elaboration on each of the points.
Here is the premise for the project dashboard:
We should take a minute to think about our PO’s priorities and responsibilities. Many companies end up with former Project Managers running this role. If that’s the case, there is a big chance that the PO will be responsible for managing costs, tracking project schedule, people, risks, follow up on features for commercial releases, communicating, etc. In many scenarios this kind of information won’t be necessarily revealed during a Demo, during the Sprint planning, or even on the Retrospectives. If that’s the case, there’s a chance that the team will be disrupted at some point to be asked about this data.
The question that arises here is: does the team have sufficient information to help the PO identify some of these variables and indicators? Can the Team provide more business value, apart from the Product Increment at the end of each Sprint? Can we take advantage of our Scrum ceremonies to compile some of this information in a clear and visual Dashboard?