Business agility

Last updated

Business agility refers to rapid, continuous, and systematic evolutionary adaptation and entrepreneurial innovation directed at gaining and maintaining competitive advantage. [1] Business agility can be sustained by maintaining and adapting the goods and services offered to meet with customer demands, adjusting to the marketplace changes in a business environment, and taking advantage of available human resources. [2]

Contents

In a business context, agility is the ability of an organization to rapidly adapt to market and environmental changes in productive and cost-effective ways. An extension of this concept is the agile enterprise, which refers to an organization that uses key principles of complex adaptive systems and complexity science to achieve success. [3] Business agility is the outcome of organizational intelligence.

Overview

Businesses which lack adaptability may be left paralyzed when faced with changing markets and environments. To counter this, business agility can be developed in the enterprise, making change a routine part of organizational life. [4] An agile enterprise may be able to nimbly adjust to and take advantage of emerging opportunities in a perpetually changing environment. The agile enterprise can be viewed as an integral component of a larger system whose activities produce a ripple effect of change within both the enterprise itself and the broader system. [5]

The discipline of enterprise architecture supports business agility through techniques including layering, separation of concerns, architecture frameworks, and the separation of dynamic and stable components. The model of hierarchical complexity—a framework for scoring the complexity of behavior—has been adapted to describe the stages of complexity in enterprise architecture. [6]

One type of enterprise architecture that supports agility is a non-hierarchical organization without a single point of control. [7] In such an organization, individuals function autonomously, constantly interact with each other to define the organization's vision and aims, maintain a common understanding of requirements, and monitor the work that needs to be done. Roles and responsibilities are not predetermined but in flux, and emerge from individuals' self-organizing activities. Projects are generated across in the enterprise and sometimes from outside affiliates. Key decisions are made collaboratively, on the spot, and on the fly. Because of this, knowledge, power, and intelligence are spread through the enterprise, making it capable of quickly recovering and adapting to the loss of any key enterprise component.

In business, projects can be complex with uncertain outcomes and goals that can change over time. Traditionally these issues were dealt with by planning experts who would attempt to pre-determine every possible detail prior to implementation; however, in many situations, even the most carefully conceived projects will be impossibly difficult to manage. Agile techniques, originating from the software development community, represent an alternative approach to the classic prescriptive planning approaches to management. The main focus of agile methods is to address the issues of complexity, uncertainty, and dynamic goals, by making planning and execution work in parallel rather than in sequence to eliminate unnecessary planning activity, and the resulting unnecessary work.

Pragmatic methods for achieving organizational agility should start from an organization's competitive bases and the organization's mission, vision, and values. [8] [9] Agile methods integrate planning with execution, allowing an organization to find an optimal ordering of work tasks and to adjust to changing requirements. The major causes of chaos on a project include an incomplete understanding of project components, incomplete understanding of component interactions, and changing requirements. Sometimes requirements change as a greater understanding of the project components unfolds over time. Requirements also change due to the changing needs and wants of the stakeholders. The agile approach allows a team or organization of collective trust, competence, and motivation to implement successful projects quickly by focusing on only a small set of details in any change iteration. This is in contrast to non-agile in which all the details necessary for completion are generally taken to be foreseeable and have equal priority inside of one large iteration.

History

A concept of "agility" as an attribute of business organizations arose in response to the requirements of modern business to operate in predictable ways in the face of extreme complexity. In particular, software development organizations have created a specific set of techniques known as agile methods to address the problems of changing requirements, uncertain outcomes due to technological complexity, and uncertain system dynamics due to overall system complexity. Some of the ideas that have shaped thinking in the agile community arose from the studies of complexity science and the notion of complex adaptive systems (CAS).

As with CAS, the outcomes or products of agile organizations such as software teams are inherently unpredictable yet will eventually form an identifiable pattern. Despite their unpredictability, agile enterprises are thought to be best positioned to take advantage of hypercompetitive external environments.

Agile enterprises exist in corporate (e.g. W. L. Gore & Associates and Oticon), non-profit (e.g. Alcoholics Anonymous), community (e.g., Wikipedia, the Burning Man festival), and even terrorist (e.g. Al Qaeda) environments.[ citation needed ]

Topics in agile enterprise studies

Comparison with complex systems

Interactions, self-organizing, co-evolution, and the edge of chaos are concepts borrowed from complexity science that can help define some of the processes that take place within an agile enterprise.

Interactions are exchanges among individuals, etc. holding a common vision and possessing the necessary resources, behaviors, competence, and experience in aggregate. They are an important driving force for agile enterprises, because new ideas, products, services, and solutions emerge from the multiple exchanges happening over time. The interactions themselves, rather than individuals or the external environment, are significant drivers of innovation and change in an agile enterprise.

Self-organizing describes the spontaneous, unchoreographed, feedback-driven exchanges that are often found within agile enterprises. Vital initiatives within the agile enterprise are not always managed by one single person; rather all parties involved collectively make decisions without guidance or management from an outside source. The creativity and innovation that arises from this self-organizing process give the agile enterprise an edge in developing (and redeveloping) products, services, and solutions for a hypercompetitive marketplace.

Co-evolution is a key process through which the enterprise learns from experience and adapts. The agile enterprise is constantly evolving in concert with (and in reaction to) external environmental factors. Products and services are in a constant state of change, because, once launched, they encounter competitors' products, regulators, suppliers, and customer responses that force adaptations. In one sense, nothing is ever completely "finished," although this does not mean that nothing is ever made, produced, or launched.

The edge of chaos is a borderline region that lies between complete anarchy or randomness and a state of punctuated equilibrium. The agile enterprise ideally operates in this region, needing the tension between constant change and the constraints that weaken change efforts to keep the organization perturbed enough for innovation and success. In other words, the edge of chaos is the space in which self-organizing and co-evolution flourish.

Comparison with bureaucracies

There are several key distinctions between the agile enterprise and the traditional bureaucratic organization.

The most notable is the agile enterprise's use of fluid role definitions that allow for dynamic decision-making structures. Unlike the rigid hierarchies which characterize traditional bureaucracies, organizational structures within agile enterprises are more likely to fluidly adapt to changing business conditions, forming them into structures that support the current direction and any emergent competitive advantage. [10]

Similarly, agile enterprises do not adhere to the concept of sustained competitive advantage that typifies the bureaucratic organization. Operating in hypercompetitive, continuously changing markets, agile enterprises pursue a series of temporary competitive advantages—capitalizing for a time on the strength of an idea, product, or service then readily discarding it when no longer tenable. [11]

Lastly, the agile enterprise is populated with individuals pursuing serial incompetence; [12] they work hard to obtain a certain level of proficiency in one area but are driven to move on to the next "new" area to develop expertise. There are no subject-matter experts specializing for years in one topical area, as found typically in a traditional bureaucracy.

Operating at the edge of chaos

Although agile enterprises by definition include numerous constantly co-evolving and moving parts, they do require some structure.

The enterprise must develop specific structures (also called system constraints) to serve as a counterbalance to randomness and anarchy, keeping the enterprise optimally functioning on the edge of chaos. These structures including a shared purpose or vision, resource management aids, reward systems, and shared operating platforms. These often emerge from three key organizational processes: strategizing, organizing, and mobilizing. [13]

Strategizing is an experimental process for the agile enterprise, in which individuals repeatedly generate ideas (exploration), identify ways to capitalize on ideas (exploitation), nimbly respond to environmental feedback (adaptation), and move on to the next idea (exit).

Organizing is an ongoing activity to develop structures and communication methods that promote serial execution. It often includes defining a shared vision, as well as systems and platforms, that ground the enterprise.

Mobilizing involves managing resources, ensuring the fluid movement of people between projects, and finding ways to enhance internal and external interactions. Typically, enterprise values, personal accountability, and motivational and reward systems are a key output of this process.

See also

Related Research Articles

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

A software company is an organisation — owned either by the state or private — established for profit whose primary products are various forms of software, software technology, distribution, and software product development. They make up the software industry.

Rapid application development (RAD), also called rapid application building (RAB), is both a general term for adaptive software development approaches, and the name for James Martin's method of rapid development. In general, RAD approaches to software development put less emphasis on planning and more emphasis on an adaptive process. Prototypes are often used in addition to or sometimes even instead of design specifications.

<span class="mw-page-title-main">Systems development life cycle</span> Systems engineering terms

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

An organizational structure defines how activities such as task allocation, coordination, and supervision are directed toward the achievement of organizational aims.

Agile software development is the mindset for developing software that derives from values agreed upon by The Agile Alliance, a group of 17 software practitioners in 2001. As documented in their Manifesto for Agile Software Development the practitioners value:

<span class="mw-page-title-main">Social complexity</span> Conceptual framework

In sociology, social complexity is a conceptual framework used in the analysis of society. In the sciences, contemporary definitions of complexity are found in systems theory, wherein the phenomenon being studied has many parts and many possible arrangements of the parts; simultaneously, what is complex and what is simple are relative and change in time.

A complex adaptive system is a system that is complex in that it is a dynamic network of interactions, but the behavior of the ensemble may not be predictable according to the behavior of the components. It is adaptive in that the individual and collective behavior mutate and self-organize corresponding to the change-initiating micro-event or collection of events. It is a "complex macroscopic collection" of relatively "similar and partially connected micro-structures" formed in order to adapt to the changing environment and increase their survivability as a macro-structure. The Complex Adaptive Systems approach builds on replicator dynamics.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

A value network is a graphical illustration of social and technical resources within/between organizations and how they are utilized. The nodes in a value network represent people or, more abstractly, roles. The nodes are connected by interactions that represent deliverables. These deliverables can be objects, knowledge or money. Value networks record interdependence. They account for the worth of products and services. Companies have both internal and external value networks.

Decision management, also known as enterprise decision management (EDM) or business decision management (BDM) entails all aspects of designing, building and managing the automated decision-making systems that an organization uses to manage its interactions with customers, employees and suppliers. Computerization has changed the way organizations are approaching their decision-making because it requires that they automate more decisions, to handle response times and unattended operation required by computerization, and because it has enabled "information-based decisions" – decisions based on analysis of historical behavioral data, prior decisions, and their outcomes.

Microsoft Solutions Framework (MSF) is a set of principles, models, disciplines, concepts, and guidelines for delivering information technology services from Microsoft. MSF is not limited to developing applications only; it is also applicable to other IT projects like deployment, networking or infrastructure projects. MSF does not force the developer to use a specific methodology.

<span class="mw-page-title-main">Organizational architecture</span> Procedural structure of an organization

Organizational architecture, also known as organizational design, is a field concerned with the creation of roles, processes, and formal reporting relationships in an organization. It refers to architecture metaphorically, as a structure which fleshes out the organizations. The various features of a business's organizational architecture has to be internally consistent in strategy, architecture and competitive environment.

Complexity theory and organizations, also called complexity strategy or complex adaptive organizations, is the use of the study of complexity systems in the field of strategic management and organizational studies. It draws from research in the natural sciences that examines uncertainty and non-linearity. Complexity theory emphasizes interactions and the accompanying feedback loops that constantly change systems. While it proposes that systems are unpredictable, they are also constrained by order-generating rules.

The following outline is provided as an overview of and topical guide to business management:

A network-centric organization is a network governance pattern which empowers knowledge workers to create and leverage information to increase competitive advantage through the collaboration of small and agile self-directed teams. It is emerging in many progressive 21st century enterprises. This implies new ways of working, with consequences for the enterprise’s infrastructure, processes, people and culture.

A glossary of terms relating to project management and consulting.

<span class="mw-page-title-main">View model</span>

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of the whole system from the perspective of a related set of concerns.

In software engineering, a software development process or software development life cycle (SDLC) is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

<span class="mw-page-title-main">Federated architecture</span> Pattern in enterprise architecture that allows interoperability and information sharing

Federated architecture (FA) is a pattern in enterprise architecture that allows interoperability and information sharing between semi-autonomous de-centrally organized lines of business (LOBs), information technology systems and applications.

References

  1. Baškarada, Saša (2020). "The Seven S's of Organizational Agility". AWS Cloud Enterprise Strategy Blog. Archived from the original on 2020-11-01.
  2. Nikos C. Tsourveloudi, Kimon P. Valavanis (2002). "On the Measurement of Enterprise Agility". Journal of Intelligent and Robotic Systems. 33 (3): 329–342. doi:10.1023/A:1015096909316. S2CID   17032103.
  3. Dyer, L. and Ericksen, J. (2009). Complexity-based Agile Enterprises: Putting Self-Organizing Emergence to Work. In A. Wilkinson et al (eds.). The Sage Handbook of Human Resource Management. London: Sage: 436–457.
  4. Hamel, G. & Valikangas (2003). The Quest for Resilience. Harvard Business Review, September: 52–63.
  5. Holbrook, M. (2003). Adventures in Complexity. Academy of Marketing Science Review, 6: 1–181.
  6. Evernden, R. Mastering Complexity to Drive EA Productivity , Cutter Consortium Executive Report, Vol. 16, No. 1, 2013
  7. Stacey, R., Griffin, D. & Shaw, P. (2000). Complexity and Management: Fad or Radical Challenge to Systems Thinking? London: Routledge.
  8. Nejatian, Majid; Zarei, Mohammad Hossein (2013). "Moving Towards Organizational Agility: Are We Improving in the Right Direction?". Global Journal of Flexible Systems Management. 14 (4): 241–253. doi:10.1007/s40171-013-0048-3. S2CID   256376182.
  9. Nejatian, Majid; Zarei, Mohammad Hossein; Nejati, Mehran; Zanjirchi, Seyed Mahmood (2018). "A hybrid approach to achieve organizational agility". Benchmarking. 25: 201–234. doi:10.1108/BIJ-09-2016-0147. hdl: 11311/1058214 .
  10. Dyer, L. & Ericksen, J. (2007). Dynamic Organizations: Achieving Marketplace Agility Through Workforce Scalability. In J. Storey (ed.). Human Resource Management: A Critical Text (3rd edition). London: Thomson Learning: 263–280.
  11. Stacey, R. (2006). The Science of Complexity: An Alternative Perspective for Strategic Change Processes. In R. MacIntosh et al (eds.). Complexity and Organization: Readings and Conversations. London: Routledge: 74–100.
  12. Godin, S. (2000). In the Face of Change, the Competent are Helpless. Fast Company, January–February: 230–234.
  13. Dyer & Ericksen (2007), op cit.

Further reading