Posts Tagged ‘tester’

Behavior in the code that is Not in the Requirements

Friday, August 7th, 2009

For most commercial applications, fifty percent or more of the shipped code cannot be traced directly to the corresponding requirements document. This is true because:

There are requirements that should have been documented but weren’t. All requirements are imperfect and incomplete. Given this fact, programmers make assumptions, add behavior, get informal, undocumented clarification of requirements, and write a lot of code to implement business requirements that never made it to the requirements document. (more…)

An agile process is not just a series of mini waterfalls

Thursday, July 16th, 2009

One of the common problems I encounter with teams new to agile is that they try to keep using the old over-the-wall hand-off methods they were used to in the waterfall world. (more…)