I've recently experienced an epiphany.
I should have seen it earlier. I mean, duh!
I have been using kanban with my teams for some time now, and up until now we have been mostly focused on limiting work in progress (WIP) and evolving our value stream. Only recently did we start trying to reduce the batch sizes of code being worked through the system.
The Changes Have Been Dramatic
Rather than trying to peer review a whole slew of code, the team is engaged in more frequent, shorter peer reviews that are highly focused on just a small bit of code, individual features in most cases.
As a direct result, I believe we are producing higher quality software.
Mind you, I can't prove it quite yet. In our waterfall paradigm, it's going to be a little while before we get to a full release where we go through formal acceptance testing. Because this is the way it's always been, defects in code are going to have to be measured against the previous benchmark established in previous releases.
It Makes Sense
I mean really, this is a no-brainer.
If someone has to spend 4 hours scouring through hundreds of lines of code, it's going to get glossed over and things will be missed.
If someone knows they will get through a peer review in 10 minutes, it's a lot different. Easier to focus. Higher scrunity on the code. Better solutions are developed and collaborated on. Awesomeness ensues.
Not to mention, there is a shorter turnaround time from when the developer codes to when they receive feedback, and when they can disposition comments and make it better. Less knowledge lost, more value gained.
Now the nagging question is....why didn't we start doing this earlier?
|Like this? Share it!|