Eight potential reasons why badges, achievements, and trophies might work are:
- They anchor our performance expectations higher
- Having goals increases our self efficacy
- Completing goals leads to satisfaction
- They create goal commitment
- They act as guidance mechanics and provide feedback
- They facilitate psychological flow through feedback
- They trigger social proof
- They trigger motivating social comparisons
Agile is full of ceremony, some of which remind me of these points:
- The team’s velocity anchors the team to what is considered a good performance
- The sprint goal can communicate expectations beyond the team’s previous velocity
- A successful sprint can be celebrated
- If the goal was reached with time to spare, the team can be more ambitious next sprint
- Progress is tracked through the sprint dashboard, Kanban board or other post-it heavy contraptions
Adam Tornhill - @AdamTornhill
“Software development is a social activity”
Code reviews vs. you are not your code.
You are your code, in order to improve we need to embrace this.
“We are anything but rational”
Pluralistic Ignorance - group bias where everyone public supports an idea that they don’t agree with in private. Common in every project.
Fight your biases.
Bias reducing social hacks. Assign the role of “Devils Advocate” in every discussion. Remember to rotate the role. Also scheduling a follow up meeting after taking important decisions. Prevent your emotions from dictating your decisions.
Base your decisions on data.
Take pretty much any popular practice, technique or method. The same story again. We don’t understand why the tools we use work and simply blindly apply them. Doesn’t that fulfill a definition of a cargo cult?
Software engineering needs to get out of its guru-phase.
Via Still Drinking:
This is what it is to learn programming. You get to know your useful tools, then you look around, and there are some handy new tools nearby and those tools show you the bottomless horror that was always right next to your bed.
It's funny 'cause it's true (mostly)! A must read.
What’s the moral of this story? To me, it’s this: if you have a giant document detailing manual steps for programmers to follow to get something done, what you really have is a spec/user story for your next development cycle. Automate all the things, and then burn those documents at a cathartic, gleeful camp fire. You can turn your onerous processes into roasted marshmallows.
This XKCD is relevant.
And this one.