Development of the Organizational Agility Maturity Model

Abstract

Abstract-The importance of organizational agility in a competitive environment is nowadays widely recognized and accepted. However, despite this awareness, the availability of tools and methods that support an organization in assessing and improving their organizational agility is scarce. Therefore, this study introduces the Organizational Agility Maturity Model in order to provide an easy-to-use yet powerful assessment tool for organizations in the software and IT service industry. Based on a design science research approach with a comprehensive literature review and an empirical investigation utilizing factor analysis, both scientific rigor as well as practical relevance is ensured. The applicability is further demonstrated by a cluster analysis identifying patterns of organizational agility that fit to the maturity model. The Organizational Agility Maturity Model further contributes to the field by providing a theoretically and empirically grounded structure of organizational agility supporting the efforts of developing a common understanding of the concept.

Traditional and Agile Project Management in Public Sector and ICT

“…The enterprises of the highest project maturity [34] are the integrators (level 4 according to H. Kerzner model [35]), and the lowest -telecommunication operators (level 1).…”

“…Actually, it is not important which of the internationally recognized standards (PMBOK ® or PRINCE2 ® ) and maturity models - [34]- [35] will be selected as obligatory on the 3 In Great Britain even the Highways Agency which is a counterpart of the Polish General Directorate of National Roads and Highways, and not of a higher level such as the UZP, cares about the level of project management and issues recommendations for the projects of highways construction.…”

Comparison of Selected Modeling Notations for Process, Decision and System Modeling

“…The model was designed by Philippe Kruchten and used for "describing the architecture of softwareintensive systems, based on the use of multiple, concurrent views" [32]. The views are used to describe the system from the viewpoint of different users (end-users, developers and project managers) [32], [34]. The "4+1" view model supports five main views, as shown in Figure 4 and in Table: 1.…”

Using ESSENCE ALPHAs in a CMMI level 5 software development organization

“…"Take the best (that fits for you) of each world and apply it in your context". As [20] establishes, an organization has to understand that the organization itself cannot be agile, but its employees can be.…”