Dash It Out!

Building a DevOps Dashboard That Actually Works

The Challenge

Picture this: You’re managing multiple DevOps projects, and every day you’re bombarded with questions. “How many work items did we complete this week?” “Which repository is causing the most build failures?” “Are we on track for this sprint?”

The data was there, scattered across Azure DevOps, buried in APIs, hidden in logs. But turning that data into answers? That was taking hours of manual work every week.

The Solution

That’s when we decided to build something different: a single dashboard that would tell the story of our DevOps performance at a glance. Using Microsoft Fabric and Power BI, we created a dashboard that transforms raw data into clear, actionable insights.

The Dashboard Story

The Morning Check-In

Every morning, we start with the KPI cards at the top. In seconds, we see:

  • 6 work items completed today (and 60.86 this week)
  • 86 commits pushed today (410 this week)
  • 11 pull requests opened today (102 this week)
  • 0.34 hours average time per work item (showing we’re getting faster)

These aren’t just numbers, they’re the pulse of our team. When we see those week-over-week trends, we know immediately if we’re accelerating or if something needs attention.

The Project Health Check

The treemap visualization tells a visual story. We can instantly see which projects are consuming the most build resources. That big red block? That’s our marketing analytics dashboard, 110 builds completed. It’s not just about volume; it’s about understanding where our infrastructure costs are going.

The Productivity Story

The bar chart showing “Work Items Completed by Project” reveals something interesting: our marketing analytics team is crushing it with 156 completed items, while customer engagement sits at 37. Is that a problem? Not necessarily, but it tells us where to look deeper. Maybe customer engagement has more complex work items, or maybe they need support. The dashboard doesn’t give us answers, but it asks the right questions.

The Warning Signs

The failure rate line chart is like a health monitor. When we see a repository’s line trending upward, we know to investigate before it becomes a crisis. It’s saved us from production issues more than once by catching problems early.

The Team Balance

The “Active Work Items Per User” chart tells a human story. When we see SampleUser10 with 17 active items while SampleUser9 has 5, we know it’s time for a conversation. Not about blame, about balance. This visualization helps prevent burnout and ensures everyone has a sustainable workload.

The Pipeline Health

The donut chart showing pipeline pass rates gives us instant confidence (or concern) about our deployment health. Seeing that marketing analytics has a 38% pass rate tells us that repository is stable. But when we see customer engagement at 9%, we know that’s where we need to focus our improvement efforts.

The Magic of Filters

But here’s what makes this dashboard powerful: the filters. With a few clicks, we can answer any question:

  • “How did Team Alpha perform in Iteration 2?” → Filter by team and iteration
  • “What’s the status of all Features across projects?” → Filter by work item type
  • “Show me only active work items for Project X” → Filter by project and state

Suddenly, we’re not just looking at data, we’re having a conversation with it.

The Business Impact

This dashboard changed how we work:

Before: Weekly status meetings spent arguing about whose numbers were right.
After: We start meetings with the dashboard already open, discussing what the data means and what actions to take.

Before: Infrastructure costs were a mystery until the monthly bill arrived.
After: We see build activity in real-time and can optimize costs proactively.

Before: Problems were discovered in production.
After: We spot failure rate trends early and fix issues before they impact users.

Before: Workload imbalances led to team burnout.
After: We redistribute work based on data, not assumptions.

The Technical Journey

Building this wasn’t just about creating pretty charts. It required:

  1. Ingesting raw data from Azure DevOps APIs into our Bronze layer
  2. Cleaning and standardizing it in the Silver layer
  3. Transforming it into a star schema in the Gold layer with dimension and fact tables
  4. Visualizing it in Power BI with interactive filters and real-time updates

The medallion architecture (Bronze-Silver-Gold) ensures our data is reliable, and the star schema makes queries fast, even with millions of rows.

The Real Win

The real win isn’t the dashboard itself, it’s what happens when data becomes accessible. Developers check their own metrics. Project managers make data-driven decisions. Executives understand our velocity without needing a 50-slide presentation.

We went from spending hours creating reports to spending minutes understanding our performance. That’s the power of great visualization: it doesn’t just show data, it tells a story.

What’s Next

This dashboard is just the beginning. We’re already planning to add predictive analytics for sprint completion, integrate cost management data, and create role-specific views. But the foundation is solid: when you can see your data clearly, you can act on it confidently.


This dashboard demonstrates how modern data visualization transforms operational chaos into clear business insights. Four charts became six, and those six charts became the foundation for better decisions, happier teams, and more reliable software.