https://agileanalytics.nl/blog Artikelen over SLO's, DevEx, DORA-metrics en teamprestaties — praktische inzichten van het team van Agile Analytics. nl agile-analytics-cloud/web/scripts/generate-feed.js Tue, 18 Aug 2026 09:38:22 GMT https://agileanalytics.nl/blog/dora-vs-space-welk-metrics-framework-heb-je-nodig https://agileanalytics.nl/blog/dora-vs-space-welk-metrics-framework-heb-je-nodig Tue, 18 Aug 2026 09:38:22 GMT De één is een vaste set van vier uitkomsten. De ander is een manier om te bepalen wát je überhaupt meet. Teams behandelen ze als concurrerende opties en vragen zich daarna af waarom de cijfers niet kloppen. Zoia Baletska https://agileanalytics.nl/blog/pluralsight-flow-wordt-uitgefaseerd-wat-nu https://agileanalytics.nl/blog/pluralsight-flow-wordt-uitgefaseerd-wat-nu Sat, 15 Aug 2026 14:41:15 GMT Renewals closed on 30 June 2026 and the product retires at the end of 2027. Appfire is not recommending a replacement, so here is an honest look at the options — including when the answer is not us. Arjan Franzen https://agileanalytics.nl/blog/iteratiesnelheid-wat-snelle-teams-echt-meten https://agileanalytics.nl/blog/iteratiesnelheid-wat-snelle-teams-echt-meten Fri, 14 Aug 2026 09:00:00 GMT De snelste iteratieloops ter wereld zitten niet in software. Begrijpen waaróm die zo snel zijn, zegt iets ongemakkelijks over hoe de meeste teams werken — en wijst naar het handjevol dingen dat het meten waard is. Zoia Baletska https://agileanalytics.nl/blog/cycle-time-vs-lead-time-waarom-het-verschil-telt https://agileanalytics.nl/blog/cycle-time-vs-lead-time-waarom-het-verschil-telt Thu, 18 Jun 2026 00:00:00 GMT Cycle time and lead time are often used interchangeably in Agile conversations, but they answer different questions — and mixing them up can create a lot of confusion. Cycle time measures how long it takes for work to be completed once someone starts working on it. Lead time measures how long it takes from the moment work is requested until it reaches production or the customer. That difference sounds small, but it changes the story entirely. Zoia Baletska https://agileanalytics.nl/blog/blinde-vlekken-in-agile-data-wat-u-niet-ziet-in-jira https://agileanalytics.nl/blog/blinde-vlekken-in-agile-data-wat-u-niet-ziet-in-jira Thu, 11 Jun 2026 00:00:00 GMT Ontdek verborgen afhankelijkheden, onzichtbaar werk en leemtes in Jira-data die uw metrics vertekenen en planning en levering minder voorspelbaar maken. Zoia Baletska https://agileanalytics.nl/blog/de-verborgen-metrics-die-agile-teams-missen-en-waarom-velocity-alleen-niet-genoeg-is https://agileanalytics.nl/blog/de-verborgen-metrics-die-agile-teams-missen-en-waarom-velocity-alleen-niet-genoeg-is Thu, 04 Jun 2026 00:00:00 GMT Your sprint dashboard shows 85% of story points completed. The burndown chart looks healthy. But features still miss deadlines. Tech debt grows. Your team is exhausted. What's wrong? You have data everywhere — Jira is full of it, dashboards track everything, retrospectives are always scheduled. Yet somehow, you're drowning in visibility but starving for insight. Zoia Baletska https://agileanalytics.nl/blog/flowgezondheid-wat-ticketleeftijd-onthult-over-uw-leveringssysteem https://agileanalytics.nl/blog/flowgezondheid-wat-ticketleeftijd-onthult-over-uw-leveringssysteem Thu, 28 May 2026 00:00:00 GMT Most teams monitor throughput. They know how many tickets were completed this sprint, how many story points moved across the board, and how many releases happened last month. Those numbers are easy to surface and easy to compare over time. The problem is that they often describe output without saying much about the condition of the system producing it. Zoia Baletska https://agileanalytics.nl/blog/5-praktische-stappen-om-trage-releasecycli-aan-te-pakken https://agileanalytics.nl/blog/5-praktische-stappen-om-trage-releasecycli-aan-te-pakken Thu, 21 May 2026 00:00:00 GMT Most teams notice slow release cycles long before they can explain them. Features take longer to reach production than expected. Work sits in review queues for days. Releases become stressful enough that teams start avoiding them unless absolutely necessary. Eventually, delivery slows down to the point where planning becomes guesswork because nobody is confident about when work will actually ship. Zoia Baletska https://agileanalytics.nl/blog/ai-observability-in-ontwikkelworkflows-wat-onderzoek-laat-zien https://agileanalytics.nl/blog/ai-observability-in-ontwikkelworkflows-wat-onderzoek-laat-zien Thu, 14 May 2026 00:00:00 GMT AI has quietly settled into everyday development work. It shows up in code reviews, pull requests, documentation, and all the small decisions that keep things moving. What’s still missing, in many cases, is a clear understanding of what it’s actually doing there. A recent paper, AI Observability for Developer Productivity Tools: Bridging Cost Awareness and Code Quality, takes a closer look at that gap. Zoia Baletska https://agileanalytics.nl/blog/agile-als-platform-hoe-het-langzaam-wordt-uitgehold https://agileanalytics.nl/blog/agile-als-platform-hoe-het-langzaam-wordt-uitgehold Thu, 07 May 2026 00:00:00 GMT Agile was introduced as a way to reduce friction, not create new layers of it. Teams adopted it because it helped them move faster, make decisions closer to the work, and respond to change without waiting for permission. For a while, that promise held up. Delivery improved, collaboration felt more natural, and processes stayed lightweight enough to adjust when needed. Zoia Baletska https://agileanalytics.nl/blog/platform-engineering-behandel-uw-platform-als-product https://agileanalytics.nl/blog/platform-engineering-behandel-uw-platform-als-product Thu, 30 Apr 2026 00:00:00 GMT For a long time, internal platforms were treated as infrastructure. Something you built once, maintained quietly, and expected teams to adapt to. If things worked, nobody noticed. If they didn’t, developers found workarounds. That model doesn’t hold up anymore. Zoia Baletska https://agileanalytics.nl/blog/embedded-vs-platform-vs-gecentraliseerde-sre-welke-aanpak-schaalt-echt https://agileanalytics.nl/blog/embedded-vs-platform-vs-gecentraliseerde-sre-welke-aanpak-schaalt-echt Thu, 23 Apr 2026 00:00:00 GMT As systems grow, reliability stops being something a few engineers can “keep an eye on” and turns into a structural concern. Incidents become harder to trace, dependencies less obvious, and small failures start to cascade in ways that weren’t visible before. At that point, the question is no longer how to improve reliability, but how to organise for it. Zoia Baletska https://agileanalytics.nl/blog/agileex-meten-teamervaring-naar-actiegerichte-inzichten-voor-agile-succes https://agileanalytics.nl/blog/agileex-meten-teamervaring-naar-actiegerichte-inzichten-voor-agile-succes Thu, 16 Apr 2026 00:00:00 GMT Agile transformations rarely fail because teams don’t follow ceremonies. They fail quietly, over time, when the experience of working within the system becomes frustrating, slow, or disconnected from outcomes. That experience — how teams plan, build, release, and improve — is what we call AgileEx (Agile Experience). Zoia Baletska https://agileanalytics.nl/blog/slos-afstemmen-op-de-gebruikerservaring-verder-dan-uptime-en-latency https://agileanalytics.nl/blog/slos-afstemmen-op-de-gebruikerservaring-verder-dan-uptime-en-latency Thu, 09 Apr 2026 00:00:00 GMT Service Level Objectives are often presented as a way to bring clarity to reliability. In practice, many teams end up tracking what is easiest to measure rather than what is most meaningful. Uptime percentages and latency percentiles look precise on dashboards, yet they can give a false sense of confidence. A service can be “up” and still fail users in ways that matter—checkout flows that break halfway through, reports that arrive too late to be useful, or APIs that technically respond but return incomplete data. Zoia Baletska https://agileanalytics.nl/blog/5-praktische-stappen-om-software-delivery-te-verbeteren-zonder-extra-proces https://agileanalytics.nl/blog/5-praktische-stappen-om-software-delivery-te-verbeteren-zonder-extra-proces Thu, 02 Apr 2026 00:00:00 GMT Software delivery rarely fails because teams don’t work hard enough. More often, the issue is a lack of clarity: where time is going, what is slowing things down, and which changes actually improve outcomes. Zoia Baletska https://agileanalytics.nl/blog/slos-opstellen-die-ontwikkelaars-serieus-nemen https://agileanalytics.nl/blog/slos-opstellen-die-ontwikkelaars-serieus-nemen Thu, 26 Mar 2026 00:00:00 GMT Service Level Objectives (SLOs) have become a standard part of modern reliability engineering. They are supposed to help teams make informed decisions about reliability, prioritise work, and balance speed with stability. Yet in many organisations, SLOs exist only on paper. They live in dashboards that nobody checks or in documentation that nobody remembers writing. Developers continue shipping features, operations teams continue firefighting incidents, and the SLOs quietly drift out of relevance. Zoia Baletska https://agileanalytics.nl/blog/slos-voor-interne-services-wat-te-meten-als-u-geen-gebruikers-heeft https://agileanalytics.nl/blog/slos-voor-interne-services-wat-te-meten-als-u-geen-gebruikers-heeft Thu, 12 Mar 2026 00:00:00 GMT Service Level Objectives (SLOs) are a cornerstone of modern reliability engineering. They help teams understand, measure, and maintain the reliability of the services they build. For public-facing services, this is usually straightforward: uptime, latency, error rates, or user satisfaction can all serve as meaningful indicators. But what happens when your service doesn’t have external users? Internal microservices, background jobs, data pipelines, and internal business systems still power your operations — but traditional user metrics don’t exist. Zoia Baletska https://agileanalytics.nl/blog/features-vs-non-features-ratio-thinking-pies-begrijpen https://agileanalytics.nl/blog/features-vs-non-features-ratio-thinking-pies-begrijpen Thu, 05 Mar 2026 00:00:00 GMT In software development, not all work is created equal. The ratio of features to non-features — the features/non-features ratio, or what we sometimes call the “thinking pies” — can be surprisingly telling about how your team is spending its cognitive and operational bandwidth. Zoia Baletska https://agileanalytics.nl/blog/slos-in-cloud-native-en-gedistribueerde-architecturen https://agileanalytics.nl/blog/slos-in-cloud-native-en-gedistribueerde-architecturen Thu, 26 Feb 2026 00:00:00 GMT As organisations scale, their software platforms become increasingly distributed. Services are no longer isolated — they communicate, depend on each other, and often operate across different teams, cloud regions, and technology stacks. While this architecture improves scalability and resilience, it also complicates reliability management. Zoia Baletska https://agileanalytics.nl/blog/slo-dashboards-die-een-verhaal-vertellen-wat-visualiseren-en-wat-vermijden https://agileanalytics.nl/blog/slo-dashboards-die-een-verhaal-vertellen-wat-visualiseren-en-wat-vermijden Thu, 19 Feb 2026 00:00:00 GMT Most SLO dashboards answer a single question: “Did we meet the SLO?” Unfortunately, that’s also the least useful question you can ask. Great SLO dashboards don’t just report compliance. They tell a story — one that helps engineering, product, and leadership make better decisions. Zoia Baletska https://agileanalytics.nl/blog/wanneer-ai-niet-helpt-valkuilen-valse-positieven-en-vroege-detectie https://agileanalytics.nl/blog/wanneer-ai-niet-helpt-valkuilen-valse-positieven-en-vroege-detectie Thu, 12 Feb 2026 00:00:00 GMT n the previous articles in this series, we explored how to measure AI adoption, how to track output and quality, how AI affects developer experience, and how to combine those signals into a responsible AI impact dashboard. This article focuses on the less comfortable side of the story: what happens when AI doesn’t help — and how to detect that early, before damage accumulates. Zoia Baletska https://agileanalytics.nl/blog/ai-impact-dashboard-bouwen-zonder-vertrouwen-of-teams-te-schaden https://agileanalytics.nl/blog/ai-impact-dashboard-bouwen-zonder-vertrouwen-of-teams-te-schaden Thu, 05 Feb 2026 00:00:00 GMT By now, most software organisations have accepted a simple truth: AI is everywhere in development — whether leadership tracks it or not. What’s still missing in 2025 is not tooling, but coherence. Zoia Baletska https://agileanalytics.nl/blog/devex-vs-space-developer-experience-meten https://agileanalytics.nl/blog/devex-vs-space-developer-experience-meten Thu, 29 Jan 2026 00:00:00 GMT In the rapidly evolving world of software development, the old notion of “productivity = more code” is long dead. Modern engineering teams recognise that sustainable performance depends not just on output, but on the developer experience (DevEx) that underlies it. Two influential frameworks have emerged to help teams think about this holistically: SPACE and DevEx. Each offers a structured way to capture what matters — but they serve slightly different purposes and deliver different insights. Zoia Baletska https://agileanalytics.nl/blog/developer-experience-en-langetermijngezondheid-ai-impact-burnout-vaardigheidsgroei https://agileanalytics.nl/blog/developer-experience-en-langetermijngezondheid-ai-impact-burnout-vaardigheidsgroei Thu, 22 Jan 2026 00:00:00 GMT AI tools don’t just change how code is written — they change how developers think, learn, and experience their work. And those effects rarely show up in PR metrics or dashboards until it’s too late. This article focuses on Developer Experience (DevEx) and long-term team health — measuring whether AI adoption is sustainable over time, or quietly increasing burnout, cognitive load, and skill erosion beneath the surface. Zoia Baletska https://agileanalytics.nl/blog/output-metrieken-code-doorvoer-en-kwaliteit-met-ai https://agileanalytics.nl/blog/output-metrieken-code-doorvoer-en-kwaliteit-met-ai Thu, 15 Jan 2026 00:00:00 GMT AI tools can help developers write code faster, suggest tests, and even automate parts of code review. But speed alone isn’t enough. Without measuring output quality, faster code could just mean more bugs, rework, or hidden technical debt. In this article, we explore practical techniques to track engineering output metrics, ensuring that AI actually improves productivity without compromising maintainability. Zoia Baletska