Tag Archives: Agile Leadership

Agile Lessons We Can Learn From Sports

I think there are a lot of lessons we can learn from sports – particularly about the importance of character, integrity, teamwork, and values.

There’s been a lot in the news lately in the US about the conduct of some sports celebrities (Ray Rice of the Baltimore Ravens and others). Some people have questioned why we should hold sports celebrities to a higher standard than other kinds of employment. For example, a normal company wouldn’t necessarily fire an employee for beating their kids or having a public altercation with their spouse; but that behavior isn’t acceptable in a sports celebrity. I think there’s a couple of good reasons for holding sports celebrities to a higher standard.

  1. The first reason is that they provide an important role model for kids and others to follow. I just saw a short story on TV about Deandre Jordan (the center for the LA Clippers) that is a great example of that – it showed him working with a bunch of 9-10 year old kids on a basketball team to teach them the importance of character, integrity, and teamwork in sports. That’s the kind of positive role models we need in sports – people who go beyond what’s expected to try to have a positive influence on people in the communities that they are part of. Kids and others in the community look up to people like that and we need more role models like that.
  2. The second reason is probably more directly relevant to Agile Project Management. One of the important factors that binds a high performance team is that they share a set of values and a sense of purpose that goes beyond just showing up for work, doing their jobs, and going home at the end of the day. Their jobs are an extension of the way they live their lives and there’s a real sense of purpose and values behind it. They are also really true to those values – it isn’t just something that they practice in public and put aside when it’s not publicly visible.
  3. If we lower our standards to the level that it’s OK for people (particularly prominent sports celebrities) just do their jobs as long as they don ‘t do anything outside of work that might be considered a crime, it seems to me that we’ve let our standards drop too far. I’m proud to be part of the Agile Project Management community and part of some very dedicated and principled people who hold ourselves to a higher standard.

Are Corporate Culture and Values Really Important?

Are corporate culture and values really important? The controversy that is currently brewing in the Boston area over the “Market Basket” grocery supermarket chain is directly related to the conflict between Agile and traditional project management. “Market Basket” is a chain of about 71 grocery supermarkets in New England that generates about $4 billion in annual revenues – it has been a family-run business founded and managed by the DeMoulas’ family for several generations.

(Source: http://en.wikipedia.org/wiki/DeMoulas%27_Market_Basket)

Arthur T. Demoulas is currently the CEO of the company and has been highly regarded by all company employees and customers for building a strong company culture based on the strong leadership and values. However, some other members of the Demoulas’ family who have an ownership interest in the company didn’t see it that way… They felt that Arthur T. wasn’t paying enough attention to the bottom-line and was putting too much emphasis on corporate culture and values including developing a clearly-defined brand image with very strong employee satisfaction and strong customer loyalty. So, they fired him as CEO and hundreds of employees who were intensely loyal to him promptly walked out of the company in protest. Customers have also started boycotting the stores in response to his firing.

The company has been paralyzed for the past few weeks in the midst of this controversy as deliveries by suppliers have almost stopped because there are no employees to accept deliveries and stock the shelves and customers have walked away. It appears now that Arthur T. is going to buy out the other shareholders in his family to gain a majority and controlling interest in the company. The Boston Globe magazine had several excellent articles on this on Sunday 8/24/2014 – here’s an excerpt of one of them:

“Under CEO Arthur T. Demoulas, Market Basket had a winning business model: He treated employees, managers, and customers as members of a common enterprise, from which everyone gained. Arthur T. rolled out a 4 percent discount on nearly all goods at the beginning of 2014, arguing his customers could use the money more than his fellow shareholders. He paid his employees and managers decent wages, and he treated them with respect. He made sure they understood the objectives, and then let them decide how to achieve them. The greed team that ousted Arthur T., by contrast, is running the company as if they’re take-it-or-leave-it martinets and everyone is losing.”

“At least one of the bidders who emerged to buy Market Basket was said to be offering more than Arthur T. was offering. They said they can squeeze more profits out of the company than when Arthur T. was CEO. They’re deluding themselves. Arthur T.’s business model worked precisely because he didn’t follow this route. Trying to squeeze out more profits will drive customers away, destroy employee loyalty, and increase worker turnover.”

“There’s abundant evidence that a company organized as a common enterprise does better over the long term than a company designed to maximize shareholder returns over the short term. Arthur T.’s business model wasn’t based on zero-sum thinking. He understood that giving everyone a stake in the business would generate gains for everyone, including the shareholders.”

“The reactions to Arthur T.’s ouster proves the point. Customers are staying away from Market Basket stores, even though its costing them, forcing them to buy more expensive food elsewhere. Striking employees are sacrificing paychecks and risk losing their jobs, but giving in means getting stuck with new CEO’s and a board that are likely to cut pay and raise prices. Local politicians have weighed in with some statements of support. This isn’t the age-old labor versus management conflict. It’s labor, management, customers, community, and fired CEO versus greedy directors – something rare in the annals of American business.

(Source: Reich, Robert, “Anatomy of a Meltdown”, Boston Globe, Globe Magazine, 8/24/2014, p 20)

What does this have to do with Agile Project Management? I believe that the conflict between a bottom-line, numbers orientation that focuses on results and a more systemic and holistic approach that focuses on people, culture, and values and other factors that drive results is also one of the key issues behind the conflict between traditional plan-driven project management and Agile.

In 2003 I published a book called “From Quality to Business Excellence – A Systems Approach to Management” which is directly related to this problem. The figure below is a diagram from that book:

Business Excellence Model

(Source: Cobb, Charles, “From Quality to Business Excellence, ASQ Quality Press, 2003)

The idea behind this is that many companies are very short-sighted and reactive – they focus primarily on bottom-line results and when the numbers in a given quarter don’t meet expectations, they try to take some kind of corrective action without really understanding the cause-and-effect relationships that drive those numbers. This can lead to erratic and unpredictable performance. Companies who take a more systemic approach and understand these relationships are able to be much more proactive by focusing on at a deeper level on the performance drivers behind the numbers rather than simply reacting to the end-results. That should result in more consistent, sustainable, and predictable performance.

This pendulum has swung back-and-forth – should a company focus only on bottom-line results or focus on the internal factors like customer loyalty and employee satisfaction that drive bottom line results? The Market Basket controversy here in the Boston area is a perfect example of that. In the 1980’s and 1990’s many leading companies and enlightened managers successfully developed this kind of softer leadership approach that Arthur T. Demoulas is noted for; however, over the years since then, increasing pressure to produce fast-paced, short-term results has caused many companies to lose sight of this concept. To some people, the focus on numbers and bottom-line results may seem incompatible with a focus on some of the softer issues like corporate culture and values; however, enlightened companies and managers are able to successfully develop what I call a “systems approach to management” to achieve both.

Traditional plan-driven project management is also very results-oriented and numbers-oriented with a focus on meeting planned costs and schedules and many people see that approach as incompatible with Agile that focuses heavily on a softer leadership approach, an emphasis on culture and values, and empowered, self-organizing teams. I don’t see those approaches as mutually exclusive and focusing on one of those extremes or the other is not likely to produce optimum results. I think it’s naïve to believe that you can focus on company culture and values and empowered employees alone and the bottom-line numbers will somehow come out right as a result; but its equally problematic to focus on bottom-line results only without an appreciation of the factors that drive those results. The right balance of these two approaches will vary from one situation to another but, in general, a focus on both is needed to some extent to achieve optimal results.

Was Steve Jobs an Effective Agile Leader?

Was Steve Jobs an effective Agile leader? I watched the movie “Jobs” this weekend about the life of Steve Jobs and his career at Apple and it was very thought-provoking.  Steve Jobs was absolutely brilliant, embodied a lot of Agile values, and he was enormously successful in developing some very innovative products in a relatively short amount of time that made Apple very successful;  but he was ruthless, tyrannical, and very insensitive in his relationships with people.  I was thinking – is that style of leadership really consistent with Agile and is it an effective style of leadership for an Agile environment?

  • Much of the thinking behind Agile is based on the idea of empowered and self-organizing teams where the product definition bubbles up rather than being driven down from above,  Steve Jobs’ leadership style doesn’t seem to be very consistent with that model, but he was very successful in getting things done.
  • Another thing that seems to be not entirely consistent with Agile is that Agile is based on the idea of teams working at a “sustainable pace” and it was apparent that many of the teams that worked under Steve’s direction at Apple worked incredible hours to get things done but they were very passionate and dedicated to their work.

Here are some quotes from Steve Jobs that indicate his values that are related to Agile:

  • Focus and Simplicity – “People think focus means saying yes to the thing you’ve got to focus on. But that’s not what it means at all. It means saying no to the hundred other good ideas that there are. You have to pick carefully. I’m actually as proud of the things we haven’t done as the things I have done. Innovation is saying no to 1,000 things…
    “That’s been one of my mantras – focus and simplicity. Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.”
  • Planning – “Again, you can’t connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something – your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.”
  • Quality – “Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.”
  • Innovation – “Sometimes when you innovate, you make mistakes. It is best to admit them quickly, and get on with improving your other innovations.”
  • Requirements and Customer Needs – “You can’t just ask customers what they want and then try to give that to them. By the time you get it built, they’ll want something new
  • Seeing the “Big Picture” – “A lot of people in our industry haven’t had very diverse experiences. So they don’t have enough dots to connect, and they end up with very linear solutions without a broad perspective on the problem. The broader one’s understanding of the human experience, the better design we will have…To turn really interesting ideas and fledgling technologies into a company that can continue to innovate for years, it requires a lot of disciplines.”
  • Continuous Improvement – “I have a great respect for incremental improvement, and I’ve done that sort of thing in my life, but I’ve always been attracted to the more revolutionary changes. I don’t know why. Because they’re harder. They’re much more stressful emotionally. And you usually go through a period where everybody tells you that you’ve completely failed.”
  • Tools – “It’s not the tools that you have faith in – tools are just tools. They work, or they don’t work. It’s people you have faith in or not.”
  • Leadership Style – “It’s not about charisma and personality, it’s about results and products and those very bedrock things that are why people at Apple and outside of Apple are getting more excited about the company and what Apple stands for and what its potential is to contribute to the industry…The people who are doing the work are the moving force behind the Macintosh. My job is to create a space for them, to clear out the rest of the organization and keep it at bay.”

And one of his most famous quotes that really sums up his values is “Stay hungry, stay foolish”.  The source of the above quotes is:

http://www.brainyquote.com/quotes/authors/s/steve_jobs.html

My thoughts on this are that:

  • Steve Jobs definitely had some “rough edges” in his relationships with people but he embodies many of the characteristics of an effective Agile leader
  • There probably isn’t one leadership style that is effective in all situations and some “out of the box” thinking is definitely worthwhile rather than implementing some kind of “textbook” Agile approach in all situations

What do others think?

 

Using an Adaptive Leadership Style in Agile

I’ve been a Project Manager for many years and, over the years, I’ve gone through a lot of job interviews, particularly as a consultant where you might change roles every 3-6 months. One of the questions I’ve been asked in interviews is “What is your leadership style?”. My answer to that is I use an “adaptive leadership” approach; that is, I think that’s there’s not just one leadership style that works all the time and that is particularly true in an Agile environment. You have to adopt an adaptive leadership style in Agile that is appropriate for the situation.

How does that apply to Agile Project Management? There is a popular stereotype in the Agile community that all project managers are only capable of operating in a “Command and Control” leadership style. I’m sure that is an exaggeration, but it is true that many project managers have a tendency to assume a somewhat directive leadership style. For years, that has been an essential characteristic of many project managers – you can’t just sit on the sidelines and let a project run its course without some kind of direction and leadership. Agile changes that paradigm dramatically by emphasizing self-organization and empowerment of the team and positions the Scrum Master in the role of a “Servant Leader” to support the team rather than leading and directing the team. So, where does that leave the project manager? What value does he/she provide to an Agile team? I think the appropriate answer to those questions is that “it depends”.

A lot of people will say that a project manager can’t possibly play the role of a Scrum Master because the roles are so different. I don’t necessarily agree with that perspective…that perspective is based largely on the stereotype that all project managers are only capable of operating in “command and control” mode. I believe a good project manager has learned over the years to develop an adaptive leadership approach that’s appropriate for the situation and I think that’s very appropriate in an Agile environment.

There is an idealistic Agile view that all Agile teams are totally self-organizing, completely empowered, and require little or no direction or leadership. The team, as a whole, should function on its own without much direction at all – that’s true to some extent, but a more pragmatic view is that all teams aren’t necessarily at that level of maturity and some leadership is needed to help them get to that point. “Adaptive leadership” is an important skill in this kind of environment…a good Project Manager or Scrum Master should be capable of providing a sufficient level of leadership to get the team to a level of self-sufficiency and progressively back out as the team reaches that level.

“Adaptive Leadership” or learning to adapt your leadership style to the situation is a very important characteristic for project managers to be successful in an Agile environment.