Agile leadership

Last updated

Rooted in agile software development and initially referred to leading self-organizing development teams (Appelo, 2011; [1] ), the concept of agile leadership is now used to more generally denote an approach to people and team leadership that is focused on boosting adaptiveness in highly dynamic and complex business environments (Hayward, 2018; [2] Koning, 2020; [3] Solga, 2021 [4] ).

Contents

History

There are many perspectives on the origins of agile leadership, some of which align with the advent of the Agile Software Development manifesto. [5] With the rise of Agile software development organizations discovered the need for a new leadership approach. The relentless advancements of technology have introduced an evergrowing amount of VUCA (Volatility, uncertainty, complexity and ambiguity). As complexity grows, organizations need to be able to respond quickly with the ability to make decisions in ambiguous environments with increasing uncertainties. Traditional management is often seen as too slow in organizations engaged in these markets. Like Transformational leadership, Agile leadership practices promote enabling individuals and teams through the mandate and freedom to make their own decisions. Through realignment of accountability and decision-making, teams are offered the ability to respond quicker to changes and complexity. This technology-driven evolution of leadership approaches looks at the leader for supporting a managerial need for creating the right context and environment for self-managing teams. See Workers' self-management.

The framework for business agility has also created a set of Agile Leadership principles. [6]

The Agile leadership approach fits well in today's technology-focused culture in providing autonomy to employees while encouraging growth and experimentation to address the unknown needs of the future. By enabling individuals and teams to create clarity on the objectives or desired outcome and discover the best ways to achieve Agile Leadership looks to address the near-constant complexity and change intrinsic to organizations. Building from the origins of the Agile Software Development Manifesto, Agile Leadership practices fit the importance of customer focus or customer-centricity market needs.

Leading self-organizing teams

For some authors, the essence of agile leadership is creating the right environment for self-managing teams. Koning (2019), [7] for example, defines four corresponding areas of action:

  1. Co-create the goals – instead of giving instructions, rather make sure that the goals are clear. So teams know what to achieve, and if their actions are bringing them any closer to their goal.
  2. Facilitate Ownership – create an environment in which agile teams can grow and thrive. Teams can't be forced to take Ownership, leaders can only create those circumstances in which teams take ownership. This is a balancing between stepping in and letting go. Finding the sweetspot where teams have the right amount of freedom aligned with their level of maturity.
  3. Learn faster – being fit and ready for the future is not about being the best, it's about learning faster. Self-managing teams need to get fast feedback on their actions and their decisions. Preferably from users and customers. It's the leaders role to promote learning from experiments and failures.
  4. Design the culture – The agile leader has to envision, design and improve the culture of the organisation.

'Enabler - disruptor' model of agile leadership

Favoring a more general approach and highlighting the leadership demands linked to digitization, Hayward (2018) [2] describes agile leadership as simultaneously enabling and disrupting teams and the organization (a paradox, he refers to as the 'agile leadership paradox'):

Agile leader as 'enabler'

  1. Learning agility
  2. Clarity of direction
  3. Empathy and trust
  4. Empowering
  5. Working together

Agile leader as 'disruptor'

  1. Thoughtfully decisive
  2. Digitally literate
  3. Questioning the status quo
  4. Creating new ways of thinking
  5. Close to customer trends

'Align - empower' model of agile leadership

This framework (Solga, 2021) [4] strives to integrate the various ideas that have been floating around the concept of agile leadership. It defines the purpose of agile leadership as enabling people and teams to meet performance expectations and customer demands in business/task environments that are charged with VUCA (volatility, uncertainty, complexity, and ambiguity) and where process knowledge (knowing how to produce desired results) is weak.

To achieve this, an agile leader needs to simultaneously foster divergence and convergence (Solga, 2021). The former involves enabling and exploiting a multitude and diversity of options and possibilities to boost adaptiveness, that is to say, promote responsiveness, flexibility, and speed to effectively deal with dynamic change and disruptive challenges (the 'empower' component). The latter involves promoting alignment with overarching goals and standards as well as across teams (the 'align' component).

Solga (2021) defines three 'alignment' practices and three 'empowerment' practices:

'Alignment' practices (ensuring convergence):

  1. Motivate: Giving esteem, inspiration, and care to inspire emotional engagement and, with it, 'emotional alignment'
  2. Infuse: Creating value orientation and commitment to the purpose and values of the organization ('normative alignment')
  3. Focus: Creating a shared understanding of goals and priorities, roles, processes, and crucial boundary conditions within teams and across the organization ('task alignment')

'Empowerment' practices (enabling and exploiting divergence):

  1. Facilitate: Providing resources, removing obstacles, enabling self-organization, and giving decision-making discretion ('structural empowerment')
  2. Coach: Enabling people and teams to (co-) operate effectively in 'structurally empowered' task environments ('competency-focused empowerment')
  3. Innovate: Enabling an explorative or iterative approach to problem solving and task delivery (i.e., spiraling between experimentation and reflection, prototyping and feedback); also, promoting a constructive approach to handling tension (understanding frictions and conflicts as 'drivers of development'); since all this is about expanding and testing options to reach improvements and novel solutions, its focus is on 'innovation empowerment'

See also

Related Research Articles

Leadership development is the process which helps expand the capacity of individuals to perform in leadership roles within organizations. Leadership roles are those that facilitate execution of an organization's strategy through building alignment, winning mindshare and growing the capabilities of others. Leadership roles may be formal, with the corresponding authority to make decisions and take responsibility, or they may be informal roles with little official authority.

Agile software development is an umbrella term for approaches to developing software that reflect the values and principles 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">Dynamic systems development method</span> Agile project delivery framework

Dynamic systems development method (DSDM) is an agile project delivery framework, initially used as a software development method. First released in 1994, DSDM originally sought to provide some discipline to the rapid application development (RAD) method. In later versions the DSDM Agile Project Framework was revised and became a generic approach to project management and solution delivery rather than being focused specifically on software development and code creation and could be used for non-IT projects. The DSDM Agile Project Framework covers a wide range of activities across the whole project lifecycle and includes strong foundations and governance, which set it apart from some other Agile methods. The DSDM Agile Project Framework is an iterative and incremental approach that embraces principles of Agile development, including continuous user/customer involvement.

Agile Manufacturing is a modern production approach that enables companies to respond swiftly and flexibly to market changes while maintaining quality and cost control. This methodology is designed to create systems that can adapt dynamically to changing customer demands and external factors such as market trends or supply chain disruptions.

Lean software development is a translation of lean manufacturing principles and practices to the software development domain. Adapted from the Toyota Production System, it is emerging with the support of a pro-lean subculture within the agile community. Lean offers a solid conceptual framework, values and principles, as well as good practices, derived from experience, that support agile organizations.

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.

A product manager (PM) is a professional role that is responsible for the development of products for an organization, known as the practice of product management. Product managers own the product strategy behind a product, specify its functional requirements, and manage feature releases. Product managers coordinate work done by many other functions, and are ultimately responsible for product outcomes.

Operational Excellence (OE) is the systematic implementation of principles and tools designed to enhance organizational performance, and create a culture focused on continuous improvement. It is intended to enable employees to identify, deliver, and enhance the flow of value to customers. Common frameworks associated with operational excellence include: lean management and Six Sigma, which emphasize efficiency, waste reduction, and quality improvement. Organizations that adopt these practices may report increased customer satisfaction and operational efficiency.

Agile management is the application of the principles of Agile software development and Lean Management to various team and project management processes, particularly product development. Following the appearance of The Manifesto for Agile Software Development in 2001, organizations discovered the need for agile technique to spread into other areas of activity, including team and project management. This gave way to the creation of practices that built upon the core principles of Agile software development while engaging with more of the organizational structure, such as the Scaled agile framework (SAFe).

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.

Business agility refers to rapid, continuous, and systematic evolutionary adaptation and entrepreneurial innovation directed at gaining and maintaining competitive advantage. 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.

VUCA is an acronym based on the leadership theories of Warren Bennis and Burt Nanus, to describe or to reflect on the volatility, uncertainty, complexity and ambiguity of general conditions and situations. The U.S. Army War College introduced the concept of VUCA in 1987, to describe a more complex multilateral world perceived as resulting from the end of the Cold War. More frequent use and discussion of the term began from 2002. It has subsequently spread to strategic leadership in organizations, from for-profit corporations to education.

DevOps is a methodology integrating and automating the work of software development (Dev) and information technology operations (Ops). It serves as a means for improving and shortening the systems development life cycle. DevOps is complementary to agile software development; several DevOps aspects came from the agile approach.

Lean integration is a management system that emphasizes creating value for customers, continuous improvement, and eliminating waste as a sustainable data integration and system integration practice. Lean integration has parallels with other lean disciplines such as lean manufacturing, lean IT, and lean software development. It is a specialized collection of tools and techniques that address the unique challenges associated with seamlessly combining information and processes from systems that were independently developed, are based on incompatible data models, and remain independently managed, to achieve a cohesive holistic operation.

<span class="mw-page-title-main">Extreme programming</span> Software development methodology

Extreme programming (XP) is a software development methodology intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent releases in short development cycles, intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted.

Disciplined agile delivery (DAD) is the software development portion of the Disciplined Agile Toolkit. DAD enables teams to make simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including scrum, agile modeling, lean software development, and others.

In software engineering, a microservice architecture is an architectural pattern that organizes an application into a collection of loosely coupled, fine-grained services that communicate through lightweight protocols. This pattern is characterized by the ability to develop and deploy services independently, improving modularity, scalability, and adaptability. However, it introduces additional complexity, particularly in managing distributed systems and inter-service communication, making the initial implementation more challenging compared to a monolithic architecture.

<span class="mw-page-title-main">Asia School of Business</span> University in Bukit Tunku, Kuala Lumpur, Malaysia

The Asia School of Business (ASB) is a graduate business school based in Kuala Lumpur, Malaysia. ASB was established in 2015 through a partnership between the MIT Sloan School of Management and Bank Negara Malaysia, the Central Bank of Malaysia. It offers a range of programs, including a 12-month Master of Business Administration (MBA), a 16-month Executive MBA (EMBA), and a 12-month Master in Central Banking (MCB).

The scaled agile framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices. Along with disciplined agile delivery (DAD) and S@S (Scrum@Scale), SAFe is one of a growing number of frameworks that seek to address the problems encountered when scaling beyond a single team.

Transcendent Leadership is a modern leadership philosophy that emphasizes holistic development, inclusivity, and ethical practices within organizations. Unlike traditional leadership models, which often prioritize hierarchical authority and top-down control, transcendent leadership advocates for empowering individuals at all levels, fostering collaboration, and aligning organizational goals with social and environmental val-ues. This approach has gained prominence in response to complex contemporary challenges, such as digital transformation and shifting workforce expectations, as leaders recognize that innovative solutions often arise from diverse perspectives and collective effort.

References

  1. ↑ Appelo, J. (2011). Management 3.0: Leading agile developers, developing agile leaders. Upper Saddle River, NJ: Addison-Wesley.
  2. 1 2 Hayward, S. (2018). The agile leader: How to create an agile business in the digital age. London: Kogan Page.
  3. ↑ Koning, P. (2020). Agile leadership toolkit: Learning to thrive with self-managing teams. Boston, MA: Addison-Wesley.
  4. 1 2 Solga, M. (2021). The 'align - empower' model of agile leadership ('practice' whitepaper #03, cidpartners GmbH)
  5. ↑ "Manifesto for Agile Software Development". agilemanifesto.org. Retrieved 10 April 2023.
  6. ↑ "Agile Business Consortium". www.agilebusiness.org. Retrieved 10 April 2023.
  7. ↑ Koning, P. (2020). Agile leadership toolkit: Learning to thrive with self-managing teams. Boston, MA: Addison-Wesley.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.