Archive for category Management

Creating a Vision – An Analogy

visionAnalogyI’m a big fan of vision and mission statements. Many people think they’re fluff but I truly believe they are valuable tools. I think vision and mission statements are misunderstood, and are really much more difficult to write than one might think. For example should a vision change yearly? When you communicate your vision are you really communicating a road map of activities?

Here are two analogies I thought of that calls out the difference between a roadmap and a vision.

imageScenario 1) As the leader of my family, i gather my children around and tell them. “Kids, we’ve got a good chunk of money put aside and we’re going to use it. Tomorrow we’re going to get up at the crack of dawn and get in the car. We’re going to spend 12 hours driving and then we’ll stop for the night. We’ve got 500 dollars allocated for this already. The next day we’ll get back in the car and drive another 12 hours. Here we’ll commit 3000 dollars over the next 5 days. after which we’ll get back in the car drive 12 hours stop for the night and drive another 12 hours the following day. Isn’t it great that Mommy and Daddy are spending this much money on you?”


How was that as a vision? Would my kids look forward to the literal and figurative Long road ahead?


Scenario 2) Untitled-2

I gather my kids around and say. “Kids we’re taking a road trip to Disney World”

Of these two options which would inspire and drive my kids. Which would help them understand what the overall goal is.

The point here is that, to me, a vision is a long term objective that inspires people and conveys the destination. Something that even if there is a detour in the road, serves as a guide post helping you get back on path to the right direction. It helps you get through the long boring drives, or stressful days at work. It brings people together in a collective goal and guides teams toward a shared future.

A vision is more than a road map or a play by play of what is coming up next. A vision is communication of where we are trying to go, not how we’re are getting there.

2 Comments

Reward the effort not just the outcome

I came across this again recently and was reminded how important the concept is. It’s easy to call out achievements and successes we see, and of course the bigger the success the more likely we praise. However, we need to also focus on praising the effort in addition to the outcome.

Kaizen is a successful philosophy of Continuous Improvement touted by many business leaders and publications. By recognizing the effort an not just the outcome, individuals are more motivated to improve all aspects of the organization, from rolling out multimillion dollar cash cows, to posting a sign reminding people to not put metal in the microwave.

Often good intentions go unnoticed simply because the outcome isn’t clear. For example when a developer refactors a method, the outcome is typically just that it’s easier for other developers to work with. There is no functional change and therefore its difficult to call out. However these small efforts that continually improve our business are just as important, if not more, and should be recognized just the same.

Praise is infinitely divisible, hand it out and you’ll always have more. You can say Good Job all day and never run out.

So take time this week to recognize the efforts within your teams not just the outcomes.

Leave a Comment

Coffee Notes: How to Build an Agile Dev Team – The GE Way

“Building software in a waterfall approach, where there is a big milestone release at the end of the process, isn’t conducive to success in the modern world, according to top executives from the NYSE and GE.” –Kerner

This article by Sean Michael Kerner reviews interviews with Robert Kerner, vice-president at New York Stock Exchange (NYSE), and Matt Merchant, CTO, GE Corporate on software development practices in their companies.

An interesting and view on what happens when leaders “get it”.

How to Build an Agile Dev Team – The GE Way

, , , , ,

Leave a Comment

Coffee Notes: Negotiating Scrum Through Watefall

Coffee Notes: Negotiating Scrum Through Watefall - Blog entry by Christopher Grant -Here’s an interesting article about how to really deal with many of the challenges faced when dealing with Waterfall cultures and new Agile concepts. In his article Phil Southward lists out many of the key SDLC phases as well as how Agile teams can work through them in a wartefall organization.
It’s an interesting and enlightening read.
qaheaven (@qaheaven)
10/21/10 2:38 AM
Negotiating #Scrum Through a Waterfallhttp://bit.ly/aE86Zt

 

http://www.scrumalliance.org/articles/189-negotiating-scrum-through-a-waterfall

, , , , ,

Leave a Comment

Coffee Notes: Offshore 280% more defects

offShore.jpgThe other day I came across this stat and it was so interesting I wanted to followup on it before I forwarded it on.  According to Michael Mah at the Cutter Consortium offshore IT creates 280% more defects than industry average. Ian Savage reports on Twitter about Mah’s research noting that the industry average of 242 defects is blown away by offshore defects averaging 677. This results in 280% more defects when development originates offshore.

Michael Mah is a Managing Partner of QSM Associates, Inc., a firm specializing in software measurement, project estimation, and “in-flight” control for both inhouse and outsourced/offshore development. QSM has developed and maintains one of the largest databases of more than 7,500 completed projects collected worldwide, with productivity statistics and trends on cost, schedule, and quality from more than 500 organizations and 18 countries.

Additional References:

 

, , , ,

Leave a Comment

Follow

Get every new post delivered to your Inbox.

Join 477 other followers