How to Increase Code Quality Using Gamification
summary
Describes a Jenkins CI plugin and a Quincy prototype that gamify Java build and test practices: the plugin deducts points for failed builds and grants +1 for each new JUnit test, with leaderboards and a team currency, while Quincy links build results, tips and challenges to rewards and sends a 15-minute team notification when a build stays broken. The system is motivated by crowdsourcing and apps like RunKeeper/LinkedIn, deployed in one project to encourage developers to write tests and promptly fix broken builds.
AI-written summary · about
chapters (13)
- 0:00Introduction to gamification
- 1:12Why games are powerful
- 6:57What is gamification
- 13:30Problems with gamification
- 14:53Gamification in practice
- 20:38Game mechanics for code quality
- 21:22Competition in gamification
- 24:37Peer pressure and team dynamics
- 27:28Progression and growth
- 30:15Mentoring and learning
- 32:43Reward systems and incentives
- 35:00Demo of the gamification app
- 41:25Workshop and Q&A
related talks
58mHow I became a tester!
44mPlay! Or: How to Get Better While Playing
17mCreating Happy Engineers - Anecdotes from the Trenches
45mDeveloper Joy – How great teams get s% t done
01h 03mHow To Do Kick-Ass Software Development
51mHow I lost my QA job
31mAssembling Excellence: Crafting a Quality Assurance Team from the Ground Up
01h 00mBuilding better developers