back to top

our blog


Developers Can’t Test For Toffee!

by Kelly Waters, 19 March 2007

In the more traditional world of managing software development projects, it is widely acknowledged that developers can’t test for toffee! Yet agile development methods increasingly seem to require or imply that all people in the project team should test, including developers. So, first of all, why is it that developers can’t test? Are we to […]

Tell me more >
Why Agile Testers Should Be In At The Start

by Kelly Waters, 18 March 2007

In my experience, some people implement agile principles within the development team itself, but leave other key roles (for instance business users or testers) out of, or on the fringes, of the agile team. Earlier in my blog I wrote that active user involvement is imperative in agile development for a wide variety of reasons. […]

Tell me more >
Agile Principle 4: Agile Requirements Are Barely Sufficient

by Kelly Waters, 17 March 2007

Agile development teams capture requirements at a high level and on a piecemeal basis, just-in-time for each feature to be developed. Agile requirements are ideally visual and should be barely sufficient, i.e. the absolute minimum required to enable development and testing to proceed with reasonable efficiency. The rationale for this is to minimise the time […]

Tell me more >
Testing Testing 123 (test driven development)

by Kelly Waters, 14 March 2007

XP (eXtreme Programming) advocates Test Driven Development, where test cases are written before the code. Radical, huh? If you think about it, it makes complete sense. Assuming you are planning to write test cases anyway, it’s no more effort than writing them later. And the big advantage of writing them first? If you know how […]

Tell me more >
What If An Agile Team Member Won’t Play Ball?

by Kelly Waters, 13 March 2007

What do you do if someone in your agile development team is simply not playing ball? Particularly if their behaviour is counter-productive to the key principles of agile development and is affecting the team’s performance. One comment I’ve heard (not at my organisation by the way) was to apply the self-organised nature of Scrum and […]

Tell me more >
Agile Principle 3: Time Waits For No Man!

by Kelly Waters, 11 March 2007

In agile development, requirements evolve, but timescales are fixed. This is in stark contrast to a traditional development project, where one of the earliest goals is to capture all known requirements and baseline the scope so that any other changes are subject to change control. Traditionally, users are educated that it’s much more expensive to […]

Tell me more >
Agile Development At Full Stretch

by Kelly Waters, 06 March 2007

In my experience, most developers are over-optimistic and tend to under-estimate. However it’s not uncommon for some teams to estimate on the cautious side. If you find yourself in this situation and finishing the Sprint (or timebox) early, include a couple of nice-to-have “stretch tasks” (or features/stories) in future Sprints. It’s important to specifically identify […]

Tell me more >