Not one word in the article about 'Requirements'
What happened to Requirements Management ?
Does the author assume that 'ALL' requirements have been nailed down.
I've seen some projects where the originator of a requirement changes it
in midstream of the project taking it back to square one (time wasted).
Agile, RUP, CMMI and other process improvement methods address requirements,
but when the man with the money changes requirements, he then has
to reach in his pocket and sometimes he doesn't like to do that !