Blog

You hear it at the conference, in the session with the performance consultant. It all sounds so helpful. She points out that you already have functional test automation. Those run through realistic scenarios, end to end. So put them on a grid, maybe in the cloud, then use them as

The Agile Manifesto has twelve principles, that include “Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.” For its time, the Manifesto was revolutionary. Today, that speed seems quaint. Agile Machismo has taken over, with one-week sprints better than two,

If you have a secret hobby of arguing over words, or perhaps worse, injecting meaning that is incorrect into a technical term, well … software might be the place for you. Consider Quality Assurance, or QA, which is something often used by people who do not have change permissions on

Three computer systems, working on the same problem separately, all try to solve a problem. If at least two come to the same conclusion, then everything can proceed. If, however, there are three different answers, then humans need to intervene to figure out what is really going on. Is this

Imagine this scenario: The company has programmers, analysts, and testers. The programmers complain the analysts do a poor job; they have to figure out what the software should really do. The testers come along and find problems with that, unconsidered scenarios, and we have to do everything over again. When

Executive Summary While the world of marketing is full of “best practices” and universal truisms, engineers tend to think in terms of trade offs. That is, this approach creates these problems and that approach creates those problems, and I value this over that, so I have made my choice. The Agile