Timeline for Implementing Peer Review System
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 24, 2012 at 17:45 | comment | added | jcmeloni | @Salman What the Valve handbook says in section 3 is very similar to what a lot of companies do, and is precisely what what Jacob G's answer and my comment speak to. That's not the same, really, as what you described in the second paragraph of your answer. Putting employees into active competition against each other is a recipe for disaster, as Jim in Texas also noted above. Perhaps we read the tone of your example incorrectly? | |
| Jul 23, 2012 at 21:12 | comment | added | Salman | I've updated my question, you can check and comment. | |
| Jul 23, 2012 at 20:31 | comment | added | Jim In Texas | "I think it will be fun, competitive and engaging" It will be fun for you if you like making your team into a collection of competing individuals. You'll certainly get your rear end kissed more frequently. Your idea will NOT be fun for your company's bottom line as your team members worry more about being voted off the island and less about creating a good product without worrying about who gets the credit. | |
| Jul 23, 2012 at 2:13 | comment | added | jcmeloni | I agree; code review as part of development lifecycle plus 360-degree feedback at review/evaluation time, would go much further toward producing a stronger team and product. | |
| Jul 23, 2012 at 1:14 | history | answered | Jacob G | CC BY-SA 3.0 |