Leadership and agility are not separate concerns but fundamentally intertwined. Drawing on the British Army's Mission Command philosophy — where commanders set intent and boundaries while empowering junior leaders to act autonomously — the post argues that software teams cannot achieve true agility without leaders who delegate authority, build trust, and communicate intent clearly up and down the chain. Poor leadership restricts agility regardless of which frameworks a team adopts, while trust and shared understanding at every level are prerequisites for teams to make fast, autonomous decisions.
Questions this post answers
What is the Mission Command philosophy and how does it relate to agile software development?
Mission Command is a British Army leadership approach that empowers subordinate commanders to act on their own initiative within a defined intent and boundaries, rather than waiting for orders. It prioritises agility and tempo by delegating decision-making to those closest to the situation. In software development, the same principle applies: teams become more adaptive when leaders set direction and trust individuals to make autonomous decisions without fear of reprisal. Engineering leaders navigating delegation and team autonomy find the ongoing debate on daily.dev useful for shaping their approach.