Should programmer reward a.Lines of code sent to the test department? b.low defect rates delivered to the test department? c.function points delivered each month? d.the number of lines reused from a corporate libary? Now, we should think of what does the programmer actually reward?
1.Pride-in-work, one comments:'well, the system's ok.... I mean it functions, but I can't really take any pride in my work. I'd like to go home feeling good about my program, but I don't. It's just a big mess that barely works.'
2.Pride-in-Accomplishment, Using the principle of small wins as a motivating reward, a team delivers as early as possible the smallest thing that will count as a win for the team. 'simplest first, worst second' let team leans how to work together and gains an early win.
3.Pride-in-contribution, people's desire to contribute is so strong that they could damage their health and private lives in their effort to contribute to the team.
posted on 2009-10-06 21:09
RUI 阅读(159)
评论(0) 编辑 收藏 引用 所属分类:
Software Development