ABSTRACT
The project is confined to a particular business function or department, it is still necessary to identify the information and business process interfaces with other parts of the organization and with those that reside outside the organization. An important consideration is to what extent the development of the intended system is to be undertaken in-house as a software development project, rather than buying in a 'packaged' solution. The National Archives provides guidance on the formulation of a records management (RM) policy with the sound advice to keep it short and strategic. Although 'records' are the key information content in an organization, the title 'information' management (IM) policy is likely to be more readily comprehended across an organization. Based on the actual experience of using enterprise content management (ECM) systems, estimates for workflow productivity gains and project delivery improvements were higher than projections by non-users, indicating results that are better than expected.
