The no sprint agile project

A sprint is defined as a limited period of time in which a number of features are created and added to an application or system. A sprint starts with a formal startup event and usually ends with a demonstration of what has been created in the sprint. What are the benefits of sprints?

Most articles quote “focus” as the main benefit of a sprint. I don’t see how sprints create focus, or how this “focus” helps the project. A project methodology should help create a product of higher quality with more features at lower cost. I don’t see how sprints contribute to this.

read on medium

How my cap table went wrong

I founded Tryllian in 1998, in Amsterdam. I had been working in AI for about ten years then, I was a pioneer in the use of the internet in business in the Netherlands, Tryllian combined both areas of expertise: we created chatbots that roamed the internet to communicate with one another.


Scrum: one size doesn’t fit all.

Scrum works fine in a project where small changes and updates are made in an existing application. But how does Scrum work when you build a new large application? This can be either a brand new application, or replacement of an old application. Think of it. You start the project, you have meetings on the over all architecture, on the frameworks you want to use, on the general philosophy of the GUI, and more. Scrum says you need to deliver your first feature after the first sprint. Even if you set sprint duration to one month, this is not a realistic goal. Scrum tells you to use the metaphore of the “minimum viable product”. But tell me, what parts of a skateboard or a bike can you re-use when you build the car?