Boek een demo

Platform

Voor engineering leiders

Voor softwarebedrijven

Prijzen

Contact

Inzichten

Docs

Login

1080_logo-agile-analytics.webp

1200_logo-agile-analytics.webp

1920_logo-agile-analytics.webp

2048_logo-agile-analytics.webp

256_logo-agile-analytics.webp

384_logo-agile-analytics.webp

640_logo-agile-analytics.webp

750_logo-agile-analytics.webp

828_logo-agile-analytics.webp

thumbnail_logo-agile-analytics.webp

logo-agile-analytics.webp

Logo Agile Analytics

Inschrijven

Schrijf je in voor de Agile Analytics-nieuwsbrief

Cost per accepted change: wat kost een wijziging die niet wordt teruggedraaid?

Meer commits, meer pull requests, meer deploys: zet AI-tooling aan en alle tellers staan hoger. Geen van die tellers zegt of het beter gaat. Eén getal wel: wat het kost om één wijziging door de review naar productie te krijgen zonder dat hij wordt teruggedraaid. Zo haal je het uit Git en CI.

DORA vs SPACE: welk metrics-framework heb je nodig?

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.

Pluralsight Flow wordt uitgefaseerd. Dit is wat er nu gebeurt.

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.

Iteratiesnelheid: wat snelle teams echt meten

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.

Cycle time vs. lead time: waarom het verschil telt

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.

Blinde vlekken in Agile-data: wat u niet ziet in Jira

Verborgen afhankelijkheden en onzichtbare blockers

De verborgen metrics die agile teams missen (en waarom velocity alleen niet genoeg is)

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.


Flowgezondheid: wat ticketleeftijd subtiel onthult over uw leveringssysteem

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.

5 praktische stappen om trage releasecycli aan te pakken

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.

AI Observability in ontwikkelworkflows: wat recent onderzoek echt laat zien

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.

Agile als platform: hoe het langzaam wordt uitgehold

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.

Platform engineering: behandel uw platform als een product

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.

Embedded vs Platform vs Gecentraliseerde SRE — Welke aanpak schaalt echt?

 

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.

AgileEx meten: teamervaring vertalen naar actiegerichte inzichten voor Agile-succes

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).

SLO's afstemmen op de gebruikerservaring — verder dan uptime en latency

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.

5 praktische stappen om software delivery te verbeteren (zonder extra proces)

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.

Zo stelt u SLOs op die ontwikkelaars echt serieus nemen

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.

SLOs voor interne services — wat te meten als u geen gebruikers heeft

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.

Features vs non-features-ratio: uw “thinking pies” begrijpen

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.

SLOs in cloud-native en gedistribueerde architecturen

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.

SLO dashboards die een verhaal vertellen: wat visualiseren — en wat vermijden

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.

Wanneer AI niet helpt — valkuilen, valse positieven en hoe u ze vroegtijdig herkent

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.

Alles bij elkaar — zo bouwt u een AI-impact-dashboard zonder vertrouwen of teams te schaden

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.

DevEx vs. SPACE: Developer Experience op de juiste manier meten

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.

Developer Experience & langetermijngezondheid: de impact van AI‑adoptie op burnout en vaardigheidsgroei meten

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.

Output-metrieken — hoe u code-doorvoer en kwaliteit nauwkeurig meet met AI

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.

AI-adoptie en toolgebruik meten — wat u bijhoudt voordat u code schrijft

AI tools are increasingly embedded into developers’ daily workflows — from IDE autocomplete and chat-based assistants to AI-powered pull-request reviews and test generation. But before you try to measure whether AI improves productivity, quality, or Developer Experience, there’s a more basic question you must answer:
Are developers actually using AI — and how?

Kunt u de AI-impact op ontwikkelaars echt meten? Een praktisch framework

AI-assisted coding tools (like Copilot, AI pull-request reviewers, automated test generators, etc.) are becoming widely adopted — but the evidence for their impact on productivity and developer experience remains mixed. Some recent studies show improvements, others show no change or even slowdowns. 

Agile-astrologie: wanneer uw burndown chart samenvalt met Mercurius retrograde

Agile is all about data… but sometimes, no matter how many dashboards we build, the team still behaves like their destiny is written in the stars. So today, let’s embrace a more cosmic approach to engineering analytics:
Agile Astrology — where your metrics reveal everyone’s secret zodiac sign. Is it scientific? Absolutely not.
Is it more accurate than your last sprint estimate? Almost definitely.

Psychologische veiligheid is een engineering-metriek — dit is het bewijs

Most Agile teams obsess over velocity, burndown charts, sprint goals, ceremonies, tooling, and frameworks. Yet a quiet story that recently surfaced on Reddit reveals something far more fundamental: “Agile doesn’t break when the process is wrong. It breaks when people feel like they can’t be honest.” In the post, a team looked perfect from the outside—standups were quick, the board was active, and everyone confidently nodded through planning. It seemed efficient.

Als continuous delivery niet kan: hoe teams toch de Developer Experience verbeteren

Continuous delivery has become the holy grail in modern software development. The idea of shipping value to customers multiple times a day, collecting immediate feedback, and iterating rapidly is compelling. But for many software teams—particularly in hardware-heavy, regulated, or legacy-heavy domains—full continuous delivery (CD) is simply not feasible.

Weg met de dagelijkse blokkades: data-gedreven manieren om uw ontwikkelaars vrij te maken

Every team has them — the daily blockers.
They show up in standups as “still waiting on access,” “tests are flaky again,” or “need someone to review my PR.”
Individually, each seems small. But collectively, they erode flow, focus, and morale.

The truth: most developer blockers aren’t random. They’re measurable, repeatable patterns — and that means they can be killed with data.

De realiteit achter AI voor ontwikkelaars: prompting in de praktijk

Generative AI is no longer a novelty in development. Tools like Copilot, ChatGPT, and others are deeply embedded in many engineering workflows. But how exactly do developers use them, how reliable are they, and what patterns of prompting and conversation actually help produce useful code? That’s what this recently published paper by Daniel Otten, Trevor Stalnaker, Nathan Wintersgill, Oscar Chaparro & Denys Poshyvanyk set out to discover. 

Hoe Meet Je de DevOps Teamprestaties met DORA Metrics en Wat Daarna? 

Ontdek hoe je met DORA metrics de prestaties van je softwareteams kunt verbeteren. Leer meer over de voordelen, beperkingen en wat je na DORA kunt meten voor nog betere resultaten

Leer hoe Engineering Intelligence Platforms de IT-kosten kunnen verlagen en de productiviteit van ontwikkelaars kunnen verhogen

De constant stijging van jaar-op-jaar IT-uitgaven is onmiskenbaar, waarbij bedrijfssoftware een groot deel van de budgetten opslokt. Maar wat als u meer zou kunnen bereiken met minder middelen? In dit artikel leggen we uit hoe een Engineering Intelligence Platform (EIP) de IT-kosten kan verlagen en de tevredenheid en productiviteit van ontwikkelaars kan verhogen. We beschrijven hoe EIP's ontwikkelaars in staat stellen om inefficiënties te verwijderen en productiviteit te verbeteren.

Hoe Google Succesvol Software Ontwikkelt: Belangrijke Lessen Uit 'Software Engineering at Google'

Softwareontwikkeling is meer dan alleen code schrijven. Bij grote techbedrijven zoals Google gaat het om het bouwen van een cultuur, processen en tools die teams in staat stellen om schaalbaar, efficiënt en betrouwbaar software te leveren. 

Het geheime ingrediënt van de Agile Teams van Praxis.nl 

De transformatieve reis van Praxis.nl , onderdeel van de Maxeda DIY-groep begon in 2018. Tussen 2018 en 2021 onderging Praxis.nl  een Agile- en Cloud-transformatie, waarbij de online digitale teams volledig werden vernieuwd. 

Team-gebaseerde rapportage met Agile Analytics 

Onze nieuwste functie, "Teams Reporting", is er! Hiermee krijg je in één oogopslag alle belangrijke metrieken te zien voor elk team! 

Nieuwe Europese cybersecurityregels komen eraan! Meer aansprakelijkheid voor de bedrijfsleiding

Recent legal developments in Europe in the Cyber security field are set to impact businesses throughout Europe, particularly those involved in software development. With stricter regulations on the horizon, The NIS2 Directive is the EU-wide legislation on cybersecurity (The EU cybersecurity rules introduced in 2016 were updated by the NIS2 Directive).

Traditionele Analytics of Agile Analytics: welke past het beste bij jou?

In dit artikel verkennen we de belangrijkste verschillen tussen Agile Analytics en Traditionele Analytics. Zo krijg je een overzicht en kun je beter bepalen welke vorm van analytics het beste bij jou past.

Wat DORA-gegevens kunnen onthullen over de prestaties van uw team

Heb je je ooit afgevraagd hoe snel je code gaat van "Ik heb een idee" naar **"Boem, het is live"**? Dat is waar *Doorlooptijd voor wijzigingen* om de hoek komt kijken – het is als de snelheidsmeter van je code. Wil je ontdekken of je codeaanpassingen zo snel gaan als de Flash, of ga je liever een rustig wandelingetje maken? In de wereld van coderen is het vinden van het juiste ritme essentieel!

Wat zijn Service Level Objectives (SLO's) en waarom zou ik ze meten?

Heb je je ooit afgevraagd waarom sommige softwaretoepassingen beter presteren dan andere? Het antwoord is eenvoudig: ze hebben goed gedefinieerde Service Level Objectives (SLO's).

Machine-learningalgoritmen gebruiken om prestaties te meten

Zoals het gezegde luidt: "You can't manage what you can't measure". Dit geldt vooral voor softwareontwikkeling, waar het succes van een project afhangt van de prestaties van het ontwikkelteam. Maar wees niet bang! Machine learning is er om te helpen.

Van rijkdom naar armoede: Hoe gelekte privésleutels leidden tot de verdwijning van Code Spaces

In de wereld van softwareontwikkeling vormen beveiligingslekken een voortdurende bedreiging. In juni 2014 werd een bedrijf het slachtoffer van een kwaadaardige cyberaanval die uiteindelijk tot de ondergang leidde. Dit waarschuwende verhaal herinnert ons eraan hoe belangrijk het is om gevoelige informatie te beschermen en benadrukt de noodzaak van Agile Analytics om dergelijke risico's te beperken.

Geen handmatig gedoe meer! Automatiseer uw niet-functionele metingen voor maximale efficiëntie!

Softwarekwaliteit gaat verder dan functionaliteit. Niet-functionele aspecten zoals **prestaties**, **betrouwbaarheid** en **veiligheid** zijn cruciaal. Ons Agile Analytics SaaS-platform biedt een uitgebreide oplossing om deze dimensies effectief te beheren en te meten. Door gebruik te maken van DORA-metrics en SRE Error Budgets kunnen teams de inzet, betrouwbaarheid en beveiliging optimaliseren, terwijl ook de softwarevoorraad wordt bewaakt en gelekte privésleutels worden opgespoord.

Autonomie omarmen met Agile Analytics: “You build it, you run it”

In 2006 introduceerde Werner Vogels, de CTO van Amazon, de inmiddels beroemde mantra "You build it, you run it", die sindsdien een leidend principe is geworden voor veel organisaties. Deze filosofie moedigt teams aan om eigenaar te worden van de producten die ze ontwikkelen en bevordert een gevoel van autonomie en verantwoordelijkheid.

Meer functies duurzaam geleverd krijgen: net zo eenvoudig als verbinding maken met Jira

Softwareontwikkelaars vinden de ontwikkeling van nieuwe functies vaak het leukste aspect van hun werk. Ze kunnen er hun creativiteit in kwijt, interessante problemen oplossen en tastbare resultaten afleveren. Bovendien is de primaire focus van de producteigenaar van het team meestal gericht op het toevoegen van nieuwe functies aan het product, omdat ze geloven dat dit is wat klanten willen en wat inkomsten zal genereren.

Stop met gissen, begin met meten in uw Quality Gate Meetings

Kwaliteitspoorten dienen als controlepunten of mijlpalen binnen de levenscyclus van softwareontwikkeling om ervoor te zorgen dat aan specifieke kwaliteitscriteria wordt voldaan voordat wordt doorgegaan naar de volgende fase. Maar al te vaak zien we dat, terwijl het proces wordt geïmplementeerd, de gegevens die op tafel worden 'gebracht' niet empirisch zijn. We zien veel HiPPO-gedrag (Highest Paid Person's Opinion) tijdens deze vergaderingen. Wij denken dat we daar een oplossing voor hebben!

Een schuldloos postmortaal proces opzetten in 7 stappen

Een post-mortem is een retrospectieve analyse van een incident of storing in een softwaresysteem. Een post-mortem heeft als doel de hoofdoorzaak van het probleem te identificeren, de reactie op het incident te evalueren en een plan te ontwikkelen om soortgelijke incidenten in de toekomst te voorkomen door het softwaresysteem of de processen te verbeteren.

Hoe de productiviteit van softwareontwikkeling meten

Naarmate de software-ontwikkelingsindustrie groeit, wordt het steeds belangrijker om de effectiviteit van je team en de software die ze produceren te meten. Dit is waar Agile Analytics om de hoek komt kijken, met waardevolle inzichten in de productiviteit van softwareontwikkeling.
Het meten van productiviteit kan een uitdaging zijn, maar het is cruciaal om ervoor te zorgen dat je team effectief werkt en software van hoge kwaliteit aflevert.

Wat is agile?

Agile, Scrum en Kanban zijn populaire methodologieën voor softwareontwikkeling en projectmanagement. Elke aanpak heeft unieke kenmerken, maar ze hebben allemaal een gemeenschappelijk doel: het ontwikkelingsproces efficiënter en effectiever maken.

Hoe je de effectiviteit van een DevOps-team kan meten

Vraagt u zich wel eens af of uw softwareontwikkelingsteam wel zo efficiënt mogelijk werkt? Het meten van productiviteit bij softwareontwikkeling kan ontmoedigend zijn, maar het is van cruciaal belang om ervoor te zorgen dat je team optimaal werkt. Gelukkig kunnen we je helpen. We gaan in op concrete manieren om de productiviteit van softwareontwikkeling te meten en op de verschillende meetmethoden en tools die daarvoor kunnen worden gebruikt.

Hoe ChatGPT de prestaties van uw softwareontwikkelingsteam verbetert

Software development can be tough. With tight deadlines, many lines of code to write, and countless bugs to fix, it can feel like a never-ending uphill battle. But thankfully, ChatGPT is coming to the rescue to level up your team’s performance. Luckily ChatGPT is a much better coder than a poet.

Agile werkt niet...

> Agile doesn't work...

I hear it more and more.
When I use root cause analysis to find out what the problem is, it's usually due to a combination of:

1. An Agile implementation that's not very agile.
2. No metrics in place to measure success or improvements.

3 manieren waarop technische schuld uw bedrijf raakt

When a software project has to be quickly completed and delivered, despite the code not being perfect, your team is assuming technical debt to meet the deadline. In their haste to deliver software capabilities, developers sometimes engage in less-than-optimal coding practices, or ‘forget’ to test or document parts of the software. 

We zijn niet hetzelfde: Developer Experience (DX) managen

If you have any internal development tools, platforms or services in your organisation that you found super easy and pain-free to onboard, then you are lucky! 
Put yourselves in your users' shoes.

Gebruik DORA-metrics ter ondersteuning van remote werken

When teams are not co-located engagement and performance issues can easily spin out of control. DORA metrics are critical when working in a hybrid or fully remote work model. Whether you’re ready to move past the hybrid midpoint or are taking the direct leap to remote, here’s why you need DORA metrics at your side.

ZEN Software’s Agile Analytics nu beschikbaar op de Atlassian Marketplace

ZEN Software proudly announces that we are accepted as Atlassian Partner for our flagship product. Agile Analytics is a time-saving analytics platform for Development Managers, Agile Coaches and Project Managers. 

Agile Analytics is a comprehensive data analytics and reporting tool based on the data from Atlassian Jira Cloud.

Know everything about your projects:

- Use Agile Analytics to see how each team is spending their time.
- Know the status of all your tasks.
- Understand which skills you need to hire or train.

Wat is een Developer Portal?

Voor development management is de uitdaging: teamautonomie behouden, terwijl u bepaalde processen centraliseert en één "single pane of glass" creëert voor zowel management als teams. Behoud de performance door onnodige rompslomp en toil (repeterend handmatig beheerwerk) zoveel mogelijk te schrappen of te automatiseren.

Team Topologies – de Reverse Conway Manoeuvre

From the book [“Team Topologies”](https://partner.bol.com/click/click?p=2&t=url&s=1228221&f=TXL&url=https%3A%2F%2Fwww.bol.com%2Fnl%2Fnl%2Ff%2Fteam-topologies%2F9200000104858740%2F&name=Team%20Topologies) by Matthew Skelton and Manuel Pais comes an interesting fix to Conway’s Law: 

Wat zijn DORA metrics en waarom zijn ze belangrijk

How do you know what performance of your software development organisation is? How do you prevent your engineers from getting frustrated, leaving, overworked or burnt out while at the same time get fair metrics on the performance of the team(s)?

Hoe begint u met SRE?

As part of the Data Science trajectory at Young Mavericks, ZEN Software provided an introduction to Multi-Cloud. How can you use cloud in Data Science and what choices are there in the field of Cloud as a toolset.

Zo zet u een succesvol Cloud Platform Team op

Most organisations have centralised (Cloud) platform teams (or they should). Setting up these teams is a fun challenge but a challenge nonetheless. In 2019  Matthew Skelton and Manuel Pais published their book [“Team Topologies”](https://partner.bol.com/click/click?p=2&t=url&s=1228221&f=TXL&url=https%3A%2F%2Fwww.bol.com%2Fnl%2Fnl%2Ff%2Fteam-topologies%2F9200000104858740%2F&name=Team%20Topologies). They share the secrets of successful team patterns and interactions to help readers choose and evolve the correct team patterns for their organisation, ensuring that the software is healthy and optimises value streams.

Wat zijn Error Budgets?

**Introduction**

Error Budgets enable a large amount of autonomy for your software teams. these feature teams can steer priority based on the level of service that is currently being offered to stakeholders. This article will explain the basics of the concepts that enable Error Budgets. Furthermore it will demonstrate how to implement it using ZEN Software’s Agile Analytics.

When implementing Error Budgets for your teams a number of things needs to be setup up in both the team culture as well as in the tools. 


ZEN Software lanceert Agile Analytics Cloud

After 30 months of coding, designing, debating and bugfixing we’re proud and happy to announce we are releasing Agile Analytics to the general public!
 

Agile Analytics is now GA
Why should your organisation use Agile Analytics?

**For Development Managers**
- Match or challenge gut feeling with real data
- Reward collaborative behaviour
- Manage Developer Experience (DX)

**For Teams & Agile Coaches**
- Improve autonomy: Make decisions for yourselves
- OKR /  SLA : promise vs reality
- Actionable & real-time performance data:  ‘how are we really doing?’

Kubernetes is geen wondermiddel

**Why Docker?**

At ZEN Software we see docker as a Configuration Management innovation. Docker solves a number of frustrating developer problems. Docker improves both the productivity and reliability of a software system. 

Docker does this by:

1. Removing all the dependency nightmares that cause production environments to be different from development environments.
2. Increasing the efficiency of packaging and deployment (both in terms of size and time)
3. Improves developer productivity — especially the inner loop of Edit -> Build -> Debug

All excellent goals to achieve, and largely accomplished.

De 10x-ontwikkelaar

Meet *‘Gilfoyle’*; Gilfoyle lives inside HBO’s comedy series ‘Silicon Valley’. This series portrays a number of fictional silicon valley companies and mainly: Pied Piper. Pied Piper is the startup company where the main characters of the show (Richard, Gilfoyle, Dinesh and Jared) strive for world dominance with their new products.

Gilfoyle and Dinesh are developers. The way they are portrayed in the series is spot on if you consider the 3 virtues of a programmer:

- Laziness, 
- Impatience,  
- Hubris



Wat is Site Reliability Engineering (SRE) en hoe verschilt het van DevOps

Both DevOps and Site Reliability Engineering (SRE) promise to improve integration between Development and Operations (DevOps) and resiliency in organisations. However, many in our field remain unfamiliar with DevOps and SRE concepts, making it difficult to implement these methods, hire or train for DevOps and SRE roles.

SRE and DevOps are very complementary practices. When implementing both, they accelerate the movement toward continuous delivery. 

Lean & DevOps implementeren met bedrijfsromans?

In 1984 Eliyahu Goldratt and Jeff Cox innovated the world of business books by writing an implementation guide to Lean as a novel. Previously this had not been done successfully. Since the success of ‘The Goal’ there have been 2 successful attempts to recreate Business Novels for IT and Software Development. Gene Kim wrote ‘The Phoenix Project’ in 2013 and the companion book ‘The Unicorn Project’ in 2019 as a hommage to ‘The Goal’ and as a way to use business fiction to implement DevOps. These books try to be a novel/story and “best practices” business book while also showing some key issues and problems with large corporations.

De effecten van Machine Learning op de zoekbalk van uw site

Personally, I don’t like the so-called “Silicon Valley Inspirational trips”. Don’t get me wrong: they sound like fun but going there just for inspiration seems a bit forced. Then: what do you call it when you happen to be in San Francisco, you are in the software business and you get ‘inspired’?  :wink:

This is what happened to me when I was in San Francisco in April 2019 to give a talk about Maxeda, Cloud Transformation and all the cool things we did there. “Since we’re already in SF” we decided to meet up with the cool team from [Constructor.io](https://constructor.io/). (see photo)

Gebruik Gitflow, verantwoord

Version control was and perhaps always will be a subject of debate. It seems at times we are in a search for a singular "best' way to manage versions of code under all circumstances. Since about 2008 git has increased popularity significantly and is the most popular version control system since 2012. This meant a new round of debate on how to use the most popular version control system at the time: git. Since it is 2017 now, has the dust settled, and are there any conclusions?


Inzichten over DORA, SLO’s, DevEx en AI

DORA-metrics en flow

SLO’s, error budgets en SRE

Developer experience

De impact van AI meten

Alle artikelen

Minder gokken. Meer opgeleverde software.