[former 2005 blog] Why Defining Requirements is Not Good Enough

Once upon a time, the mainframe was. The mainframe hosted complex corporate applications that required a very disciplined and sequential approach to requirements definition. In particular, it required requirements to be fully flushed out before coding began. Changing requirements en route was a big no-no and (mostly) constituted a too expensive proposition. That era is gone (...) The generally accepted approach in software development now calls for iterative (or evolutive) development.

[former 2005 blog] Government of Canada IM Day 2006 | Web 2.0 "Track"

Last week, the planning committee of the Fall 2006 Government of Canada "Information Management Day" (GC IM Day) met, and we flushed out some ideas on what topics to put on the schedule. In our current planning, one track will have the "Leading" flavour, in the sense of leading change, and that one or two sessions under that track will specifically deal with Web 2.0 implementations in the Government of Canada - existing, proposed and suggested.