Every organisation needs access to fast online data in order to meet increasing customer demands. As a result, the information architecture of a company, how it is designed, and how information is managed are very important. Because the amount of content is growing at a precipitous rate, in order to manage it with the greatest efficacy, an Enterprise Content Management (ECM) system is
... [Show full abstract] recommended. The challenge for organisations is to implement and manage a dynamic ECM system that is responsive to changing requirements, while providing a structure that contributes to organisational efficiencies. How a new ECM system is designed (engineered) and implemented (e.g. with Office 365, SharePoint, G Suite, or SAP OpenText) determines its future success. This paper discusses the use of Agile approaches for ECM systems engineering, to also manage the risks and decrease the chance of disuse. This research paper looks into the current context of Intranets, Content Services, and the desirable qualities of an Agile approach. First, the literature review explores the definitions, elements, and benefits of Content Services. Then, the paper discusses Agile project management (APM) with some major characteristics and typical features. Thirdly, the paper describes how an Agile ECM system should be. An Agile ECM can be developed with an APM or hybrid approach-i.e. the combination of an Agile software development process and an Agile end product. Content Services are using more and more Artificial Intelligence (AI) features. Content Services should also take advantage of the growing Internet, cloud services, and mobile computing. This paper covers possible methodologies based on traditional and Agile software engineering approaches. These encourage a flexible development approach to ECM implementation, and keeping end user involvement and needs at the forefront. Once implemented, an ECM system should also be dynamic enough to meet the demands of future organisational growth and business environment. A system should allow integration with other new software in the future including those used within the organisation and those in the Cloud. Examples of methodologies include Scrum and MIKE2.0, which are explained, along with their strengths and weaknesses. One recommendation is to have a hybrid approach. Finally, the paper reemphasizes that the most important stakeholders of the resulting system are the numerous and diverse online end users.