Staying On Track – Video From AgileByExample 2014

There’s no point in driving faster in the wrong direction.


That’s why staying focused on what really matters during the whole the software development process is crucial. Which means  killing features that no one is going to use, shortening discussions and brining them back on track, and helping teams with difficult decisions (“Should we refactor this piece?”, “Should we allow deleting users?”, “What to work on next?” ) – I must admit I really enjoy this process 🙂

I gave a talk on this topic during the last AgileByExample 2014 conference.

Video and presentation slides are available.


Goodbye SoftwareMill. Time For New Challenges

Five years ago, together with my friends Tomek Szymański, Adam Warski and Jan Zborowski, I founded SoftwareMill.

SoftwareMill is a unique company – 26 awesome team members, all of them working remotely, flat structure with no managers and full financial transparency. I’m really proud of it.

That made the decision to leave an extremely hard one, but I feel it’s now time for me to look for new challenges. […]

Visibility Shift In Distributed Teams

“Distributed agile is hard” is what I often hear. And yes, after working remotely in various distributed teams for 8 years, I agree. But I am going to argue that this is a good thing.

Basically I believe that working in a distributed environment is like using Scrum – it does not solve your problems, but makes them more visible. I like to call this a “visibility shift”. […]

No Backlog Policy

I hate Product Backlogs’ unrestrained tendency to grow, get messy and unmaintainable.

Ideally, a Product Backlog should give the whole team a clear roadmap on work to be done. I remember times when I actually believed this is really possible, even with a huge Backlog, but in practice in every project I worked on I struggled with keeping the Backlog up-to-date, prioritised and consistent. […]

High-altitude Projects

Altitude sickness has taught me two important insights about speed and trends, which can be applied to software development projects (and probably many other areas as well). Altitude sickness After trekking above approximately 3,000 meters one has to take care not to climb too fast. The general rule is not to ascend more than 300 […]