[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] Information Management as a Unified Discipline

Until quite recently, Information Management (IM) practitioners have practiced their craft in isolation. Typical stereotypes and perceptions often portrayed records managers belonging to the basement, IT specialists in high paced I can do anything settings, Librarians in I go on managing my collections and serials mindsets and business users in why does IT not solve my problems as expected exasperations. This era is coming to an end. Why? The commoditization of IT, the increasing pressure to achieve better cost-efficiency and higher management expectations are forcing IM to reorganize itself into a coherent field of practice. IM is becoming more “unified” or “integrated”.

[former 2005 blog] Inaugural Post - Information Management Now!

In 2005, when blogs were still relatively new, I started a blog on Information Management. This inspiration for that blog was summarized in this head note:

So much stuff on information management, content management, information technology, data management, records management, library management... But how does it all come together? Where to find an "Information Management Body of Knowledge"? (IMBOK)

For the sake of continuity, I am importing here a few posts from that old blog to give my readers a sense of continuity from the old Information Management paradigm to the new Digital Transformation paradigm.

Here follows the inaugural "Information Management Now" post.