Skip to content

Posts from the ‘agile’ Category

Self-organization and independence aren’t the same thing

Picture by Frédéric EsplandiuAgile relies and promotes the concept of self-organized teams but the concept is still misunderstood – except maybe for Jurgen who explains it very well in his book.

Even within Pyxis where we push the concept of self-organization to the entire organization, people often mistake independence and self-organization.

Here’s an attempt at distinguishing the two perspectives.

Independence is a condition of a nation, country, or state in which its residents and population, or some portion thereof, exercise self-government, and usually sovereignty, over its territory. – wikipedia

Independence is strongly tied to self-governance which is defined as:

(…) an abstract concept that refers to several scales of organization. (…) It can be used to describe a people or group being able to exercise all of the necessary functions of power without intervention from any authority which they cannot themselves alter. – wikipedia

On the other hand, self-organization is defined as:

the process where a structure or pattern appears in a system without a central authority or external element imposing it through planning. This globally coherent pattern appears from the local interaction of the elements that make up the system, thus the organization is achieved in a way that is parallel (all the elements act at the same time) and distributed (no element is a coordinator). – wikipedia

Although in both cases, no authority interferes with the organization of the people, self-organization emerges when there is no planning of how people will work together. In addition, the notion of imposed constraints appears when discussing self-organization.

As such, while independence could mean “We can do what we want, how and when we want”, self-organization means “We are free to operate how we wish within the defined constraints in order to achieve the established objectives”.

As I recently described, immature self-organized teams are often selfish and irresponsible:

Team members are happy to take advantage of being self-organized but only as long as it benefits them and that there are no increased responsibilities. Once a situation negatively impacts them (while benefiting the team), they aren’t willing to cooperate and when they are asked to take accountability for something, they shy away from the responsibility. In a nutshell, these individuals want the best of both worlds. To successfully transition to self-organization, it is critical to explain that they will need to make a decision and pick self-organization with responsibility or freedom outside the self-organized team.

Consequently, true self-organization means that people take full accountability for their actions and do what ever it takes to get organized as a group in order to operate within the imposed constraints.

Once presented with self-organization, people and teams quickly assume that they now fully control their destiny – which is incorrect. The additional detail that needs to be added is “within the imposed constraints” which means resources are limited and an objective has been established. So unless you are in control of the resources or have officially been delegated authority for the resources, you have the option of self-organizing, not becoming independent.

Software developers as commodities

Demand for software developers is unlikely to drop over coming years. I suspect the contrary is more likely to happen as demand for technology workers will continue to increase while North American universities produce less graduate developers.

That’s good news if you are a software developer as the demand is likely to continue exceeding the supply for many years. If you are on the market for a new job, your chances of finding another job are pretty good.

That’s also good news if you are an organization who offers software development services to customers. The trend showing that organizations are not staffing up to their full need and prefer to hire external temporary help (consultants) to complete their projects.

So all is well in this perfect world, right?

Well, it depends. If your goal is simply to get “a job” things are OK for you – send your resume to an organization that is recruiting and if you successfully go through the various steps of the recruiting process, you’re in. Congratulations! If at first you don’t succeed, try again a few more times and chances are you will get into one of the hiring organization.

If you are looking for interesting projects or projects inline with your personal goals and aspirations things might be more complicated. How do you ensure you are the one selected for that special project?

If you haven’t realized it yet, software developers are commodities. There simply isn’t much differentiation between software developers. I don’t mean to be disrespectful and as such, I won’t attempt to compare software developers to other commodities but the fact remains that there are very few ways to distinguish software developers.

In marketing, product differentiation is the process of distinguishing a product or offering from others, to make it more attractive to a particular target market. This involves differentiating it from competitors’ products as well as a firm’s own product offerings – Wikipedia.

The question that comes to mind is “What are you doing to stand out of the crowd?” and “What are your differentiating factors?”.

One differentiating factor that is slowly appearing in job descriptions is the requirement for “Agile software developers”. Although a step in the right direction, this is likely to mean very little in the near future as the definition of an agile software developer still needs to be agreed upon.

If you are part of an organization that offers software development services, what are your differentiating factors? Ours is simple, we offer immersion and highly performing software development teams that are ready to make a substantial impact from day 1.

What are your differentiating factors?

Great news the project is over! Now let’s dismantle the team

Image by pgcCongratulations, you have finally delivered the project! The team you have carefully assembled over many months can now be dismantled and people can go back to their normal job. That’s the natural sequence in the project management world – project is kicked-off, team is assembled, team develops solution, team encounters delays, team tests solution, team moves solution into production, team hands-off solution to maintenance team, project team is dismantled, and life goes back to normal.

I wonder if the Green Bay Packers will do the same now that they have won SuperBowl XLV or maybe the San Fransisco Giants may want to start their 2011 season with new players after winning the 2010 World Series. At least the F.C. Internazionale Milano should want to give it a fresh start after winning the Serie A championship, wouldn’t you think?

Nobody would consider breaking up a highly performing sport team but when it comes to software development, it is common for organizations and departments to split up team members and start new with their next project.

From a purely practical perspective, breaking up a performing team makes no sense considering the time invested in:

  • carefully selecting and recruiting the right people with the right skill sets and the right attitude,
  • hiring external consultants with specific skills to complement the existing team,
  • getting the team to work together despite the team members’ personalities, work methods and obvious looming conflicts,
  • training people on the organizational culture and business activities,
  • establishing a leadership style that will work well with the team’s expectations,
  • eliminating the bad hires,
  • building relationships with the team members and between the project team members themselves,
  • etc.

Team members need time to become highly performing. Why not keep those team members together after the completion of their project and assign them together to the next project – even if the skill sets doesn’t seem to be perfect at first glance?

Martin Proulx (Analytical-Mind) to celebrate International Coaching Week with free leadership coaching

In celebration of International Coaching Week, February 6–12, 2011, I am pleased to offer as I did last year, 10 hours of leadership coaching.

See what Louis had to say about his coaching experience:

I contacted Martin to help me transitioning to a senior role in the banking industry. He always used appropriate questions to bring my reflection to the right point, allowing me to accelerate thoughts I could possibly have but on a much longer period of time. Martin is smart, clear and articulate and efficiently interfere with a minimum number of words to help in the evolution of the reflection. Our coaching sessions helped me to improve my management skills, and I would definitively recommend him!

Coaching is partnering with clients in a thought-provoking and creative process that inspires them to maximize their personal and professional potential. Coaches work with clients in many areas, including business, career, finance, health and relationships.

Image by seier+seierIf 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[dot]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 who wishes to achieve a specific goal. The sessions will take place over the phone (skype) at the rate of 1 session per week. You have until Wednesday, February 16th to submit your profile and I will select the coachee on February 19th. I am confident you will enjoy the experience.

International Coaching Week (ICW) is a weeklong global celebration of the coaching profession held each February since 1999. ICW is a designated time for coaches and clients to educate the general public about the value of working with a professional coach and to acknowledge the results and progress made through the coaching process. During this extended commemoration, coaches around the world offer a variety of activities and pro bono services in their local communities to share what coaching has the ability to do. For more information about ICW, visit www.coachingweek.org.

The International Coach Federation is the leading global organization for coaches, with more than 16,000 members in more than 90 countries, dedicated to advancing the coaching profession by setting high ethical standards, providing independent certification, and building a worldwide network of credentialed coaches. The ICF is the only organization that awards a global credential which is currently held by over 5,700 coaches worldwide. For more information about the ICF, please visit our Web site at www.coachfederation.org.

The Carrot Principle – Using Recognition to Increase Team Performance

Increasing teams and departmental performance – isn’t this why most organizations adopt the Agile principles?

Although there might be other reasons, many of the organizations we work with aim to increase their teams’ performance. I recently read The Carrot Principle – How the Best Managers Use Recognition to Engage Their People, Retain Talent, and Accelerate Performance – to see how recognition may help increase teams’ performance.

While many organizations still believe an above average salary is enough to keep people motivated, salary alone is not a good motivator. As Daniel Pink described, above an acceptable base salary, salary no longer is a good motivator. As such, managers often look for alternate ways to keep their team motivated.

The fact is that money is not as powerful a reward as many people think. While pay and bonuses must be competitive to attract and retain talented employees, small amounts of cash – anything short of $1,000 – will never make the best rewards because they are so easily forgotten – The Carrot Principle.

Recognition is deemed an important source of motivation and is usually used to maintain a low employee turnover rate and, increase employees’ performance and business results. Many organizations who adopt Agile practices recognize that it is increasingly difficult to attract top talents and in order to remain competitive, they should focus on increasing the performance of their existing work force.

Engaged employees demonstrate: innovation and creativity, take personal responsibility to make things happen, desire to contribute to the success of the company and team, have an emotional bond to the organization and its mission and vision.

U.S. Department of Labor statistics show the number one reason people leave organization is that they “don’t feel appreciated” – The Carrot Principle.

The book relies on surveys done by HealthStream Research and supported by data from Towers and Perrin. Below are some of the conclusions derived from the data:

  • Companies that effectively recognize excellence enjoy an ROE (return on equity) three times higher than the return experienced by firms that do not;
  • Companies that effectively recognize excellence enjoy an ROA (return on assets) three times higher than the return experienced by firms that do not;
  • Companies in the highest quartile of recognition of excellence report an operating margin of 6.6 percent, while those in the lowest quartile report 1 percent.

The authors point out that to be impactfull recognition should be combined with what they call the basic four areas of leadership:

  1. Goal Setting: defining the purpose of a task and tying it to a desirable end result
  2. Communication: discussing issues and sharing useful information with employees, welcoming open discussions
  3. Trust: keeping his word and owning up to his mistakes, maintaining a high ethic and positively contributing to the reputation of the organization
  4. Accountability: ensuring people deliver on their commitments.

Recognition can take many forms but whatever it is, the best reward is always personal and tailored to employees interests and lifestyle, given by a manager who cares enought to find out what motivates each individual - The Carrot Principle.

Finally, the book presents four levels of recognition:

  • Day-to-Day recognition: low-cost but high touch recognition such as Thank You notes to encourage small steps leading toward success
  • Above-and-Beyond recognition: provide a structured way to reward significant achievments that support the company’s core values
    • Bronze: to recognize on-time above and beyond related to core values
    • SIlver: reward on-going above and beyond behaviors for consistently demonstrating company’s values
    • Gold: behaviors that produce bottom-line results
  • Career recognition: recognize people on the anniversary of their hire
  • Celebration and events: celebrate successful completion of key projects or new product launches.

Cracking the Code for Standout Performance – Applying the approach to Agile Teams

I just finished reading Great Business Teams: Cracking the Code for Standout Performance.

In Great Business Teams, renowned business consultant Howard M. Guttman takes you inside some of the world’s most successful corporations—Johnson & Johnson, Novartis, Mars Incorporated, and L’Oréal, to name a few—to discover how a powerful new high-performance horizontal model has changed the way leaders lead, team members function, challenges are met, and decisions are made. He also reveals how and why the organizations that have implemented this innovative team structure have become great companies, able to ride the crosscurrents during lean times and truly soar when opportunities arise.

As Agile team coaches or organizational coaches, we aim to increase the teams’ performance in an attempt to deliver better results. We improve quality, help the team work more efficiently, and have fun while delivering increased business value. Interestingly, many of the observations presented in Great Business Teams: Cracking the Code for Standout Performance are in line with the Agile values and principles. Here are some of the keys points to remember:

1. Great Business Teams are Led by High-Performance Leaders who:

  • Create a “burning platform” for fundamental change;
  • Are visionaries and architects;
  • Know they cannot do it alone;
  • Build authentic relationships;
  • Model the behaviors they expect from their team;
  • Redefine the fundamentals of leadership.

Isn’t this what we would expect of the Product Owner in Scrum?

Interestingly, the author positions the process by wish the leader achieves these objectives by asking tough questions such as:

  • What is the business strategy and how committed are we to achieving it?
  • What key operational goals flow from the strategy and how do we make sure these goals drive day-to-day decision making?
  • Are we clear on roles and accountabilities?
  • What protocols or ground rules will we play by as a team?
  • Will our business relationships and interdependencies be built on candor and transparency?

Hence, the support of an external coach is useful and can help the leader ask powerful questions.

2. Members of Great Business Teams are Us-Directed Leaders

Members of great business teams think of themselves as accountable not only for their own performance but for that of their colleagues. Similar to the concept of self-organized teams, great business teams typically take accountability to achieve their objectives.

On high-performing teams, accountability goes well beyond the individuals recognition that he or she is part of the problem. It even goes beyond holding peers on a team accountable for performance. “Us” accountability includes holding the team leader accountable as well.

3. Great Business Teams Play by Protocols

Once a leader with the right skills is in place and supported by a self-organized team, the group needs to agree on the rules they will play by. Obviously, the more structured its way of working together, the less likelihood of misunderstanding, conflict or costly delays and bottlenecks the team will encounter.

One important set of protocols related to decision making.

Straight-up rules such as “no triangulations or enlistment of third party”, “resolve it or let it go”, “don’t accuse in absentia”, and “no hand from the grave or second guessing decisions” can eliminate much of the unresolved conflict that paralyzes teams and keeps them from moving to a higher level of performance.

4. Great Business Continually Raise The Performance Bar

No matter how much it achieves, great business teams are never satisfied, they implement self-monitoring, self-evaluation, continuous improvement, and raise the bar. The continuous improvement process helps a highly performing team to keep improving its performance and deliver impressive results.

5. Great Business Teams Have A Supportive Performance Management System

Having the right individuals in the right roles and establishing clear rules of engagement are not sufficient. The performance monitoring systems have to be inline with the expected behaviors.

  • Team and individual goals have to be crystal clear;
  • The necessary technical and interpersonal skills have to be provided;
  • Performance has to be monitored;
  • And feedback has to be timely an well thought out.

The book wasn’t written for an Agile audience but after reading it, it seems to me that applying the Agile principles would come close to cracking the code for standout performance.

Agile self-organized teams – is the team self-organized or not?

Image by Cyndie@smilebig!Where ever we read about self-organized teams, it often seems to be a binary thing – either the team is self-organized or it isn’t.

When people suggest that the team should become self-organized, the suggested process is presented as fairly easy and straight forward.

If you are amongst the people who believe these previous two statements, I am sorry to be the bearer of bad news. In exchange, I will offer you a free reality check. Team self-organization is neither binary nor straight forward – self-organization is an evolutionary process that takes time.

We have been helping customers implement self-organizations for years and we have been pushing the limits within our organization. Based on that experience, I am sharing 7 levels of self-organized teams.

  1. No opinion: Team members follow the direction of their manager. Not to be confused with Zombies or Living-Deads, these individuals are neither happy nor upset about being directed in their tasks – things are the way they are, period. These team members do not pay much attention to the organizational structure or who the actual leader is. They are strictly interested in “doing their job”. Although they may express an opinion with regards to the current structure, they don’t necessarily believe that self-organization is a better alternative. If you are moving towards self-organization, you shouldn’t spend much time convincing these people since they will gladly follow the official structure.
  2. Status quo: Team members have benefited from the current structure in the past and wish to preserve it. They are un-likely to want to change to any other team structure (including self-organization) until they clearly see the benefits of transitioning. To move towards self-organization, you will need to spend time demonstrating what the new structure will bring them specifically and gaining their trust so they are willing to experiment with what you are proposing.
  3. Selfish and irresponsible: Team members are happy to take advantage of being self-organized but only as long as it benefits them and that there are no increased responsibilities. Once a situation negatively impacts them (while benefiting the team), they aren’t willing to cooperate and when they are asked to take accountability for something, they shy away from the responsibility. In a nutshell, these individuals want the best of both worlds. To successfully transition to self-organization, it is critical to explain that they will need to make a decision and pick self-organization with responsibility or freedom outside the self-organized team.
  4. Interested and learning: Team members are very interested in being self-organized but aren’t familiar with the changes required for them to become autonomous. They are ready and willing to learn and fully embrace the proposed structure. These are key people in a transformation, they are the ones who will pull the others forward as long as you take the time to explain what they need to do.
  5. Self-organized: Team members are fully accountable and play by the rules of the team. They recognize their strengths and weaknesses and work on improving the organization of the team in order to become fully autonomous and self-supported. They deliver great results and need minimum involvement to remain in their current state. This is where you want your teams to be.
  6. Leading a self-organized team: Although the team is self-organized, leadership is always required. These individuals will willingly take responsibility to organize the existing teams (they are team members and not managers) or the new teams you are hoping to transition to the new model. In a transition, you will want to work with these individuals to spread the new model and increase the number of self-organized teams.
  7. Independent: Team members are too much self-organized. As a consequence, they no longer wish to be part of the organization and wish to go on their own. Although rare, in the event that self-organization transforms into full-autonomy, it may be necessary to break down the team and use some of the team members to help lead other self-organized teams.

The road to self-organization is long but very rewarding. Each organization needs to determine how far they are willing to push the model and how fast they wish to move.

You may also be interested in this post: I don’t believe in self-organized teams…

Real-life laboratory for human experiments – The case of an Agile organization

Our organization is well known in Canada, France, and other French speaking countries around the world as a leader with the Agile approaches. We are one of the few organizations in North America with over 20 full-time agile coaches (employees).  For most part, our governance model relies on self-organization, the absence of hierarchy, and transparency in our decisions. This is what is well known from customers who have worked with Pyxis and potential employees who wish to join the organization, but what is much-less known is how Pyxis is a real-life laboratory for management, organizational behaviours, and team dynamics.

Most of the people who come in contact with people at Pyxis or who have worked with us will agree that the organization is different and throughout this year, I will share some of the inner working of our organization.

Pyxis helps software development companies to become places where results, quality of life, and fun coexist sustainably by being first and foremost an example of what it proposes to its clients and by coaching them.

We help our customers transition to Agile because we know it works – not because it is written in books but because we have been living the Agile way for 10 years now.

As the first post on the inner working of our Agile organization, I will explain the root cause of this difference. More posts will follow on self-organization, agile management, governance models, and growing a profitable organization by leveraging people’s inner motivation (remember autonomy, mastery and purpose?).

The fundamental reasons why Pyxis is different

After observing the organization from the inside for over two years, I have had the opportunity to appreciate that we are fortunate (and one of very few organizations) to have a real-life laboratory for human experiments – no, not the kind usually reserved to white rats. Our structure allows us to experiments with governance models (the way people are managed) and observe first hand the organizational behaviors that arise and the impact on team dynamics. We pride ourselves as being an incubator for highly performing teams and as such, we often experiment new concepts within our organization before trying them out on our clients – which is not often the case in consulting, but I digress…

The first reason behind our uniqueness is the philosophy of the founder. François sees the world differently from most people and although he has an opinion on many topics, his real contribution is that Pyxis is not a profit-maximizing organization. Like every organization, Pyxis wishes to generate a yearly profit but that is not the reason why Pyxis was originally created. Pyxis was born with a purpose to improve how software development is made and more importantly to improve the quality of life of people within those organizations.

This is critical to understand the organization because it leaves rooms for experiments (making mistakes is a critical part of learning), for employee satisfaction (people truly enjoy working at Pyxis), and deliver great results (highly motivated employees deliver better results).

There are other reasons why the organization is different but in my opinion, this one is fundamental.

As an Agile Leader, I believe that …

Image by Robert GoodwinAs a leader, I believe it is important for people I work with to know my beliefs. As the leader of a self-organized company, I want to share those beliefs.

I personally believe that:

  • people are good in nature and wish to accomplish meaningful goals;
  • people truly wish to be successful and should be trusted to achieve success;
  • collective intelligence leads to better decisions;
  • individuals working together will find the solution to their problems, they know more about their skills, competences and environment than anyone else outside the team;
  • long lasting knowledge is best learn through hands-on experience;
  • as long as we learn something from the experience, failure is an investment, not an expense;
  • true success is achieved when people are in it for the long run;
  • a systemic perspective is useful to understand the entire system;
  • short term goals are rarely optimal and tend to maximize locally and not globally;
  • motivation comes from within, external factor do not really motivate people;
  • motivated people deliver better results and are highly contagious;
  • no single individual can (and should) be attributed success;
  • success attracts successful people;
  • you should judge people by their intention not their actions.

What are your beliefs?

We are surrounded by Zombies! We better do something…

I finally finished writing this post that I started just after Halloween – not because it is long or complex but simply because other things were more of a priority. Anyhow, back in October and in the spirit of Halloween, we had decided to rent a Halloween movie that was somewhat kid-friendly. Our selection ended up being Shaun of the Dead, a 2004 movie. Don’t worry, I haven’t turned into a movie critics and I won’t pretend this movie ranks anywhere in my top 3,000 favorite movies – that’s not the point here – but the movie made me realize how many (most?) employees are zombies.

“What the heck are you talking about?”, you ask.

I’ll spare you the gory details but there’s a scene at the end of the movie were the zombies end up being captured and turned into normal workers. The scene is great as it portrays the zombies perform mindless (and numbing) tasks while people around them don’t seem to notice them or even mind them at all.

[You may also be interested to read what Derek has been publishing on the topic of zombies in the workplace]

To simplify things and explain the analogy I came up with after watching this silly movie, I will start by explaining that in my opinion people (employees) fit into one of three categories.

The LIVINGS

Although at first, we may believe that everyone fits into this category you may be surprised to find out that it isn’t so. LIVING people are those who take full responsibility of their life while they don’t necessarily travel the path the most followed. LIVINGS do a lot of introspection to make sure they are living the life they truly want and they aren’t afraid to step outside their comfort zone.

In organizations, the LIVINGS aren’t afraid to look for a better way to do things and challenge the status quo. They aren’t happy just mechanically doing their job and they look for challenges that will make them grow professionally. You can find LIVINGS at every levels of an organization.

Although not measured scientifically, I believe there is only 20% to 30% of the working population that are real LIVINGS.

The ZOMBIES

At the other end of the spectrum are the ZOMBIES. Contrary to the LIVINGS, the ZOMBIES are dead workers. They perform routine tasks without getting intellectually and/or emotionally involved. No matter how old they biological body actually is, the ZOMBIES are counting the days ’til retirement – or if retirement is more than 5 years away, they are counting the days until their next vacation, until next week-end, and sometimes the hours until the end of the day.

In industrial times, ZOMBIES were seen punching in and punching out of their day job. With the advent of modern technology and the disappearance of the punch clocks, ZOMBIES can pass their time updating their Facebook page, sending useless emails and performing tasks on their computer to keep their body active since their soul has died.

Although not measured scientifically, I believe there is between 20% to 30% of the working population that are dead ZOMBIES.

The LIVING-DEADS

Somewhere between the LIVINGS and the ZOMBIES is the majority of the working population. The LIVING-DEAD are very difficult to distinguish from the LIVINGS as they seem to perform their tasks with some interest. The main difference between the LIVINGS and the LIVING-DEAD is that the latter were once part of the LIVING population but at some point in their career, their brain has been captured by ZOMBIES – just like in the Shaun of the Dead movie, once a living is bitten by a zombie, there is a gradual decline toward becoming a full-fledged zombie.

Although not measured scientifically, I believe the majority of the working population (between 40% and 60%) are LIVING-DEAD.

Can ZOMBIES and LIVING-DEAD transform back into LIVINGS?

Contrary to the movie, the LIVING-DEAD and the ZOMBIES can come back to becoming LIVING individuals but the road back is difficult. The sad news is that most large organizations are based on rules, on controls and on structures that help breed ZOMBIES by converting LIVINGS into LIVING-DEAD. The good news is that there are ways out – I know, I used to be a ZOMBIE myself…

What category do you fit into?

Follow

Get every new post delivered to your Inbox.