How does management evolve in scaled agile versus traditional program management?

WHAT THIS TESTS: This question tests whether you understand that scaling agile is not merely a process expansion but a fundamental shift in management philosophy. The interviewer wants to see if you recognize that LeSS explicitly rejects traditional management by controlling subordinates in favor of a style aligned with Lean Thinking and the Managers as Teachers principle. You are expected to contrast this enabling posture with the command structures found in traditional program management.

A GOOD ANSWER COVERS: First, explain that LeSS dramatically changes the manager role because self-managing teams delegate responsibilities downward and Product Owners decide what the team works on, which removes the classic manager function of task assignment. Second, describe the LeSS management style as rooted in Lean Thinking where managers act as teachers who develop people and improve the system rather than directing daily work. Third, contrast this with traditional program management which typically relies on a Theory X assumption that people dislike work and must be coerced, controlled, directed, and threatened to extract effort, leading to top-down dependency resolution and alignment by command. Fourth, note that in LeSS cross-team dependencies are handled through team self-coordination, communities, and clear product ownership rather than by inserting a hierarchy of project managers.

COMMON WRONG ANSWERS: A major red flag is proposing that scaled agile simply adds more project managers or program directors to coordinate dependencies. Another weak pattern is describing LeSS as just Scrum with extra meetings while ignoring the structural change in management accountability. Candidates who frame alignment as something leadership forces through detailed plans and Gantt charts rather than through product vision and clear priorities are missing the core distinction.

LIKELY FOLLOW-UPS: An interviewer might ask how you would coach a former command-and-control manager to adopt a teaching role. They may also ask what specific systemic impediments you would expect a manager to remove in a LeSS adoption, or how you would handle a situation where a Product Owner and a former engineering manager disagree on priorities.

ONE CONCRETE EXAMPLE: Imagine a company moving from a traditional program office that enforces quarterly milestones across five teams to LeSS. Under the old model, a program manager held weekly command meetings to resolve dependencies and reallocate resources when teams slipped. After adopting LeSS, the same leader stops assigning tasks and instead spends time removing organizational barriers like slow procurement, teaches teams to coordinate directly during multi-team Sprint Planning, and ensures the Product Owner has final say over the product backlog. Cross-team alignment shifts from status meetings to shared product ownership and transparent sprint reviews.

Source: less.works