Re: [SCRUMDEVELOPMENT] Re: Does your development tea m do code review? Or do you wish you could? I’ve a few que stio ns and would like your input.

Esther,

Among many in the Agile world, code reviews are known to be an inferior
practice to better ways of preventing defects and creating quality designs.
Many of us will be reluctant to give arguments in favor of code reviews
simply because we don't want people to do something inferior. The well you
are attempting to draw from might be a bit dry.

Besides, my answer to "What do you wish managers knew about <better
practice X>?" would be similar, whatever X might be.

Alan


On Fri, Oct 2, 2015 at 1:31 PM, [email protected] [SCRUMDEVELOPMENT] <
[email protected]> wrote:

>
>
> You're right; it's not what I was looking for. :-)
>
> 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?
>
> So can we please keep to one topic? and ideally the one I'm asking about?
>
> 
>