Re: [SCRUMDEVELOPMENT] Does your development team do code review? Or do you wish you could? I’ve a few questio ns and would like your input.
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <CALaPUVfDdAZNZT5E-5_-T+jdDFNfvEyX40xiG=L-BhDD5QqT5Q@mail.gmail.com> |
On Friday, October 2, 2015, [email protected] [SCRUMDEVELOPMENT] < [email protected]> wrote: > > > You're right; it's not what I was looking for. :-) > Mea culpa ;-) > I've no problem with pair programming, certainly. But it might frustrate > you if you asked, "What should the boss know about pair programming?" and I > said, "That we should do code reviews!" > > An effective and top-quality software development process can include more > than one process, right? There's nothing wrong with pair programming _and_ > code review? These can exist? > > Yeah. I've been on teams that do both, usually because they are pretty new to pairing. Once you are pairing effectively the reviews immediately feel redundant in a palpable way. > So can we please keep to one topic? and ideally the one I'm asking about? > > If you aren't practicing collective ownership then code reviews will do little mitigate the effects. If you are then code reviews are a waste of time. So, they are a stop-gap. That is something I wish managers understood about them. Stop-gaps are not bad things as long as they don't become codified practice. They should be transitional. As a transitional practice code reviews can be effective if done face-to-face preferably with the whole team present.