Overcoming Blockages In Strategy Execution: Lessons From Agile Managers

2021 ◽  
Vol 86 (2) ◽  
pp. 54-63
Author(s):  
Robert Ford ◽  
Misty Loughry

Managers’ attempts to implement their organization’s strategy often meet with challenges that block the execution as planned and these blockages are not always obvious. This paper presents seven lessons from agile software development that managers can use to avoid and overcome blockages in strategy execution. They are: 1) Define and communicate an agile culture. 2) Define and communicate an end goal with measures and deadlines. 3) Break the end goal into multiple projects with specific objectives and short deadlines and assign them to small teams. 4) Give project teams autonomy, but hold them responsible for achieving their objectives on time. 5) Hold frequent brief meetings to identify problems and coordinate across teams. 6) Frequently consult with the customer or end user. 7) Constantly monitor all teams’ progress and customer needs to look for blockages; pivot quickly when a change is needed to execute the strategic plan. These seven lessons help managers quickly recognize when the path to strategy implementation is blocked and lead their teams to find alternatives and quickly pivot to new implementation plans. The process creates a culture that focuses on results yet empowers teams and employees to use their talents and creativity. As a result, the organization is focused and energized as it implements its strategy.

2021 ◽  
Vol ahead-of-print (ahead-of-print) ◽  
Author(s):  
Carin Lindskog ◽  
Monika Magnusson

PurposeThe purpose of this study is to apply the concept of organizational ambidexterity as a conceptual lens to increase the understanding of tensions between exploitation (continuity) and exploration (change) in Agile software development (ASD) project teams, and particularly the balancing (ambidextrous) strategies utilized.Design/methodology/approachA conceptual framework was constructed from interdisciplinary sources on ambidexterity. A literature review of publications on ambidexterity in ASD was then performed, and the results from the selected publications were classified according to an extension of the conceptual framework.FindingsContextual ambidexterity in ASD is affected by the four basic coherent concepts: time, task, team and transition. The study found that most ambidextrous factors and strategies were task and team-related. In addition, a mixture of hard (performance) strategies and soft (social) strategies is needed in order for people/teams to (be able to) become ambidextrous.Practical implicationsTo provide a better understanding of ASD, it is important to identify a broader set of ambidextrous factors and strategies that can impact ASD project teams. The expanded conceptual framework can serve as a basis for future empirical research and provide insights to practitioners on how to strengthen ambidexterity in ASD projects.Originality/valueThe contribution is of great importance for ASD research and practice, as ASD methods are a popular method for managing projects within ASD and in other nonsoftware organizations. In addition, as more and more organizations struggle to deal with rapidly changing environments, interest in the phenomena of paradoxical tensions and the strategy (ambidexterity) to deal with these tensions increase.


2018 ◽  
Vol 49 (6) ◽  
pp. 78-102 ◽  
Author(s):  
Kim E. van Oorschot ◽  
Kishore Sengupta ◽  
Luk N. Van Wassenhove

The iterative cycles used in agile software development create a series of deadlines for project teams. We investigate the optimal iteration length under behavioral conditions for agile software projects. Based on system dynamics simulation, we argue that both very long (as in sequential development) and very short (monthly) iterative cycles create huge and disruptive fluctuations in schedule pressure experienced by the team. These lead to poor performance in terms of quality, as well as costs and time compared with optimal iterative cycles of two to three months. The monthly cycles used in many agile practices might be too short to ensure optimal performance.


2020 ◽  
Vol 30 (2) ◽  
pp. 100288 ◽  
Author(s):  
Anna Zaitsev ◽  
Uri Gal ◽  
Barney Tan

Sign in / Sign up

Export Citation Format

Share Document