Agile

  1. Agile vs Waterfall

    I have come to dislike “agile vs waterfall” discussions. “Agile vs waterfall” is a false dipole which leads to confusion about agile. The term “waterfall” is simply a description of a problematic, default approach to developing software.

    Continue reading

  2. A Couple of Thoughts About "Standard Agile"

    Lately I’ve been hearing a lot about standardization of Agile methodologies, and while some of the discussion may be well-intended, I feel the trend isn’t a healthy direction for the Agile movement. My concern is that it reveals a reverence for manufacturing which doesn’t help teams and managers when implementing Agile practices.

    Continue reading

  3. The Minimum Size of Value and Independence

    Recently I stumbled into a conversation with a client about the virtues of smaller stories when analyzing and estimating work. One business consultant asked a the question, “Have you found that there is confusion around people thinking that because a story should have business value and be independent that this means it is essentially impossible to break things down smaller than a minimum marketable feature?”

    Continue reading

  4. Agile Notes:
    Why Story Cards Matter

    Does writing formal story cards feel hokey? Although they may seem ceremonious, well-formatted story cards add critical value to the software development process. In this essay I’ve broken down the aspects and features I like to use/see on story cards…

    Continue reading