In an earlier post I’d lamented about the problems in managing requirements, this post probably reads as a prequel to that one. What are the real problems when it comes to requirements analysis? continue reading…
In an earlier post I’d lamented about the problems in managing requirements, this post probably reads as a prequel to that one. What are the real problems when it comes to requirements analysis? continue reading…
As a IT professional, I’ve often found myself at a loss when I’ve had to explain my job concisely. Usually following the informal pleasantries, including hellos, name exchanges and handshakes is the dreaded “So, what do you do?”
Um’ I’m an IT professional.
Okay, but what do you do?
Software development has come a full circle states Alex Iskold in a scathing, pull-no-punches broadside upon the Waterfall model.
Read it here: the future of software development
Nowadays, this question seems to figure at every technical interview that that I been involved with (at either side of the table). What would you choose – Waterfall model or the Iterative approach?
The correct answer – it depends.
The usual answer – some mumbling about extreme programming (followed barely disguised rant on how one was forced to use it).