Development Cycle 2.0
A good friend of mine just gave me a great description of a less-than-perfect software process, expressed as a BASIC program:
10 You’ve just written some poor software
20 Experience problem with software
30 Attempt to fix
40 Goto 10
Gotta love the simplicity of it all. Haven’t we all worked like this from time to time? I know I have. Recently, in fact…
Here’s another one for the project managers and service delivery managers out there:
10 Take one step forward
20 Take two steps back
30 Goto 10
[...] just read a recent, albeit small, Blog entry which highlighted the gap between stakeholders requirements and end products delivered within the [...]
Pingback by Now, where the hell is THAT mentioned in the Spec??? « DevGorilla - not your average coding monkey — April 18, 2008 @ 6:19 pm