|
I thinking about how increase developer's commitment to release and create release cycle as a game for more fun in office. Current suggestions
|
|||
|
|
Can't we just have developers who understand why a proper release process is important and do it out of a sense of professional pride? |
|||||||||||||||
|
|
Hudson supports something similar Take a look at the Hudson continuous integration server. It has plugins that support games to that developers get points for successful builds, but lose badly if they commit a broken build. Might be better than building towers... |
|||
|
You can create a puzzle with an image representing your system in a visual way. And then after each release you will add pieces of puzzle to the appropriate parts of the system. That game would need clear vision of what you're building and work good designer. |
|||
|
|
|
Obviously those in charge have not provided the proper motivation to make everyone follow this standard. Punish one, teach a hundred. I'm not saying it's the same level, but this is one of those necessary evils like filling out a time sheet. You do it right and on time or you have to go. Now, a game that encourages everyone to enter quality code for those release cycles would be fun. Maybe the code review process could be like stack overflow. Your code is basically the assumed question "how good is this code?" and everyone gets to review, comment, up/down vote with points and badges, tshirts and bragging rights. There can be some scoring to see if it is good enough to commit. Write code and get it evaluated along with taking responsibility for reviewing others is pretty much what programming is all about in a team environment. Teamwork is more than just cubicle location. |
|||
|
|
|
I'm sorry, but your current ideas sound like bullshit managerial metaphors to try and trick your underlings into caring.
This one reeks of a thin veneer of false incentive. A physical reminder of the work ahead and behind. I understand the theory. It's supposed to make it fun and give people a physical thing to take pride in. But I have never seen such a ploy work. At best it comes off as "yeah, that's Bob's thing, he likes to see how we're doing". At worst the reinforces the cynical ones to feel like they're being treated as stupid children. Even as as child I could see through this sort of bullshit.
As depicted as what? A chart with a mountain in the background? Same sort of managment fluff as the brick tower. If you want to make your motivational powerpoint slides more cute, sure, go for it. But "cute" doesn't get code out the door.
Now, this one I had to contemplate. At SE, I come here of my own free will and participate because I care. ie, I'm already motivated. The bronze badges are mostly bullshit incentivators to go try out all the different aspects of SE. The 'nice answer' and 'good answer' badges I actually do kind of care about. Because those are a judgement of my peers. Nameless, faceless peers that melt into the masses in a way that is completely unlike a small development team. You could try an anonymous employee of the month submission. But if you want to gameify code releases, you should actually incentive your coders. I wouldn't particularly hand out money. See RSA motivate. No, if the team makes a goal, give them a reward. Real rewards. From wearing jeans, free pizza, extra time off, an Xbox in the lounge, choosing their next project, or actual money. Let them all submit reward proposals and vote on what they want. Veto what you will and then organize a tiered reward system which makes meeting and beating deadlines a game with actual rewards. Without real rewards, gamification only works on the gullible and easily deceived. |
|||
|
|
