Recently we discussed how we no longer knew exactly what each other was doing. We might know generally what part of the product they were working on (through standups), but now had very little idea of how they implemented technical details. With standup time being the same (15 minutes) and the number of people who had to speak doubling, there was no way we could fit in extra discussion. We threw around having occasional code reviews, but anything that isn't regularly scheduled tends to fall by the wayside pretty quickly.
Our final solution was for the whole team to show up to our biweekly demo an hour early and go over what we changed on the projector. It's a perfect time to show completed code, do knowledge transfer AND prepare for the demo.
Posts
We use Atlassian Crucible and create code reviews for every feature we work on.
ReplyDeleteCrucible looks pretty cool, but I think that good code reviews have a lot more to do with the mentality than the tools. If people really want their code reviewed, a way will be found. I personally am not in favor of "heavy" tools that can take time and/or money to setup and then get neglected, but I'm sure this is a "to each their own" topic.
ReplyDelete