Archive for the ‘Attitude’ Category

A real "class act"

Wednesday, March 2nd, 2011

I learn so much from failure it’s hard to ignore the good that comes from it.

This week I parted company with a client long before their goals were reached.

Sadly, I knew from the start they would be a challenge and made the mistake of ignoring the warning signs.  Never again.  Honest!

This entry is as much for coaches and consultants as it is for teams, staff, management and leadership.

There are several tell-tale indicators of success and/or failure.  In our own ways and in their own contexts, experienced coaches and consultants know what these indicators are.  Well-rounded, experienced, and seasoned practitioners within companies know them too.  In fact, most people know them instinctively, somehow.  I can therefore safely say that whether it’s through experience or instinct, we all know many of the same indicators.  In fact, we can probably sum-up every indicator in one word: Attitude.

So, yes, Jeff Keller’s famous self-help book, "Attitude is Everything", applies as well.  In organizations, "attitude" is frequently interchangeable or encompassed by company "culture".  And yes, attitude is a derivative of culture.  But sometimes culture is harder to pinpoint than attitudes.  Attitude shows up in your interactions with the company from the very start of your prospecting dance.

Here are some attitudes you may encounter and whether or not they spell greater odds of success or failure:

Failure-prone attitudes:

  • Hassling about price/cost/time but expecting the same scope and performance outcomes.
  • Focusing on deadlines and schedules instead of real results.
  • Not owning the work and expecting off-site outsiders to invent working approaches.
  • Shallow goals that aren’t S.M.A.R.T.
  • Mistaking a task for an outcome or goal.
  • Ignoring, denying, and filtering information that indicates problems.
  • Poor communication (which often starts with poor listening skills).
  • No allocation of explicit time and/or resources to make improvements.
  • Failing to recognize the importance of the right people in the right roles for the right reasons.
  • Delivering materials for review with no lead-time for turn-around.
  • Persisting in propagating bureaucratic policies despite the obvious lack of value-add.
  • Executives who are mostly (if not exclusively) involved in decisions involving budgets but not in making changes.
  • Repeatedly using external influences as excuses to not make important changes.
  • Assuming a victimization attitude instead of owning up to their circumstances.
  • Failure to learn and apply new ideas — even after being presented with the benefits of those ideas.
  • Management by motivation 1.0 or 2.0

Success-leading attitudes:

  • Focus on results not the cost of getting them.
  • Clear, S.M.A.R.T. goals.
  • Executive involvement and ownership of leading the changes.
  • Respect and appreciation for everyone’s contribution and effort.
  • Active concern for overtime, unplanned work, and defects.
  • Accounting and planning for everything that takes time by everyone involved.
  • Taking full ownership for all the work (irrespective of the “divisions of labor” as seen by the customers).
  • Clear-eyed view of effort and not planning around "best case only" scenarios.
  • Ability to appreciate the need for non-technical, non-managerial skills in the roles of leading change.
  • Seeing beyond the surface: A desire to learn and understand the meaning behind the work, not just following the specific language of the work.
  • Dealing with people as people and not numbers.

My best clients have always had direct, clear and unambiguous evidence of two things:

  1. S.M.A.R.T. Goals, and
  2. Executive involvement in making the changes happen — not just lip service and budget authorization.  This usually took the form of the top leader (or 1-step away) taking personal involvement in not just setting direction, but in working through the best way to make things happen with the people who will be most affected.  (What does NOT count is a “top” leader with a purely administrative role and no executive accountability or responsibility.)

In experiencing the failure with this client, I admit to learning about at least one critical oversight on my part (there were others but this one takes top spot).  As we were interviewing each other, I failed to interrogate the leaders of the company for specific improvement goals.  The only "goals" they came to me with was to make their processes "leaner" and to attain a CMMI Maturity Level 3 rating with leaner processes.  Which turned out to really mean little more than to replace their heavy-handed compliance-oriented approach with a set of processes more projects could comply with more easily.  Again, note that they were still about "compliance".

Despite claims to the contrary, I didn’t fully realize until well into the engagement that compliance was still their primary attitude — at least among the people who were charged with overseeing the process assets for the entire organization. 

During the engagement, I repeatedly worked to identify meaningful improvement goals that being "lean" could help them attain.  I then created a strategy that would bring them closer to these goals and presented it to the majority of the executives.

Despite wide agreement on the goals and the strategy, when it came to rolling out the necessary changes, it was met the same-old resistance to change and fears that I knew spelled doom.

Nonetheless, I had high hopes for this organization so I decided I would bring them around by modeling the behavior I was trying to help them see.  A few people caught on but, alas, not the people who held sway in the organization.  Our mutual falling-out began early when it became apparent that desire among the leadership to achieve a maturity rating without upsetting the apple cart was overshadowing the desire to actually reach the performance goals being a leaner organization would achieve.

Notwithstanding, there were other tell-tale signs from the list above that this organization didn’t have the attitude to make the changes necessary.  I won’t belabor you with the complete saga.  Instead, I’ll return to my point about this entry.
You as coaches, consultants, and staff can’t want to better than your leadership is prepared to be.  The signs are all around you.  Pay attention to the signs early.  You will save yourself a lot of time, heartache and frustration.  If you believe you don’t have enough experience to justify your powers of observation, then trust your instincts.  Is the organization defensive about their entrenched position on their circumstance?  Do they make excuses instead of setting goals?  Are the goals devoid of any real results? 

You don’t even have to go that far.  How are you treated as a person, as a professional, is about all you really need to know about whether or not there’s a hope that things can get better.  If you’re not appreciated, if your organization is willfully blind to the things that cause you grief, if you see signs that tell you the organization lacks "class", you don’t need 20 years of experience telling you you’re right to know you’re right.  This organization is doomed to mediocrity.  Is that the kind of organization you want to be associated with?

I don’t, and, I won’t ever be again.

Doing Agile CMMI without “Doing” Agile or CMMI

Monday, November 8th, 2010

There’s an under-appreciated reality of what either agile or CMMI can accomplish for an organization.  In particular, it’s not as much about what either accomplishes for an organization as much as it is about what an organization does for itself that achieves agility and systemic improvement.

It seems to be a decades-old issue that many technology-oriented companies, and, it seems, especially software companies, struggle with organizing and managing operations towards excellence.  I can’t even begin to dig into any reasons why this is so, but there may be some truth to the stereotype about technology people not being good with business and/or people. ;-)

I’ve found something fascinating that is fairly consistent across many companies I’ve visited or discussed with colleagues.  What’s fascinating about it is not only the consistency across multiple fields, industries, verticals, and national boundaries, but that it reinforces a position I’ve taken since beginning my career.  That position is the afore-mentioned “under-appreciated reality”:

Aligning the organization with specific business goals and providing a supportive culture
leads to broad behaviors at all levels that result in high performance.

OK.  So, that may not seem earth-shattering.  But there’s a lot in this statement about agile and CMMI that too many organizations to “get”.  And, this is where all the anecdotal evidence from the many companies comes into play:

Organizations with a culture of excellence generate behaviors (including setting and pursuing specific business goals) that achieve agility and systemic improvement without specifically setting out to achieve either “agile” or “CMMI”.

Throughout my earlier career, I was routinely frustrated by “training” that provided me with specific tools and techniques for dealing with “many common” situations – pretty much all of which were cultural, interpersonal, and otherwise based on human behavior.  The cases, examples, and solutions all felt very canned and contrived.  Why?  Because, in effect, they were.  They were very specific to the context and would only solve issues in that context.  What the examples lacked – and by extension, the entire course – was fundamental tools with which to deal with situations that were not neatly boxed into the provided context.  In other words, these training courses provided practices. These practices work in explicit situations, but they fail to provide the basis upon which those practices were built.  Without such a basis, I and other consumers of this “training” could not address real situations that didn’t match the training’s canned scenarios.

“Doing” agile or CMMI by “doing” their respective practices results in exactly the same limited benefits.

Making agile or CMMI “about agile” or “about CMMI” accomplishes little value and lots of frustration.  These are only practices.  Practices are devoid of context.  A culture of excellence and an explicit business case to pursue improvements provide the necessary context.

We see this all the time.  For example, for decades in the West mathematics was taught in a way left many students wondering, “what will I do with this?”  (This may still be true in many places.)  It was/is taught without any context to how it can help them better analyze and understand their world.  As a result, Western students have historically been less interested in math, do less well in math tests, and are less inclined to study in fields heavily dependent on math.  All due to being taught math for math’s sake and not as a means to a beneficial end.

Medicine is also taught this way around the world.  Leading too many doctors to seeing patients as packages “symptoms” and “illnesses” rather than as people who need help.  Scientific exploration often gets caught up in the same quandary.  Exploration is the goal, if you’re looking for a specific answer, it’s research.  When you’re trying to create a specific solution it’s development.  Mixing-up “exploration” with R&D will frequently result in missing interesting findings in pursuit of narrow objectives.

In agile practices, what’s more important: doing Scrum or delivering value?  Pair programming, or reducing defects?  Maximizing code coverage in unit tests or testing the right parts of the product?  “Doing” Scrum, pairing, and automating unit tests are intended to deliver more product of high value, sooner.  Focusing on the practices and not what’s best for the customer are missing the point of these practices.  Same with CMMI.

What are the economics of your core operation?  Not just what your group costs to operate on a monthly basis, but what unit of value is produced for any given unit of time?  How do you know?  Why do you believe your data is reliable?  The ability to make decisions relies on data and when the data is unreliable, decisions, plans and anything else that relies on the data is questionable and risky.

It turns out (not surprisingly) that when a group focuses on what’s important AND has the economic data to reliably understand the behavior of their operation, it aligns their actions with the very same goals set-forth in both agile and CMMI.

Focusing on the right things in your operation will cause behaviors that achieve agility and “rate well” against CMMI.  Whether or not you’re even trying to “do” agile or CMMI.

Field notes from SEPG-NA 2009 – Thursday

Thursday, March 26th, 2009

image San Jase, CA.  Actually there won’t, unfortunately, be much to report today as I was side-tracked from all but one session.  The session I attended was an experience report from a lead appraiser working with a company whose total size was all of 12 individuals.  In fact, they were a distributed workforce with no central offices.  Everyone worked from home.  This was a report on how they achieved CMMI ML3.  The company itself had very impressive results made possible by very impressive people and attitudes.  Let’s get one (or two) things straight immediately: (1) they really truly were ML3, no corners cut, they really truly did the work of defining, managing and using their processes, (2) they did NOT need CMMI to be disciplined — to a person they were highly skilled, highly technical, supremely professional, absolutely committed their work and company, incredibly laid-back, and deadly serious about NOT causing themselves work that was not fun and benefit the work and company.

The moral of this story is that the primary driver of improvement (of any flavor) is first and foremost attitude and culture.

Moving on.  I stopped by David Anderson’s last talk of the conference on Metrics and Agile, and once again, it was close-the-doors-room-is-full SRO.  While other sessions were letting out early and people were streaming out right at the stop time (time for lunch!), David’s session was full until kicked out.  Once again, put CMMI, Agile, and Maturity in the same space and sparks fly.  Dave impressed several very important people.

That’s all I have to report today about the conference.  Stay tuned for SEPG-NA 2010.  I’m contributing to the program committee and know there are some really great things in store.  Planning for it started today and I’ve got action items due.  :-)