It’s quite ironic that my most “popular” tweet has been posted while Twitter itself is in such a chaotic phase. It’s also quite ironic that I try to provide helpful suggestions for doing a better job as a programmer, yet such a bitter tweet ends up to be so popular. Twitter and Mastodon are micro-blogging platforms. The problem with micro-blogs, and with short interactions in general, is that everybody can proceed to project onto your words whatever they like. So at some point I often feel the need to explain myself with more words, in an “actual” blog like this one.

This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant, and perhaps even some new items never before contemplated. Copyright © 1998-forever Ronald E Jeffries

When making estimations using story points didn’t feel helpful, a team decided to experiment with #NoEstimates. Breaking down stories into smaller tasks gives them insight into their velocity and has

There are myriad ways to optimize teams, but all too often we ignore the individual. When the individual is overlooked, the software production engine can be severely…

What if the Agile software movement was the manifestation of an entire industry that was, just, like, dealing with some stuff right now?

Modern Agile is four guiding principles that define a simpler, safer, speedier way to achieve awesome results. It has no roles, rituals or anointed practices. You choose how to act on the principles.

When the Manifesto for Agile Software Development was first published, it was not a process, but a set of guiding principles. Two of the core, foundational principles of agile development are reflection and continuous improvement. By creating tight feedback loops of iteration, analyzing the meta-process of product development, and constantly experimenting in order to improve communication and efficiency, these early agile teams were able to efficiently deliver high quality software while being able to quickly adapt to the shifting priorities of the business.

Continuous delivery is a set of principles, patterns, and practices designed to make deployments predictable, routine affairs that can be performed on demand at any time. This article introduces continuous delivery, presents both common objections and actual obstacles to implementing it, and describes how to overcome them using real-life examples. Continuous delivery is not magic. It

Michael Wolfe's answer: Let's take a hike on the coast from San Francisco to Los Angeles to visit our friends in Newport Beach. I'll whip out my map and draw our route down the coast: The line is about 400 miles long; we can walk 4 miles per hour for 10 hours per day, so we'll be there in 10 da...

[Pubblicato originariamente in lingua inglese su Medium il 25 agosto 2016] “FAIL FAST” è probabilmente l’espressione più abusata nell’ambiente startup: imparare dai propri errori e iterare velocemente sul prodotto dovrebbe essere il modo migliore per avvicinarsi al successo. Quando si tratta di mett

The following is a story about how we matured as an engineering team. We went from an ad-hoc process to Scrum, and used Scrum for a whole year. Scrum leveled us up as a team in terms of structure and…