The primary notion of rewards within an Agile culture is that the team shares the success or failure of the work they are doing. The driving principle is that unless we all succeed, none of us succeed. There are advantages for rewarding at the team level. Rewarding by team promotes the Agile team culture. Team rewards promote and encourage team members to help each other out. Trust is built when individuals must come together to share information and collaborate. This can work well except that it leaves no room for individual focus and can leave some top performers feeling underwhelmed. So the question is, is it so simple to say that we “only” reward as a team?
It is true that some team members will align with the Agile culture quicker than others. Also, some team members will, in fact, contribute more than other team members. And maybe sometimes, it is important to acknowledge exemplary work when it occurs. However, individual rewards can lead to unhealthy competition. Past leaders who have been constantly rewarded for being the superstar will have a hard time with a team reward approach. Under-performers may find it easier to lay low in an Agile team and just do the minimum. By providing more reward to some team members could lead to a feeling of jealousy and resentment. This is problematic in not only an Agile culture but any culture.
Ultimately, you do have to remember that you get the behavior you reward. If you give reward at the individual level, you will get a level of competitive behavior and a willingness to place personal achievement over team accomplishment. If you reward at the team level, you will get a level collaborative behavior that places team accomplishments over personal achievement.
Team Reward Approach
Within an Agile context, rewards should be supportive of the team culture. The question is, what does a reasonable reward structure look like? First it is important to acknowledge that answer isn’t straightforward. It depends on your context and situation. As a suggestion, consider starting by making at least 50% of the reward based on team collaboration and success. Then over time increase the team reward part to make it a major part of the rewards, and still leave a small percentage available to acknowledge individual growth, exemplary work, and more adaptive alignment to an Agile culture.
Not all Rewards are Created Equal
What is meant by reward? Not all rewards are created equal and a reward for one person can mean something difference from one person than another. To some employees, reward means money in the form of a merit increase or bonus. For others it can mean advancement and more responsibility. Yet for others it’s the ability to have freedom to work on what they want. As part of self-organizing teams, you can have Team members recognize each other. For example, during a Sprint retrospective (if this is being applied), the first part of this event can be where team members recognize each other for their help, assistance, helping the team drive forward, complete stories, and more.
Team Reward must Live within a Team Culture
very good thoughtReplyDelete
I certainly agree with the importance of rewards and here's a few "best practices" (oh oh--here come the comments!) that I really like.ReplyDelete
1. Never incent (dangling carrots). Incentives may work once, but generally change a team culture to one of ego, cutting corners, and bad culture. (Websters defines incentives as "bait," by the way.
2. If you publicly reward the team and treat everybody equally, you've probably watered down any benefits of appropriate recognition. For the entire team, do something nice (party, day off, ...).
3. Private, TIMELY awards can really do wonders. These gestures can be most anything (letter from the CEO, private bonus, night out on the town for two, ...) can really be motivating and can easily be a retention tool.
another thing to experiment with: give "rewards" after the fact. And don't give them every time. When you always give a reward after something is done, a lot of people will work for the (even un- announced) reward. And this external motivation is lower then their intrisic desire....ReplyDelete
Here is a slidesdesk from a workshop I did with Vera Peeters at XPday Londen in 2008:
Agile programming is always a team work strategy. If you have strong and sharp minder team you get best result in your project and manage your project easily.ReplyDelete
Very informative post agile system development can help us to improve our products quality. Agile practices deliver just enough functionality to meet the stakeholders needs with high quality. The sprint retrospectives, allowing the scrum team to continuously improve processes and work.ReplyDelete
I am bit confused whether to opt for Scrum credentials or attend a PMP prep course / PMP classes preparing to take PMP certification exams. Any thought?ReplyDelete
Heres a thought inspired by Capt David Marquet. Establish a reward in advance that ypu WANT to give the team, and ask them what they need to achieve that reward. An agile team needs lean agile leadership to thrive; ask the team to help you create that environment by getting their input through reward targets. The best rewards are not surprises, they are acheived by working towards a goal.ReplyDelete
Hi ! I read your blog, it was really interesting. Virtual R&R Corporate Events Celebration themes for workers to appreciate their efforts and creativity to boost the confidence of employee engagement.ReplyDelete