Analytical-Mind

As I was heading back home, I wondered – is coaching something we do or the way we are? So once I got home, I looked up the definition for both words (coach & coaching) and came across Visual Thesaurus (image below).

The reason I was wondering is that when I meet people who “do coaching”, they always say “I’m a coach”. I’m not actually disputing that they are (or aren’t) coaches, it’s just that I wonder if they have assimilated the coaching role so much as to BECOME coaches. Maybe it’s simply like someone who defines himself as being an accountant, an engineer or a clown when in reality it is because their day-job is accounting, engineering or clowning.

This leads me to wonder, if accountants stop doing accounting after 5 pm, does it mean coaches stop coaching after work hours? It seems to me, based on the many coaches I personally know that very few actually stop coaching – that’s almost a way of being – coaching the kids, sometime the spouse, some of the friends and so on.

Should we call ourselves coaches only when we are on duty or is there a better name to describe bipeds who provide coaching to people around them?

Personally, I have decided a while back that I do not define myself as a coach. Coaching is simply a tool for me – a very effective one, I would add – that I use to help people accomplish their objectives.

My colleague François Perron launched a very interesting discussion on our private wiki – “As a coach, what to do when executives and upper management force the project team to do over time in order to meet deadlines?”.

As you can probably guess, this initiated very interesting discussions and an obvious reaction to such an approach.

Everyone agreed that due to the project visibility and the position of the organization within its market, the project launch date was critical. Everyone also understood that the organization had very few options so nobody debated the need to achieve results. The discussion was strictly around which measures to use in an Agile context.

I’ll admit up front that I am biased toward intrinsic motivation (I really loved Drive by Dan Pink) and the fact that it is well suited for an agile environment.

As such, my first impression to the conversation that was going on were:

• Does the organization wish that employees spend more hours at the office (attendance) or would they prefer more engagement (commitment)?
• If their choice is to increase the hours of attendance, imposing overtime will achieve this goal while giving them a false sense of increased performance. People will show they are working longer hours but the real throughput is unlikely to be much higher. In addition, software development is a brain intensive activity and reducing the amount of rest people get is likely to increase the number of mistakes they make.
• On the contrary, if the organization wanted more involvement, the inclusion of team members in determining the best way to achieve the results would probably come to a better decision – even possibly leading the willingness to do over time

It appears to me that by forcing overtime, the executives and senior managers will probably collect their bonus and congratulate each others in the short term only to realize in the longer term that they have simply pushed the problem forward for others to deal with – and possibly request more over time in the long run.

At the Agile 2010 Conference this week, out of the two hundred or so sessions presented, a number of them talked about the role of the manager in an Agile team. A few people believe managers are no longer necessary once the team has self-organized while others say people managers are still required. Either group failed to provide compelling arguments for their position.

The notion of self-organized teams keeps gaining visibility and acceptance. Those who have adopted the approach can’t stop talking about the benefits. At the same time, people realize that managers are unlikely to disappear from the organizational landscape anytime soon. In this context, it is with a mixed-feeling that Agilists talk about the role of the people manager in an agile organization – mostly as something not so useful but that the team needs to keep around in order to maintain their autonomy – something similar to the appendix.

The most common explanation for the appendix’s existence in humans is that it’s a vestigial structure which has lost its original function – source wikipedia

Then a few things happened.

First, I got to attend Michael Spayd‘s session called “Blueprint for an Agile Enterprise: Plans, Tools & Tech to Build a Human Enterprise”.

Want your whole organization to be more like an Agile team? Starting teams is well understood; expanding Agile to the organization is definitely not. Using 8 years experience applying organization development to Agile, we’ll unfold a 7 layer organizational architecture for building a human enterprise. Each level has an overall perspective, specific tools and key practices. Part tutorial, part demo, we’ll create a change plan for one participant’s organization, exploring culture, leadership, change, team performance, and management’s role. You’ll leave with a plan template and many ideas – source Agile 2010 Program

Then, I went to Damon Poole’s session called “Getting Managers and Agile Teams Out of Each Other’s Hair”.

One of the most talked about and least well understood concepts in Agile is the “self-managing” team. This session will provide a new perspective on self-management by examining the external roots of the practice and by taking a bottom-up look at what it is, the benefits, and how it works. We’ll see how twelve widely adopted Agile practices contribute to self-management by reducing and/or redistributing traditional management activities. These practices provide a framework for delegation, communication and coordination; and encourage team ownership, commitment and accountability – source Agile 2010 Program

Finally, I also attended Jim Highsmith session called “What do Agile Executives and Leaders Do?”

In some circles agile executives and leaders are admonished to buy pizza and get out of the way. In others they are asked to be supportive of self-organizing teams. But leading agile organizations requires more. There are specific activities that help build agile organizations that can weather business turbulence. This session will explore those activities that an agile leader or executive must “do,” including: revising performance measurements; facilitating self-organizing teams; developing strategies for operational, portfolio, and strategic agility; and assessing how agile to be source Agile 2010 Program

After the sessions, I sat in the lobby of the conference and read some of the blog feeds I subscribe to and came across these…

• Esther Derby’s ONE-ON-ONES WITH SELF-ORGANIZING TEAMS
• VersionOne’s Self Organizing and the “M” word

Obviously, something’s up!

The role of a traditional people manager

In many organizations and depending on their level, people managers are expected to plan, direct, organize and control (Deming‘s Plan-Do-Check-Act) – more specifically, the role of the manager is to:

• Define the individual objectives
• Assign work to team members
• Determine priorities of the tasks
• Monitor progress of the activities
• Make decisions for the team
• Get visibility into the work of the team
• Mentor and train employees
• Protect the team’s financial and human resources
• Provide career development opportunities
• Build relationships with other departments and teams
• Motivate the team members
• Communicate information

What self-organization removes from the equation

Once the concept of self-organized team is implemented, there are a few things that were traditionally the responsibility of the people manager that now fall on the team. The activities are:

• Assigning work – team members now select their tasks instead of the manager
• Determine priorities – team members now determine the order in which they should to complete their work
• Monitor progress – team members track their own progress and make it visible and accessible to those who need to know
• Make decision for the team – within the team, team members get to make their decisions
• Get visibility into the work – team members track their own progress and make it visible and accessible to those who need to know
• Mentor and train employees – when possible, team members may decide to implement a mentoring program within the team
• Motivate – self-organized individuals are known to be more motivated than traditional teams, hence the reduced need for the people manager to retain this activity

So what is left for the people manager?

In order for the people managers to transform into Agile leaders and feel as part of the team, we already stated they need to modify their role. The agile manager will achieve higher level of performance and possibly increased personal job satisfaction by macro-managing – working with an increased perspective as opposed to getting into the details. As such, the activities the agile managers need to retain are to:

• Define high level objectives for their team and department instead of focusing on the tasks
• Determine priorities in the objectives of the team and department instead of the activities
• Monitor progress toward achieving the objectives
• Coach employees
• Continue to protect the team’s resources
• Support employees in their career development
• Build relationships with other departments and teams

I realize that this type of transition is easier said than done but with the willingness to recapture an important role as part of the team and with some external help, the traditional managers don’t have to became extinct professionals.

Last week, I attended the breakfast conference presented in Montreal by Ken Schwaber.

As always, Ken gave a great presentation focusing on the “definition of done” in Scrum and the impact of incorrectly defining what done really means.

As I was listening to the presentation, I looked outside the window overseeing René-Levesque boulevard and noticed an asphalt truck and city workers filling a pothole – then it hit me… As interesting and valuable Ken’s presentation was, we need a systemic approach if we want Scrum to succeed in organizations. Let me explain…

Nobody likes to drive on a street with potholes. So what do cities do? Obviously, they fix them! If you live in Montreal, you realize that every year, the city fills thousands of potholes in an attempt to keep their streets in a good driving conditions but no matter how much efforts (and money) the city invests, the potholes keep appearing.

Isn’t this like implementing Scrum within an organization?

As attendees to Ken’s presentation, weren’t we simply like city workers attending an asphalt conference? It is as if an asphalt guru was explaining to us the right mix of tar and rocks to make the most resistant asphalt when in reality, the problem isn’t really with the asphalt itself but with the city’s traffic management approach.

Same goes for Scrum.

The definition of done is critical. The right people in the right roles is important. Dedicated teams members is crucial. But what about the managers in the organization? Are they supporting Scrum? I mean, are they really supporting the use of Scrum within their organization?

Don’t get me wrong. I truly believe doing Scrum the right way is critical but it is not sufficient to be successful. If your managers aren’t on board, you can try to implement as many of the Scrum best practices as you want – including the right definition of “done” – your teams will never reach the highest level of performance they could. Get the managers on board and your Scrum implementation will be greatly improved.

As Agile Coaches, we aim to be efficient. We analyze the situation around us, we ask questions, we experiment, we share our thoughts and observations, we make suggestions and recommendations. We try to be helpful.

Are we always efficient in the way we ask our questions? Could we ask our questions differently for better impact?

Below is a list of qualities associated with Powerful Questions taken from the reading material of the certification program I’m currently undertaking.

• Clarity
• Brevity
• Relevance
• Direct
• Single Subject
• Positive expression
• Allow silence for the response

To be powerful, the questions should also have an impact. To be impactful, the question should aim at:

• Personal issues and remain contextual;
• Motivation behind the actions;
• Consequences of the actions.

And include the question “what else?”.

What we are looking for in the levels of information provided is:

• Facts
• Emotions
• Opinions

Finally, to be truly powerful, the questions should take the person out of his comfort zone in order to explore new horizons. Questions such as the following are usually very helpful:

• What would happen if …?
• With hindsight, what can you see?
• If you were an expert in this field, what would you do?
• If you had a magic wand, what would you do?

Formulating a question isn’t always easy but to be an impactful coach, properly asking the question is critical. Hopefully, these few tips can help you become a better coach.

We are currently recruiting Agile Organizational Coaches.

Main duties and responsibilities

The Agile organizational coach works directly with the Information Technology and Business management teams to help leaders assimilate and apply the Agile principles to their day-to-day activities.

The organizational coach helps transform the traditional management style to a more Agile approach. Thus, the coach helps managers to properly assess the differences between the current situation and a set target. He then works with the managers to define a suitable plan and take concrete actions to address the obstacles encountered during the transition. More specifically, the organizational coach:

• Through appropriate training, educates managers to the application of  Agile to their management style;
• Creates groups (communities) of interest and exchange to assist managers in their development;
• Meets with various stakeholders to understand the fears, challenges, and resistance and provides the necessary support to help them;
• Participates in various management committees to train members of such committees and support them in their development.

Requirements

• Have held a management position within a large organization;
• A minimum of fifteen years of experience in managing software development teams;
• A minimum of two years experience in an Agile development environment;
• Significant experience in project management;
• Bachelor’s degree in business administration, commerce or management.

Assets

• Certified ScrumMaster;
• Bilingual (English and French);
• Experience in the financial sector (banking, insurance, investment);
• Certification from the International Coach Federation.

General Criteria

• Political acumen and diplomacy;
• Ability to find solutions win-win situations;
• Passionate and self-motivated;
• Team player;
• Talented facilitator;
• Understanding of business needs, business processes and organizational dynamics of a business.

If you are in the process of transitioning your organization to an Agile approach, you have certainly realized that moving to Agile impacts more than the software development team – if you haven’t realized it yet, you will eventually find out the hard way

In a large scale transition, it is necessary to work with the various managers to help them understand and assimilate the principles related to Agile and make them integrate those principles into their day-to-day actions. Therefore, an Agile Organizational Coach helps managers change their management approach to a leadership style better suited for an Agile environment.

The transition to a new leadership style is not limited to the software development teams. It also applies to the interactions and relationships with the business team’s managers. Making managers more Agile requires changes in their behavior, more specifically, it requires managers to:

• Transfer certain powers to the team members themselves so they can determine how best to accomplish their tasks;
• Define the desired vision, to adapt to the context of each team to ensure alignment with the overall objective of the project and ensure cohesion between the teams and their members;
• Accept and publicly endorse the idea that the status quo is no longer acceptable and that the old methods are no longer adapted to the new reality;
• Adapt their style of management when necessary to use an inclusive and democratic approach.

As such, the role of the Agile Organizational Coach is to:

• Educate managers through appropriate training;
• Create groups (communities) of interest and exchange to assist managers in their development;
• Organize individual and group meetings with various stakeholders to understand their fears, their challenges, their resistance and to provide the necessary support to help;
• Work with groups who require special support during the transition;
• Participate in management committees where the presence of an agile expert is required.

Following my posts on delivering results in an agile context, the 7 dimensions of an agile project team and their agile work environment, this fifth and final post on Agile Leadership presents the “Leadership” level of the model. I’m hoping to help managers, leaders, and stakeholders better understand which behaviors to modify in order to obtain better performance and improve employee satisfaction within their organization. I came up with five dimensions associated with Leadership in an Agile context.

Before I begin, I want to make a distinction between management and leadership. Over the years, the terms “leadership” and “management” have often been used as synonyms. To distinguish the two words I would specify that leadership is “transformational” in nature while management is more “transactional”.

Leadership

Leadership has been described as the “process of social influence in which one person can enlist the aid and support of others in the accomplishment of a common task” (wikipedia)

Servant Leadership

Servant-leaders achieve results for their organizations by giving priority attention to the needs of their colleagues and those they serve. Servant-leaders are often seen as humble stewards of their organization’s resources (wikipedia)

Management

Management in all business areas and human organization activity is the act of getting people together to accomplish desired goals and objectives. Management comprises planning, organizing, staffing, leading or directing, and controlling an organization (a group of one or more people or entities) or effort for the purpose of accomplishing a goal (wikipedia)

Goal Setting

Goal-setting ideally involves establishing specific, measurable, attainable, realistic and time-targeted objectives. Work on the goal-setting theory suggests that it can serve as an effective tool for making progress by ensuring that participants have a clear awareness of what they must do to achieve or help achieve an objective (wikipedia)

A few questions to assess the Goal Setting dimension of the Leadership model:

• Are the team members objectives aligned with one another?
• Are the suggestions coming from the retrospection of the team taken into consideration in the objective settings?

Performance Management

Performance management includes activities to ensure that goals are consistently being met in an effective and efficient manner (wikipedia)

A few questions to assess the Performance Management dimension of the Leadership model:

• Does the leader clearly define the objectives of his people?
• Does the organization measure its progress toward its goals?
• Is the performance measured at the team level in addition to the individual level?
• Does the company evaluate both the individual’s work behaviours and outcomes against the defined objectives?
• Do the team members receive timely and frequent feedback?

Remuneration

Remuneration is pay or salary, typically a monetary payment for services rendered, as in an employment (wikipedia)

A few questions to assess the Remuneration dimension of the Leadership model:

• Do managers mostly rely on intrinsic (rather than extrinsic) motivation?
• Does the remuneration model reflect the individual’s contribution to the team or is it based on seniority?
• Is the compensation model clearly understood by all team members?
• Is the leader rewarded for the development of his members?
• Do team members participate in the definition of the compensation of their colleagues?
• Is the compensation model strictly based on individual performance?

Coaching

Coaching refers to the activity of a coach in developing the abilities of coachees. Coaching tends to focus on the achievement by coachees of a goal or specific skill (wikipedia)

A few questions to assess the Coaching dimension of the Leadership model:

• Does the leader support its members in their skills and competences development?
• Does the leader take the time to teach his team members on how to increase their skills and better themselves?
• Is the leader selected by the team members?
• Is the leader evaluated by his team members?

Change Management

Change management is a structured approach to transitioning individuals, teams, and organizations from a current state to a desired future state (wikipedia)

A few questions to assess the Change Management dimension of the Leadership model:

• Does the leader work with the team members to establish a clear change management strategy?
• Does the leader acknowledge that the pace of change is different for all team members?
• Does the leader deal constructively for team members’ resistance to change?

Leader’s Qualities

Finally, in order to assess if the leader has the right qualities to be successful in an agile environment, I have selected a handful of qualities the leader should clearly demonstrate.

Does the Leader display the following qualities?

• Making decision when necessary
• Enthusiasm / Optimism
• Humility
• Respect
• Trust
• Integrity
• Confidence

If at any point while you read this post, you disagree with any of my statements, go ahead and click the “Leave a Comment” link. Express yourself!

While the original title of my post was “Why most software development managers need a leadership coach”, I changed it to “Why most managers need a leadership coach” because the situation I have witnessed in the software development industry is also present in many others specialized fields of expertise – at least that’s what many of the people I speak with confirm. Nonetheless, in order not to generalize my assumptions (yet!), I will share my assessment of the people management and leadership capabilities within the software development industry. Let’s begin…

Are you familiar with such problems?

• Unhappy employees leads to high turnover
• Communication challenges
• Employees fail to deliver on their commitment
• People who fail to deliver what they promise
• How To Deal With Problem Staff And Poor Performance

These are only a handful of typical problems encountered by a manager and for most experienced managers, they may sound trivial. Considering that new leaders are not born with management abilities, how can we expect them to be successful in their role?

People managers lack the basic skills

Here’s why I believe most software development managers (and many others) need coaching to become successful in their role (and apparently, I am not the only one who believes this is a valid suggestion). My logic goes as follows:

• Managers – including software development managers – are people;
• There are 2 ways to become successful at something. Either you learn through education or you possess above average intuition and intelligence and can figure out how things need to be done;
• Most software development managers have a technical training /education (examples can be seen here, here, here, and here);
• In addition to their education background, most software development managers mostly played technical roles (software developers, business analysts, application architect, etc.) in their career prior to getting promoted to a management position;
• Most people management positions are complex and require knowledge and experience outside of technology such as Business, Leadership, People Management, Organizational Development, or Psychology;
• Very few people in people management positions have all the requirements (see previous bullet);
• Without prior education and experience outside the software development sector, most managers are ill-equipped to successfully perform in their role.

Coaching is a solution

With an average salary¹ of $85,000 to $125,000 depending on the number of years of experience and location, why wouldn’t an organization invest a few thousands of dollars to hire a coach in order to help develop the people management and leadership abilities? Despite the economic downturn, I still see organizations spend thousands of dollars on training or conferences. Although I don’t argue the value of such events, I doubt they support the development of people management and leadership abilities.

It seems to me that we need to help those in management position succeed. Otherwise, the performance of the entire team will suffer.

Not convinced?

Others seem to agree with this new trend…

1.- Sources:

• The 2010 IT Salary Guide
• Monster.ca Salary Wizard
• Payscale Salary Survey

In the spirit of International Coaching Week, I am offering 10 hours of leadership coaching (for free) to a leader in need. Since “96 percent* of clients report they would use coaching again to achieve personal and professional life goals such as work-life balance, increased self-esteem, productivity and much more“, this is an opportunity for you to try a coach.

In honor of annual International Coaching Week (ICW), Feb. 7-13, ICF Chapters and coaches everywhere will take time to recognize professional coaching and what it offers by hosting various coaching events within their local communities. This includes pro-bono coaching services, such as free coaching sessions, educational lectures and workshops for the public.

“This week is the perfect time for coaches to get out in their communities and show people what coaching is and how it can benefit their lives,” said ICF President and Master Certified Coach Giovanna D’Alessio. “Coaching is proven to help people attain their personal and professional goals and those who use it can expect to see a solid return on their investment.”

If you ever wondered if a coach can help you achieve better results faster, I invite you to send me an email (martin [at] analytical-mind.com) with the following information:

• Description of the professional objective you are hoping to achieve.
• Why you think a leadership coach could help you achieve your objective?
• Why YOU should be selected?

I am donating 10 x 1-hour sessions to one leader in need to help you achieve your goal. The sessions will take place over the phone (skype) at the rate of 1 session per week. You have until Saturday February 13th to submit your profile and I will select the coachee on February 15th. I am confident you will enjoy the experience.

*2009 ICF Global Coaching Client Study.