The Agile Manager.

Agile development was defined by Eric Ries in his book The Lean Startup.  It is the breakthrough idea that software (a product) should be built iteratively with pieces customers value most created first.  Lean Startup allows companies to create order not chaos by providing tools to test a vision. as ideas are put through the build-measure-learn loop. But, who manages in an agile organization and what exactly do they do?  This article in the McKinsey Quarterly (July 2018) answers these questions.

The agile workplace is becoming increasingly common. In a McKinsey survey of more than 2,500 people across company sizes, functional specialties, industries, regions, and tenures, 37 percent of respondents said their organizations are carrying out company-wide agile transformations, and another 4 percent said their companies have fully implemented such transformations. The shift is driven by proof that small, multidisciplinary teams of agile organizations can respond swiftly and promptly to rapidly changing market opportunities and customer demands. Indeed, more than 80 percent of respondents in agile units report that overall performance increased moderately or significantly since their transformations began.

These small teams, often called “squads,” have a great deal of autonomy. Typically composed of eight to ten individuals, they have end-to-end accountability for specific outcomes and make their own decisions about how to achieve their goals. This raises an obvious and seemingly mystifying question for people who have worked in more traditional, hierarchical companies: Who manages in an agile organization? And what exactly does an agile manager do?

Lay of the land

The answers become clear once you understand that the typical agile company employs a dynamic matrix structure with two types of reporting lines: a capability line and a value-creation line. Nearly all employees have both a functional reporting line, which is their long-term home in the company, and a value-creation reporting line, which sets the objectives and business needs they take on in squads.

In agile parlance, the capability reporting lines are often called “chapters” and are similar in some ways to functions in traditional organizations (you might have a “web developers” chapter, say, or a “research” chapter). Each chapter is responsible for building a capability: hiring, firing, and developing talent; shepherding people along their career paths; evaluating and promoting people; and building standard tools, methods, and ways of working. The chapters also must deploy their talented people to the appropriate squads, based on their expertise and demonstrated competence. In essence, chapters are responsible for the “how” of a company’s work. However, once talent is deployed to an agile team, the chapters do not tell people what to work on, nor do they set priorities, assign work or tasks, or supervise the day-to-day.

The value-creation reporting lines are often called “tribes.” They focus on making money and delivering value to customers (you might have a “mortgage services” tribe or a “mobile products” tribe). Tribes are similar to business units or product lines in traditional organizations. Tribes essentially “rent” most of their resources from the chapters. If chapters are responsible for the “how,” tribes are responsible for the “what.” They set priorities and objectives and provide marching orders to the functional resources deployed to them.

Management roles

In this world, the work of a traditional midlevel manager is reallocated to three different roles: the chapter leader, the tribe leader, and the squad leader. Let’s examine the responsibilities of each and the challenges they pose for traditional managers looking to become agile managers.

The chapter leader

Every functional reporting line has a leader. This chapter leader must build up the right capabilities and people, equip them with the skills, tools, and standard approaches to deliver functional excellence, and ensure that they are deployed to value-creation opportunities—sometimes in long-term roles supporting the business, but more often to the small, independent squads. The chapter leader must evaluate, promote, coach, and develop his or her people, but without traditional direct oversight. Chapter leaders are not involved in the day-to-day work of squads; they don’t check on or approve the work of their chapter members, and they certainly don’t micromanage or provide daily oversight. Instead, regular feedback from tribe leaders, team members, and other colleagues inform their evaluations and the kind of coaching they provide. Since they’re not providing direct oversight, their span of control can expand greatly, a fact that can eliminate several layers of management. In fact, chapter leaders often free up enough time to tackle “real work” on business opportunities as well.

Go to https://www.mckinsey.com/business-functions/organization/our-insights/the-agile-manager?cid=other-eml-nsl-mip-mck-oth-1808&hlkid=1b8b41f7b12c45f09f57b7a12809227f&hctky=10391094&hdpid=8a3fd5bc-8a1d-47ae-a36b-85ee54d9761c