FTE or Consultant?? Let me Coach!

Oh, the dilemma!

Agile Coach contemplating a new opportunity: "Should I go in as a consultant or an FTE (full-time employee)?

The decision around consulting versus being a full-time employee when it comes to coaching companies in Agile encompasses more than benefits, vacation, salary, etc.  It encompasses what you plan to accomplish, and how successful you want to be at reaching the goals.

In general, there are two coaching paths.

1. Coaching teams already using Agile techniques
2. Coaching a department or entire organization through the transformation to using Agile techniques

If you're about to coach teams already using Agile, choose whatever suits you; FTE or Consultant will work.

However, if you're getting an organization up to speed on adopting, and eventually transforming to Agile, then there are a few things to consider.

Why Consulting Works for an Agile Transformation Coach (or any position that requires an organizational change)

No More Politics Please                                                

As someone who has to influence everyone from the teams to upper management, it is important not to have to report to one department.  We all know how politics play out in a matrix organization.  Some departments don't like other departments, one manager wants something different than the other.  At some companies I have consulted with, I saw full-time employees trying to undermine other employees so  that they can get promoted.

Being a consultant means you don't have to play the company politics.  You're able to stand back and watch, so bring some popcorn and a large cherry coke.

Objectivity                                                                        

If you're an FTE assigned under one manager, that person determines your salary and bonuses.  That tells me that you're going to be biased toward what that person wants.

It is important to set expectations up front, especially to the person who is paying you from their department budget.  It is vital to your livelihood as a Coach to reiterate that you are working for everyone involved in the transformation and that you are an objective party no matter what. If you feel that the company is not for that, don't take the job.

Being a consultant means you answer to the entire organization.

Freedom and Focus                                                             

By freedom, I mean freedom to do your job.  As a consultant, you're brought in for one purpose and you should be given the freedom to accomplish that purpose.  As an Agile Transformation Coach, you want to focus on the transformation, not other tasks that are outside that realm.
As an FTE, there are times when you will be asked to take on something else.  Although, this benefits the organization in the short term, the long term effects of not being able to focus on the transformation will hurt the company as your time is taken away


Being a consultant means you get to focus on the goals that were set forth when you were hired.

Trust                                                                                        

One vital component to bringing about change (and Agile Adoptions & Transformations are all about change) is that people have to trust you.  This means that every point I mentioned above has to be true.  The organization has to believe that you aren't playing company politics, that you are objective, and that you are focused on the transformation of mindsets and practices.
Your goal and purpose is to make this company succeed through the practices you teach and live by.  Your goal is not to sell a tool, not to progress in the company, not to make yourself look good. You are to transform an organization so that they are delivering high quality, valuable products that are within a reasonable range of the schedule, scope, and budget constraints.

Being a consultant means that people can trust you to get the job done and see the change through so that it sticks.

________________________________________________________________________________

After the transformation, taking an FTE position or staying a Consultant is up to you.  If you think you've achieved all of the above, and that being an FTE won't change anything because you've set your ground, go ahead.  There are times when being an FTE will work.  My take is, in the beginning especially, it is important to stay away from politics, be objective, have the freedom to focus, and be trusted.  This happens best as a Consultant.

What do you think?  Do you think that when transforming an organization, being an FTE is better?  If so, let me know. I'd love to hear your feedback and experiences. 



 

Team Fever? Grab the Thermometer!

With symptoms ranging from runny noses, to dry coughs, to fevers that put you in terrible sweats, getting sick is never fun. Being sick is even more disruptive to a team when someone has to miss work and others have to pick up slack, work later, or come up with other innovative ideas on how to continue at the same pace.

The same applies when team members are "sick" at work and have negative symptoms in their work environment; their productivity and quality are negatively impacted.  So how do I gauge how a team feels? I take their temperature.  A temperature gauge is my favorite way to start conversations and anonymously see how team members feel.  I do this before starting a retrospective, but this can be used in other meetings, at a wider level, or even at home for family meetings.

STEP 1

Create a thermometer with a scale, and feel free to make it fun.  With a recent team, someone saw my thermometer and thought I had the junior high girl I mentor work on it. In reality, I was the horrible artist, but the team loved it. We knew what it was for and it served it's purpose.

STEP 2

Create a measurable scale for the thermometer.  I like to use 1-10, though I have also used 1-5 to make it less convoluted.  You can also use words like "Perfect", "Not the Best", "Lousy", "Can I go Home and Never Come Back."  The point is to have some way of measuring how people are feeling.

STEP 3

Identify and document what the scale means and what is being measured so that there is no confusion. What does 1 really mean versus a 5? Am I allowed to use 5.5 or other fractions?
What are we measuring (the last iteration, the release, external factors, etc)?

STEP 4

Have each team member vote anonymously.  I like to hand out post it notes on which individuals write their temperature and hand it in.

STEP 5

Average the responses to get the temperature.

STEP 6

Follow up immediately on why the team thinks the temperature is the way it is.  What factors brought us to a 6?  How do we get to a lower temperature so we don't have a fever?

Document and decide as a team how to resolve any issues that were brought up.

STEP 7

Keep a rolling graph in the team area on the temperatures throughout the project.  You will mostly notice that as velocity lowered or things weren't getting done that the team temperature was worse.  

Let me know in the comments if you have been doing something like this or will be trying it, and what your result is.

TIPS:

• If a team  has low temperatures all the time, it could be a good thing or it can be that your team doesn't feel like they can be open. Evaluate the cause.

• Do not call people out if you think they put a bad temperature in.  Keep the conversations objective and allow for openness among the team members.

• If issues come up that will continue to impact the project, put those items in the backlog so they can be mitigated or resolved.