Managers Are People, Too!
Managers Are People Too - Picture by Ryan Ripley

Managers Are People, Too!

I'm working my way through Scott Ambler 's article about the Agile Community and their apparent incontinence. While I'm not sure, someone who sold out to the PMI for millions of dollars then gets to wag their finger at the collective Agile Community. He has some solid points about how we all collectively messed up and how we can do better in the future.

One particular idea that often strikes a chord with me is the stance the Agile Community takes toward managers, directors, VPs, and Leadership. Management is treated as the enemy. This toxic stance had done far more harm than good to teams and organizations.

A recent example is a LinkedIn post I created that started like this:

"Your boss should be your next Scrum Master. A manager or director is best positioned to help a Scrum Team effectively deliver value to customers and the organization."

As you can imagine, the majority of the comments were not supportive. (Check them out here if you want to dig into the fray.) The comments range from "My manager is far too busy to help our team" to "My manager's command and control style would destroy our team's ability to self-organize."

Another response of many given:

Managers do not have the required time or patience. Many do not have minimal people skills. Few managers believe they personally should be growing their people.

Agile purity is undoubtedly at play here, as is a large amount of hubris. The managers and directors in many organizations are quite intelligent and have worked their way up the corporate ladder through the muck that is office politics. They are connected, capable, and hungry for success (delivery of value.) It might surprise many that most managers primarily care about their employees and are not looking to make their lives miserable.

As the community turned its nose up at managers, it also ignored management disciplines such as change management, risk management, measuring and validating value (EBM!), practical goal setting (EBM!), technology road mapping, and governance. While these are not the most exciting topics, they are critical considerations when working with mature organizations.

However, the attitude towards management and leadership is the far greater problem.

We often downplay the manager's role in strategic thinking and planning: "Self-organizations" and "self-management" are often used a bat to club a manager for getting involved rather than ideas designed to empower teams to decide "how" to do their work. Neither "self-organization" or "self-management" mean in the exclusion of management and leadership. Team still need long-term organizational plans and goals, along with budget and a corporate vision.

Agile consultants and practicioneers are often dismissive of managers and leadership structures: Rather than seeing management as a strategic partner, they are viewed and painted as obstructionists. How many times have managers been labeled as "resistant to change" or even as "impediments?" I've even seen instances where managers were targeted as the "old way" that the transformation was meant to disrupt. It shouldn't be shocking to see managers and leaders acting with skepticism about future agile initiatives.

We've undervalued the experience the managers bring to the table: The managers and leaders we think we are working to disrupt have years of experience and expertise in the organization and could be especially useful with improving delivery and outcomes. Rather than leverage this expertise, the preference is often to dismiss these leaders who have deep industry knowledge.

We didn't pop the Scrum Bubble: Broader organizational goals are important. Managers and leaders work towards these goals and needs the support of individuals and teams to be successful. The overemphasis of coaching and working with teams rather than the wider organization causes friction between team goals and the broader organizational objectives. Scrum Masters - the Agile Coaches of the organization - focused too much on Scrum and the Scrum Team and not enough of the needs of leadership and management.

It's time for the Agile community to stop treating managers and leaders as the enemy and start seeing them as essential partners in driving success. One key partnership going forward is seeing more managers fullfil the Scrum Master accountabilities.

It’s time to evolve and learn from our mistakes, bringing leadership back into the fold. The future of Agile depends on it.



David Owens

Sr. Full Stack Java Developer - Rest and Microservices - Relational and No SQL Databases. Technical Business Analyst capable - Application Support

11mo

We have some problems here. You can't use leadership and management as if they are interchangeable, they are not. Virtually no one who has experienced management understands it as the same as leadership. You haven't asked the question regarding why agile is resistant to management. You assume it is a fault. Perhaps it is. But you are championing a process that prides itself on empiricism, so it seems incumbent that your argument spends more time on the why here. Don't just start from the framework that management is great let's have some more of it. For one simple thing to ponder. Why do you feel that Dilbert resonates as well as it does in the office. Perhaps if something regularly denigrates management, trendy buzzwords, HR, offshoring as much as Dilbert does and it is pinned in so many offices and cubicles that it is on to something? Let's look at your caption for your picture. Managers Are People Too! Well let's examine that in the backdrop of the layoffs that have been happening. Let's examine that in the light of the reports we have been hearing about the number of pregnant women being laid off. Let's examine that Let's consider reports of people not able to leave their place of work during natural disasters out of fear.

Like
Reply
Mary Miller

Senior Project Manager | Former $25M Project Leader | Helping successful leaders stop pushing through exhaustion and start thriving

11mo

I had to think through this one some more. If there is one thing, these posts were thought provoking! On one hand, I have been what private industry would consider more of a program manager, and I definitely encountered some of the challenges you point to in this article. It was really disempowering because I had the relationships to make things happen that the Scrum Master struggled with. I have also been the “Scrum Master” who gets frustrated when I have to do things because it is mandated, and compliance is required even though others could see more overhead was being created. I am still not sure if I would want a boss as a Scrum Master. However, I could get a Program Manager, Director, VP being a Scrum Master. They have a lot more influence. What I think you are pointing to is a paradigm shift in how Agile is implemented. Work has evolved since the Agile Manifesto was created. There will always be the Zombie implementations of Scrum and managers who have room to grow. But, maybe the people with greater influence can do more to create a great working environment. After all, that was part of the opportunity of higher levels of management.

Peter Sealy

Results-driven program management for technology transformations and complex projects | Cross-functional team leadership | Complex problem resolution | CCPA compliance | PMO | Seasoned consultant | FinTech & Wall Street

11mo

For me, the traditional Scrum model was missing two things: prioritizing the top-down corporate goals (the product owner is just supposed to magically do that), and coordinating work with other scrum teams and/or departments outside the scrum structure. Those are both places where a traditional middle manager can provide great value, with their knowledge of the corporate structure and relationships across it.

Jeffrey Davidson

Enterprise & Team Transformation - Helping you and your teams accelerate and deliver

11mo

Thank you, Ryan. This is a needed push back against the knee-jerk response that management is the problem.

Julie Singh

Enterprise Agility Champion

12mo

I love the sentiment and challenge in your post (not because I am a manager) but because I promote Agile frameworks and Product thinking. Having been an Agilest and now championing Agile teams to succeed from the management side, I will say that more leaders need to learn and adopt Agile, if they want agility and flow. Otherwise, they cannot help where agility needs management to break barriers for them. It is hard for an Agilest to drive agile culture when their impediments are misunderstood or not understood at all.

To view or add a comment, sign in

Others also viewed

Explore content categories