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.

A parable:

A software development manager her people "There is no time to do code
reviews or pair programming. We can't waste time on things that don't
produce code. We have too much to do! Focus on getting the code written and
tested."

The developers and testers quietly nodded and got back to coding and
testing.

Having successfully managed her people, she rushed off to a dentist
appointment. As she sat in the chair she said to the dentist "I know I need
some work done on that tooth. But, I have a lot going on back at the
office. Please save some time and just get to work on the tooth. Don't take
x-rays, don't bother sterilizing the tools. I'm sure I'll be fine if you
just get to work."

The dentist laughed and asked the manager to leave.

</parable>

I wish managers and developers expected each other to be professional in
their skill. That managers and the managers' managers realized that the
professionals they hired know what needs to be done.

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?
>
> 
>