Archive for April 2014

Agile is Nothing New

April 23rd, 2014

When we talk proudly of adopting Agile processes for our projects, why do we do so with a somewhat superior air over the old tried and trusted methods of software development? Read More

The Software Chicken and the Egg

April 16th, 2014

For a considerable period of time, we did well organized testing, but not against requirements that were formally defined.
Why was it deemed necessary to automate the test management process before there were any decent tools for recording exactly what we were testing for? Read More

Beware the Over-Engineered Software Product

April 8th, 2014

When evaluating software features to either build or buy there is a tendency to want to have every possible feature even if it will be rarely (or event never used) on the off-chance that it could be useful. This post describes some of the pitfalls with this approach. Read More

Documenting Requirements in Agile Projects

April 1st, 2014

(aka The Changing Role of the Modern Father)

One of the difficulties of moving from waterfall to an Agile development process is the breaking down of silos of responsibility, including that of the product owner. No longer the deliverer of the requirements 'master-specification', the product owner now participates throughout the entire process, sharing the requirements management task and taking on new, varied and, sometimes unexpected, responsibilities.

Read More