Sander Hoogendoorn

If I had to believe my LinkedIn timeline, agile is dead.

It is 2026.

A LinkedIn post about someone nearly losing six months of work on a single local branch is not a story about bad luck.

Refactoring isn't a favor you ask permission for.

A sleeper bus and a slowboat through Laos both left exactly on schedule and both arrived hours late.

Measuring developer productivity by counting commits works about as well as measuring air base activity by counting kerosene use — it just teaches people to dump kerosene.

A student asked whether it's still worthwhile to become a software developer in 2025.

A LinkedIn post questioning pull requests racked up 350,000 views and a bonfire of discussion.

Yesterday it happened again.

The Agile Manifesto was written by techies who wanted to improve software development.

In September 2003 I visited the friendly city of Arhus in Denmark to deliver a talk at the JAOO conference.

Software development leent zijn terminologie van de bouw en de fabriek — architectuur, bouwen, de lopende band.

When organizations map their traditional roles onto Scrum, the product owner slot usually gets filled by a former project manager or analyst — and quietly becomes the single-person bottleneck the team was supposed to get rid of.

A job ad for an 'agile project manager' who's also not afraid of running PRINCE2 projects.

Microservices is a hot topic.

Stel.

Verplicht leuk doen Enkele maanden geleden had een goede vriend een kennismakingsgesprek bij een gerenommeerde webwinkel.

Even though the year is still young and still cold, I have already presented two training courses.

Een organisatie die al zeven jaar Scrum doet belt voor een review, want ze zitten vast.

One of the great things about being a programmer is that you never stop learning.

In September 2016 I will do the closing keynote for SwanseaCon in Swansea, Wales.

It’s April and the sun is slowly becoming more powerful, warming the people in the green and white deck chairs in Green Park in London.

In 2009 I hired a building contractor to build a house.

Having coached many teams, projects and organizations on both software architecture and agile, one of the questions I’ve been asked a lot over the past fifteen years is: what is agile architecture?

In September I will run a masterclass on microservices at Luxoft in Moscow, Russia, see www.luxoft-training.ru/master-class/sander.

Earlier last week I was trying to refactor around two thousands lines of code, optimistically being convinced that the component could offer the exact same functionality in less than two hundred lines.

Back in 1988, when I was first employed by a company for writing software, the world was fairly simple.

If you, are working in technology, like me, there’s a chance that you live under the impression that our field changes faster than you can keep up with.

Over the past fifteen to twenty years I’ve been invited numerous times to help organization move from traditional to iterative and agile software development.

Agile hippies think all tools are evil.

Recently we’ve introduced Tags for work items on www.speedbird9.com .

There is an intriguing question that pops up frequently in organizations developing software in projects: when is a project successful?

www.speedbird9.com is an free open online agile and Kanban board, that allows you to monitor the progress in your projects – whether they are IT projects or not.

One of the key and often very much underestimated assets of working in agile teams, whether working on products or projects, is the idea of sustainable pace.

Many organizations turn towards agile to escape failing traditional software development.

While writing this post, I am on an airplane to Helsinki.

Due to the ever-rising demand for seasoned software developers in the nineties, offshore software development became a compelling alternative to in-house development for many organizations.

For as long as I can remember I have been evangelizing, promoting, practicing, coaching, and training agile.

When building applications with the Adf framework, smart use cases are implemented in task classes.

One of the requests we often get in projects that use the Adf.Net framework is to be able to get specific validation messages, especially when during persisting panels to domain objects, properties that have value objects as their type fail to persist, us…

Implementing use cases in Adf.Net is covered by the task pattern.

Het besparen van kosten is een veelgenoemde aanleiding voor Business Intelligence (BI) projecten.

Believe it or not, but I have a confession to make.

This month I hope to round off the work on my new book Dit Is Agile (in Dutch).

After a series of very disappointing games the Dutch national football team was eliminated during the preliminary rounds of the European Championships.

Over the years I have noticed a lot of agile anti-patterns during projects.

It must have been about twenty five years ago.

Without any doubt agile is the biggest evolution in software development approaches since the introduction of waterfall back in the early seventies.

I guess object relational mapping is an accepted paradigm for exchanging data between an object oriented domain layer and underlying databases.

Er is een anti-patroon op het gebied van agile dat me nauw aan het hart gaat.