Is Agile another word for Anarchy?

I’ve had a Dilbert strip pinned to my wall for a few years that always brings a smile to my face.  In it, the pointy-haired boss is talking to his “team” and says agile programming is, “… no more planning and no more documentation – just start writing code and complaining.”  It’s funny because it’s true.

Don’t get me wrong, agile development is fantastic.  For most organizations and for most projects, moving away from formal waterfall project methodology is a welcome relief.  Companies no longer have the appetite nor patience for multi-year projects and project team members want to work on smaller deliverables to have a sense of accomplishment and to expand their experience with multiple technologies.  However, agile has a dirty secret that is overlooked or ignored: it requires commitment and development best practices for success.

In a recent InfoWorld article titled, “What’s wrong with agile development“, culture and people topped the list of reasons for why agile initiatives fail.  I agree with the results, however I would suggest that there is a broader misunderstanding of exactly what agile is that needs to be accounted for.

It has been my experience that agile methodologies produce smaller, but faster components and that teams who use agile methods are more nimble than those that do not.  Being more nimble means they can more quickly shift focus to keep aligned with ever-changing business priorities.

Agile development does not mean little to no requirements and little to no testing.  Somewhere along the line those who haven’t experienced agile for themselves have bought into they myth that agile essentially means a hallway conversation today results in a deliverable tomorrow.  That is simply not the case.  In addition to culture and people, agile requires well documented requirements, typically in the form of user stories, and good testing practices before production release.

I love PHB’s recommendation to “just start writing code” but without some rigor around the development process the result will look increasingly less like agile development and more like anarchy development.

What have been your experiences?  Where have you tried agile and seen it succeed and where has it failed?

What is your V.A.L.U.E.?

“I’m good enough, I’m smart enough, and doggone it, people like me!” – Stuart Smalley

We all like to think we’re important, that we’re valued members of our company and that we are critical to its success, but the reality is there are probably few people who are completely irreplaceable.  For some, their departure causes huge holes that may never be filled and in rare cases heralds the downfall of their company, but for most, the organization adapts – new people hired, someone is promoted to fill the gap or the responsibility gets shifted to multiple people.

Everyone wants to be needed at their jobs – to be an essential member of their team, or even the entire organization.  Our sense of corporate worth comes from a several inputs such as title, salary, number of direct reports, office size, and education, to name a few, however, perception is often not reality, especially when it comes to self perception.  We are always measuring ourselves and comparing our value to others, but it’s not our valuation that matters: if you were stack-ranked in your company, would you be near the top?  Are you sure?

Could some type of workplace value index save us?  Not necessarily.  Kred & Klout scores try to measure a person’s social influence in social media, however are they really accurate measurements?  Probably not – they are only as good as the accuracy of what they are measuring.  For example, I could create a scoring system that predicted how influential a person is at the grocery store based on their combined height & weight but do I know these metrics have anything to do with influence?  No, because I would be trying to measure something not measurable: emotion.  So why are Kred & Klout successful, despite being flawed?  They give a somewhat reasonable & measurable score which can be compared against others to see how each person stacks up.  For those that care, it is simply another number added to our increasing portfolio of digital worth indicators: number of twitter followers, facebook friends, linkedin connections, and now Kred & Klout scores.

Instead of trying to measure value at the workplace, what can you do to make sure you are maximizing your contribution to the larger organization?  Not by focusing on a number, but constantly trying to improve each day. using the following attributes as a guide.

Vision: Heads down is a nice phrase that conveys hard work, however it’s critically important to look up and course correct.  Set goals for yourself and for your industry and be constantly improving.

Attitude: Studies have shown that more agreeable workers are more productive and have higher success in the workplace compared to their peers.  In an earlier post, I shared that as a hiring manager, I would rather hire a person less experienced but had a better attitude than a jerk with talent.  Skills can be learned, however, I can only model attitude and hope it sticks to those working for me.

Leadership: I strongly believe people should work as if they have a role greater then they have.  I encourage my team to do so, not only does it elevate the team, it is incredibly valuable for them individually.  When opportunity comes, it is very easy for that person to assume the new role because they have already been doing it!

Understanding: Perhaps the most important, it is essential that there is an understanding of the environment around you.  Know the main challenges facing your company, do the same for the various departments and work down until reaching your level in the company.  It is much more difficult to be a leader or have a realistic vision without having a good understanding of the larger environment.

Engagement: Networking, relationships, engagement – they essentially all mean the same thing.  The greater the quantity and quality, the more information and influence you have.  In an article on Aspiring CIOs, the author says one of the 6 critical qualities is relationship-building prowess and it is so important in fact, that it was valued above project management!  This holds true for any position – simply replace “CIO” and “project management” with a title and key skill needed for that position.

I plan on exploring the five attributes of VALUE in upcoming posts and providing examples of where these items have proven successful.

What do you think, is Stuart Smalley on to something?  Doggone it, I wish it were that easy.

CIO: Chief Irrelevant Officer?

There is an increasing number of articles heralding the doom of CIOs and the IT departments that they lead.  Almost on a daily basis titles such as, “Are CMOs Making The CIO Irrelevant” and “More Proof That Shadow IT is a Growing Issue” fill my blog roll and the larger Twitterverse.  These articles talk about the growing ability of organizations outside of IT to go their own way, to roll out a system, program or feature that meets their needs.

I can’t say that I blame them.  With The Cloud delivering on the promise of cheaper, faster, connected, ubiquitous, scalable, secure, and accessible one simply needs a browser and a credit card to fire up a solution…  demos optional.  And it doesn’t stop there, companies such as Salesforce.com and Workday have incredibly rich platforms that makes it easy for any employee to whip up a robust application often without writing a single line of code.

Business leaders have always been operating in a “do-more-faster” mode as companies try to keep pace with their competition or maintain their competitive advantages.  With new cloud solutions arriving at an increasing rate and offering more and more features, IT no longer controls the infrastructure and can be avoided entirely.

So, are CIOs and IT as a whole, doomed?  No, but we need to think differently.  I see four ways CIOs and IT leaders can not only prevent becoming irrelevant, but also unlock their value within their company:

  1. Become a Trusted Adviser.  Dictionary.com defines trust as “a person on whom or thing on which one relies” – note it indicates a willing participation by the person doing the trusting.  It doesn’t say anything about control, dependency, or force.  I don’t believe business leaders want to manage all that comes with any solution, instead they want an organization that can give guidance, expertise and the ability to deliver relevant & timely solutions.  To become a trusted adviser you need to:
  2. Understand.  IT needs to understand the business processes and pain points of the organizations they support.  This seems self-evident, but it’s easier said than put into practice, mostly due to the complexity and the ever-changing nature of business.  What is known today will be outdated tomorrow.  Understanding, like staying in shape, needs to be done intentionally on a daily basis.  And understanding begins with:
  3. Be Social.  Trust and understanding are a result of establishing and fostering relationships.  Being social is critical to relationship building and with video conferencing, enterprise instant messaging, social media, and those old-fashioned things called legs, it is easier than ever to nurture a social network… again it’s a matter of effort.  And being social is much easier if you:
  4. Speak the Language.  Frame every decision, approach or solution in terms of the desired business goals being achieved.  Be honest about the costs of the proposal and review it from the point of view of those funding it.  Constantly attack the problem from multiple angles and consider non-traditional solutions.  The outcome should be a proposal that would make a trial lawyer smile – something that is so self-evident the final decision makers will be convinced half way through the argument.

Is it possible to fire up a cloud solution and meet some type of business need?  Absolutely.  But consider how that solution fits into the larger ecosystem and this is where IT can really help.  Will you need to integrate the system with others?  Does the system need data from other systems and if so where is that data coming from?  What type of reporting will you want to do?  How will users access the new system?  Are there security concerns?  Is there an opportunity to deliver the same features from an existing system – freeing up resources for other projects?  Are there compliance considerations?

The heralds are correct: change is definitely coming and anyone who keeps an eye on industry trends can see that.  Cloud and pace of innovation doesn’t need to be a wedge separating IT from the rest of the business.  Instead IT leaders need to do what they should have done all along to stay relevant – support they businesses they have the privilege of working for.

Can a “Just In Time” Approach to Architecture Work?

This is how fast I drive to work in the morning

Companies are increasingly moving to cloud-based software and service infrastructures and that trend is only expected to accelerate.  Gartner is forecasting that more than 50% of the world’s 1,000 biggest companies will store customer-sensitive data in the public cloud by the end of 2016.

The faster pace puts pressure on IT organizations to adapt to a constantly changing set of requirements and systems, which in turn makes strategic planning difficult.  When change comes quickly, the natural tendency is to slow down and plan more; to take a breath and create a formal design for the future.  One that is flexible enough to adapt to changing requirements, but is also built to last.

If pressure and coal makes a diamond, what does pressure and people make? Hotdogs?

Even if it was possible to design such a solution, this approach is directly at odds with progressive IT organizations who function in an agile, business-first fashion and who desire to be a business enabler and trusted adviser.

With pressure coming from many directions, something needs to give.  IT organizations can either resist and further distance themselves from the rest of the business they serve or they can change their practices and embrace the pace of change.

A Just in Time Architecture can be adopted by IT organizations to have enough control to ensure system stability and flexibility while allowing for an increased pace of business.  Just in Time Architecture is an approach that is flexible in nature,  allows for the best technical decisions using the information that’s available at the time, all while aligning efforts toward a long term, strategic vision.

It is best achieved when using the following 7 principles:

  1. Constantly evaluate the major players, solutions and direction of a market
  2. Stay current with the newest technologies and trends
  3. Fanatically search for an easier way, favoring a buy over build approach
  4. Keep the solution as simple as possible
  5. Strike the balance between built-to-last and built-for-speed and need
  6. Make the most informed decision possible just in time to meet the needs of the business
  7. Implement and course-correct as needed

This approach can be difficult for people to adjust to – especially someone used to more traditional methodologies (ie, waterfall) or responsible for enterprise systems in large organizations.  For those organizations holding onto these traditional practices, the pressure is mounting.  They will need to adapt or risk being outsourced themselves as businesses choose to go around them instead of working with them.

How about you? How have you been able to adopt a “Just in Time” approach to architecture?  Do you think this approach would work or only introduce more problems?

The importance of good communication

Ninja

This guy has a black belt in communication... and public humiliation

I know I’m not the first person to write about this topic – in fact I wouldn’t be surprised if there were hundreds of blogs, tweets and articles written just this past week alone on communication – but the importance of good communication cannot be overstated.  The sheer number of words written on the subject is an indication that it’s a difficult skill to master.

I believe consistent, good communication is so hard to attain because it takes time and effort and for most of us with our busy lives those are two luxuries we can’t afford.  Unfortunately by not taking the time to communicate in an effective manner, an information vacuum is formed.  Similar to a black hole, an information vacuum has immense gravity and draws to it every perception and opinion near and far.  The worst part of this phenomenon is the time and effort needed to set things right is far greater than to simply communicate well in the first place.

So, how can you make your average, run of the mill communication good communication?  And what can you do to decrease the amount of time and effort needed to be a communication master?

Clarity
At the heart of good communication is clarity – having a clear (and concise) message is critical to good communication.  It could be argued that bad communication is worse than no communication at all.  So, stay on point and keep it simple.  Don’t give more detail than absolutely needed – it’s best to start at the most basic point and expand from there.  Keep it simple stupid, certainly applies here.  Also, anticipate questions you expect to be asked by those receiving the communication and use them to further shape your message.

A stain glass window representation of Polonius.

Be brief or risk death by sword - this guy is serious

Brevity
Shakespeare famously wrote in Hamlet, “Brevity is the soul of wit”.  Wit alone doesn’t benefit from succinctness.  In fact, one could argue that it’s more critical than ever to be brief given today’s 140 character, micro-blogging culture.  Brief is consumable and readable.  More so for those whose schedules are already full and may only have minutes to hear/read and digest your update.

H. G. Wells' War of the Worlds (2005 film)

Please let me know if you see this happening outside your window

Timeliness
Communication is most valuable when it’s done in a timely fashion.  What good is it to learn about an alien invasion weeks after it happened?  Most likely that’s something you would appreciate knowing as soon as possible so you can finish building your apocalypse bunker – fully stocked with Spam and Twinkies.  Your job is to give people the information they need when they need it.

So now that we have established a few guidelines for improving communication, how can it be something that’s not a chore?

Use Templates
Come up with a few good templates and use them religiously.  I have one for email-based status reports; one for presentations with a key point on each slide; one for swimlane diagrams; one for datasheets; one for project requirements, etc.  And I use them when possible and either adjust them as needed to incorporate a new feature or clone them and modify.

Fancy Isn’t Always Better
Less is more.  Fancy has its place, but don’t embellish unless your audience requires it.  Content is king here.  I’ve found Google Docs with fewer features than Microsoft Office actually helps me from being my own worst enemy here by limiting what I can and can’t do.

Set Reminders
I’ve worked for the same manager for years and I still need a reminder to send him my team’s status report every Friday.  In addition, I keep a punch list in Google Docs for items that I need to complete that week and I use reminders in Gmail calendar to remind myself for recurring and point in time events.

There you have it – my thoughts on what make good communication.  Being a good communicator is hard work.  Having techniques that work for you is essential, but communication, like most things, does get easier as you work on it.

I find I still have a long way to go… but I’m trying and hope to master it some day.

What did I miss?  What other techniques have you found to become a better communicator?

The importance of just doing something

A blank whiteboard

"Come on... write on me... I dare ya"

At the beginning of a creative task I often find myself staring at an empty screen (or paper – yes, this stuff still exists) or off into space as I rack my brain in an attempt to fill the vast emptiness in front of me.  One of the most daunting parts of any creative project is the sheer challenge of just getting started.  The void stares back at you, taunting you with its blankness.  At times you can almost hear it whisper, “you’re a fraud”, “you don’t know what you’re doing” – it is terribly overwhelming and a real confidence killer.

A photo of a napkin holder I took.

Got a napkin? Great, I have an idea

During these times when I am struggling with getting started, I’ve learned to apply  a simple method to help me move forward: write down everything I can and step away.  I have to force myself to do both of these steps because “everything” may only include fragmented thoughts, a few flowchart blocks or stubs for a wireframe and walking away from something so incomplete is hard to do.  After some time has passed (hours, days) I will come back and work on what I’ve started.  I’m always amazed at how well this simple approach works.  I’ve also found that this process works for teams as well.

Recently I was in a meeting to review a design proposal for a new intranet team site.  As the discussion picked up the ideas started flying and by the end of the hour the final design was very different from the prototype.  I felt bad for the designers and was concerned that they would leave the meeting feeling discouraged or demoralized but the goal of the meeting wasn’t to confirm the design, it was to hear all opinions, brainstorm and “get it right”.

Later, a thought occurred to me – did the proposal team fail in their attempt to design a replacement site?

Isaac Newton Dansk: Sir Isaac Newton Français ...

Sir Isaac Newton: "If I have seen further it is by standing on the shoulders of Giants"

I think most of us left the meeting feeling that it was our efforts that created something useful.  And while it’s true that final solution was much better with input from the group, the real stars of the process were the designers.  Their work was what got the creative juices flowing.  By putting something in front of the team they provided everyone a straw man to wrestle with.  Without them we would have stared at a blank whiteboard and the result would have suffered.

Nike got it right: Just Do It.  Don’t try to be perfect out of the gate.  Try it, fix it, try it – iterate until it’s good and then iterate until it’s better.

When faced with a creative project, what do you do to help move things along?

What methods do you use with a group to foster brainstorming?

What I learned from The Hunger Games

Cover of "The Hunger Games"

Good stuff!

My daughter has gotten me hooked on The Hunger Games.  Along with practically every other tween and teen (and a lot of parents) in the US, I’ve read the first book in the series and saw the movie on opening weekend.  I am currently half way through Catching Fire and can’t wait to see how the story ends.

One of the benefits of my long commute to work is I have plenty of time for my mind to wander.  Recently I was thinking about The Hunger Games and came up with some key elements from the story that I feel apply to business.

Here are 5 things I learned from The Hunger Games:

Warning: some spoilers ahead

1. Surround yourself with talented people
Consider how essential Cinna, Hamish and Effy were in promoting, training, helping and comforting Katniss and Peeta through the entire process leading up to, and including, the games.  That support team successfully navigated the District 12 tributes through the pre-game activities and generated an interest from the fans and investors for both of them.  Without their help, the in-game gifts would not be possible and most likely neither of them would have survived the games.

You may have a lot of strengths, but you have weaknesses too.  Surround yourself with people who compliment your skill set.  Add people to your network that will push you to be better through their experience, knowledge and abilities.  Learn to take criticism and use it to improve the areas where you are weak – you will be better for it.  What you achieve with your supporting cast of characters will far out perform anything you would have been able to do by yourself.

The Hunger Games (film)

Would you mess with this girl?

2. Invest in your talents and use them to succeed
Before the games begin, we see each tribute showcasing their survival skills to a group of judges who score the players based on usefulness and mastery of the skills displayed.  Similar to Vegas odds, the scores are using by the general public as an indication of a tribute’s likelihood of winning.  The scoring process also impacts the possibility of tributes receiving gifts during the game to keep them alive.

Constantly invest in yourself.  Further develop existing talents or pursue new ones to round out your skill set.  Use your skills to pursue your passion.  Remember little Rue?  Consider how long she lasted in the games by using the skills she had developed during her lifetime.

3. Don’t be afraid to be a leader
Early in the book we learn that Katniss has been providing for her family after a mining accident killed her father.  Her mother should have provided for her daughters, but instead of rising to the occasion to take care of her family she wilted under a crushing depression.  In contrast, Katniss did what she needed to do, hunting, gathering, trading and provided for her family when no one else could.

Don’t wait for a perfect situation or an invitation to be a leader, start today.  If there is a void in leadership, a lack of knowledge or a drought of innovation take steps to correct the situation.  Visionaries see a future, leaders take you there.  Be a thought leader in your space and look for ways to improve yourself and those around you by leading.

The Mourning Path, Bridgend, Stewarton. Linked...

Bring your bug spray and keep on the path

4. Hold steady to your principles
One fascinating element in the book is seeing how the characters respond to incredibly challenging situations. We see some tributes using violence only as a method of defense while others are on the offensive during the games – eagerly hunting down the other players.  At the end of the games Katniss and Peeta make a poison berry suicide pact rather than being forced to kill each other.  The night before the games, Peeta worries that the games will change him saying, “I’m more than just a piece in their Games”.

Do not compromise your principles – not for short term gains, not for long term gains.  This is incredibly difficult to do and can happen without even knowing it.  How do you eat an elephant?  One bite at a time.  How do you compromise on your principles?  One exception at a time.  Constantly evaluate yourself and course-correct along the way.  Ensure you are operating in a way you can be proud of.

5. Whenever possible, let your actions, and others speak for you
When Hamish asks the District 12 tributes what their talents are, neither tribute is willing to reveal their skills.  Instead it is the other person who shares that information about their fellow tribute.  While this is a truly unique situation, it does provoke questions on how to balance self-promotion with the risks that come with doing that.

Having other people praise you for your actions and accomplishments is both rewarding and humbling.  Recognition earned from publishing your own accomplishments always feels hollow.  Yet in our competitive society you need to raise your profile and showcase your talents.  By following the first four key principles outlined above, you won’t need to be a self-promoter.

May the odds be forever in your favor.

What do you think?  Are there any other takeaways from The Hunger Games that you find to be relevant to your personal or professional growth?

What makes a good cloud developer?

This post first appeared on the Enterasys corporate blog site at blogs.enterasys.com and has been updated.

Cloud

These things aren't just for rain any more

Recently a colleague of mine posed a similar question regarding what software skills are needed for college students to have in order to pursue a career in application development.  After I answered the question, I wondered if my response applied to only a traditional, on-premise development career or if it was appropriate for the ongoing technology shift to the cloud.

Before jumping to my conclusion (you will have to read, skim or scroll to the bottom for that) let me share what I believe are the key attributes, skills and personality traits that I would look for in a good developer.

The brain

Critical thinker, but do you want this guy on your team?

Critical Thinking Skills: To me this is a core requirement for a developer and for most knowledge worker positions.  Any developer worth their weight in coffee beans will have good critical thinking skills.  Critical thinking skills for a developer involve converting a vague concept, business process or problem into functional, logical components and to design the most appropriate solution given the environment, restrictions and a host of other factors.  I would hire a person with excellent critical thinking skills, who had little to no experience with a particular language, over another candidate who had experience with a language but could not design sensible solutions.

Attitude: To dovetail to the previous item, if you’re a critical thinking whiz with a healthy dose of arrogance, I’ll pass. I have yet to find someone who is so incredibly amazing at what they do that they can be the office jerk and get away with it.  No thanks. I’d rather someone who is slower or less experienced, yet works hard and does so with a good attitude.

An old microphone

This is one way to get heard

Communication: This skill transcends development – being able to communicate clearly both in verbal and written forms is incredibly valuable.  Developers are often required to do more than just develop – including gather requirements (listening), coordinate testing (facilitation), gather and solicit feedback (facilitation), announce new features (communication), collaborate with coworkers (collaboration), work with customers (negotiation) and present to stakeholders (presentation). Not only will having good communication skills help someone be successful at their job, it also provides them with a powerful mechanism for their voice and opinions to be heard which can shape direction on solutions and strategy.

Constantly Learning: Don’t settle for one language, learn and conquer them all. This will not only make you more marketable, but will also give you additional options when approaching a problem. The pace of technology is accelerating. Unless you continue to learn and adapt to new technologies, systems and concepts you will soon find yourself falling behind others in the market. In sales, you are taught to Always Be Closing (ABC); for developers it is Always Be Learning.

Nature's Finest: Naughty by Nature's Greatest Hits

Who's down with OOP? (Photo credit: Wikipedia)

OOP: You can develop with just about any language in the cloud, however if I were to focus on one to start with I would propose becoming proficient in Java. Java is a solid object oriented programming (OOP) language used by software engineering companies for commercial software and services as well as by IT departments for line of business applications. In addition, expertise with Java would also provide you with knowledge of JavaScript, which is one of the core components to AJAX and web 2.0 website development. If Java isn’t an option, C# is a very close alternative and has similar concepts to Java and is essentially interchangeable. Either way, once you have a good working knowledge of object oriented programming, the scripting languages (Ruby, Python, PHP, Perl) will come easily. I believe that most people can develop with a scripting language but that doesn’t always translate to being a good developer. If you really understand a higher level of programming and object-oriented concepts, then you can quickly and easily master a scripting language which is more likely to be used in the cloud development ecosystem.

Data: Experience with one or more relational databases (MySQL, SQL Server, Oracle, etc) and relational data concepts. Pretty user interfaces are great, but they’re useless without the data behind them to drive the applications. Knowing how to structure data as well as consume it will help you be a better developer. Additionally some working knowledge of XML would be important, especially when working with web services.

Web Services: Cloud development becomes really useful when connecting one or more services or datasets either between cloud vendors or from a cloud offering to an internal system. To do this you will need a working knowledge of web services (REST or SOAP) – how to write them and how to consume them. You can rapidly accelerate the time to delivery of a solution by leveraging existing services in the cloud and knowing how to quickly integrate with them is essential.

There are a lot more items listed above than I expected when I first set out to answer the development question.  Some of the skills are more important than others and most will take time to perfect.  However, someone that can master these skills would clearly distinguish themselves from their peers and they would find themselves with opportunities to work on very interesting and rewarding software projects.

So what’s the verdict?  Does the shift to the cloud require a different skill set from that of a classically trained developer?  I don’t believe it does – the same core qualities and knowledge that makes a person a rock star at developing in one environment are easily transferable to another environment.

I would love to hear what you think about this list.  Let me know what I missed and your experiences with software and cloud development.

How to reward employees when budgets are tight

Dollar

What to do without these? (Photo credit: Images_of_Money)

I manage a team of 10 developers ranging in experience, tenure with the company and role on the team.  I also happen to manage in today’s work climate where the pressure is constant to do more with less and at a pace faster than the day before.

My team works hard.  And when they do as a manager I want to recognize their contribution to the company – the challenge is how can this be done when the budget doesn’t allow for any extra spend?

The reality is, in a world where cash is king it may seem like having none neuters a manager, but I’ve found the following rewards useful and essential to building a healthy, thriving team:

The Walking Dead

Someone in desperate need of a day off...

Comp Time
Sometimes the project deadline cannot be moved and the work just needs to be completed in time.  During these stretches the time leading up to the deadline can feel like Finals week in college where it’s an all out, caffeinated, marathon of a cram session.  I try to reduce how often these sessions occur by gathering good requirements and accurately scoping how long projects will take to complete, but when these situations cannot be avoided, I will often reward the weary developer with one or more comp days.  In addition to being a type of “reward”, it’s also self-preservation, because the last thing I need is for one of my developers becoming an extra on The Walking Dead.

Flexibility
As a general rule I treat each person that works for me as a professional and expect them to work that way.  They have lives outside of the office and occasionally need to adjust their schedule as situations arise.  Being flexible with working hours isn’t necessarily a reward for hard work but it does build a relationship based on trust between the employee and manager.

Recognition
Everyone desires recognition for succeeding and this is a reward with a lot of room for creativity.  I’ve created a Monthly MVP award that I give to the top performer in front of the rest of the team and explain what the person did to receive the reward.  It’s fun – and it’s a real trophy of a baseball player swinging at a baseball – leftover from when I coached T-Ball, which just adds to the fun of the award.  Also, I constantly look to promote my team’s success and hard work to my manager and the CIO.  I will simply cc them on glowing emails or other positive mentions to highlight the value one or more developers give to the company.

Telecommuting
It is becoming ever easier to work remotely – in fact some companies, like Appirio, have a workforce dispersed over the globe with no real central office and operate exceptionally well.  In addition to working in pajamas (which is fantastic) telecommuting offers a number of other benefits such as saving money and time commuting and even giving the employee extra time to sleep in.  But perhaps most importantly, there are significantly less disruptions at home than at the office.

If you do find a some money for rewards, here are two other rewards that come with a receipt:

Delicious Chicken nuggets.

Just say no to drugs... and chicken nuggets (Photo credit: Wikipedia)

Team Lunch
A lunch with the team or lunches with members of the team are great team building events.  In addition to a free lunch it’s a great way to get everyone out of the office for a mental break and provide people an opportunity to connect on more personal levels that may not be possible in the office.  Finally, as much as the budget will allow avoid eating at a restaurant that features a Dollar Menu or has a drive thru.  Don’t cheap out if possible – but be reasonable – black tie lunches probably aren’t too much of a reward either.

Gifts
Small gifts ($250 or less), especially those that are special to the person being rewarded, are excellent rewards.  If I am unable to think of something, I will reach out to spouses and friends through Facebook or other social media to find the perfect gift, size or other detail to make sure the reward hits the mark.  When I’ve had this luxury, some of the gifts I’ve given have been Xbox games, an NHL jersey and even Visa gift cards.

Employees who are deserving of rewards can still be rewarded.  A good manager who uses all the tools at their disposal can keep their employees happy and from keeping one eye on the job boards by being creative and looking for ways to reward a job well done – and without spending any money.

What other rewards have I missed?  How do you like to reward or be rewarded for exceptional performance?