Skip to the essays

Improving the world with software

Better software. Better questions.

Essays on software development, teams and the craft of building things that last.

Essays, page 21

314 essays in the archive

  1. Understanding schedule and scope in Agile projects.

    Here is an example of something that the software world needs to improve. In his blog post from January 4th, James shore talks about software project estimation. He describes a waterfall project with 4 milestones and asks the reader to guess how much that software will be late based on the information he gives. Here’s …

    5 min read

  2. Use your brain (not tools to replace it!)

    Here’s a good post about a tendency that I’ve seen several times repeated in the Software development industry. The point in the article is short and sweet: if you are doing TDD you should write your tests yourself. Don’t use tools to generate tests for you unless you understand exactly why and what the savings/efficiency …

    1 min read

  3. Function follows form… or results depend on team structure

    Dave Nicolette touches upon a subject that has been in my mind lately. Roles, do matter in a software development team. Quoting Conway’s law: the software produced will look like the organization that produced it. Why is this important in the context of Agile teams? Because, if your organizational structure mimics what it was when …

    1 min read

  4. Opening a new debate, our industry needs to grow…

    Agile development practices have caught on lately. Just look at the number of people attending what, some time ago, were “marginal” events like the ScrumGathering. The software industry as a whole is awaking to a new wave of “process improvement”. It’s important to look back in history and understand the previous waves in our industry …

    4 min read

  5. Why do teams slow down?

    So, here you are. You just joined a team, you’re the third or fourth member to join and you feel good. Your team follows an Agile development method. You churn out new functionality and customer-value at the end of every iteration and things could not go any better for you. The product sells, the team …

    1 min read

  6. Time is up for middle age conceptions of software development

    Sometimes it takes time for the full understanding of reality to fall on us. Scratch that. IT ALWAYS TAKES TIME, many times it takes too much time. David is contributing to shorten that itme in at least one item: the road is over for super-specialists in the software industry. You can and should still be …

    1 min read

  7. Agile brings organizational changes…

    David has a good analysis of one the most clear consequences of going Agile. Once the development bottlenecks are solved, the bottleneck moves elsewhere, and in many cases it moves to the organizational structure: read it here.

    1 min read

  8. Agile implemented with (real) roller skates

    Martin Fowler has a great example of what an agile mind would think of to deliver customer value much sooner than what people would normally think. Great example of what the Agile values are about!

    1 min read

  9. Joel on Software gets close to “a universal truth” software development

    The important phrase is at the end of this paragraph… Wow, That’s really on the spot. That’s exactly the same time we saw at our company (average of many projects) a validation/testing/debuging phase takes… when you use waterfall!!!! Lately we’ve got the period from “last feature added” to “release” in a lot less time (no …

    1 min read

  10. Nokia’s “door” (Ovi in Finnish)

    I can’t believe it! How can someone be so ignorant so out of touch with reality so complete absorved on their own petty little half-monopoly to have no clue whatsoever about what makes a web service usable, cool and desirable? Have you checked out Nokia’s Ovi (door in English)? talk about a crappy user experience. …

    2 min read

  11. A Demo-day smell

    While attending a team demo the other day I came accross what I consider a “smell”. A smell is like a sign that something is wrong (from “smells bad but I don’t know where it comes from). The smell is the following, teams get on stage to demo the results of the latest iteration and …

    2 min read

  12. Patterns of Agile adoption

    During XP 2006 in Oulu, Finland. I attended a session jointly hosted by Amr Elssamadisy and Ahmed El shamy on patterns of Agile adoption. There are now a few articles about that and other sessions that Amr has held in other conferences. You can check the paper on “Functional Testing: A Pattern to Follow and …

    1 min read

Keep the conversation going

The essays work best in company. Join the community to keep the questions coming.

The #NoEstimates book and its companion volumes

Chapter 1 · Free PDF

What if better planning started with a different question?

The first chapter of #NoEstimates argues that the “deliver on time” challenge is answered by a different question. Read it, and see whether it changes how you plan the next piece of work.

Free PDF of chapter 1. No purchase, no library access. How we handle your details