Those are very good points.  I'll should frame it in terms of risk!

I do try to indicate that it is for the teams to be able to define
their goals not goals from on-high.

While code without any automated tests (and in general a poor quality
rating) is a risk, code that no one is willing to have analyzed is an
even greater risk.

On Apr 25, 1:42 pm, Matthew Farwell <[email protected]> wrote:
> There are two levels, project level and enterprise level. For the
> individual teams, their reasons for using sonar are exactly the same
> as yours.
>
> This is a personal view, but in my experience managers aren't really
> interested in quality and maintainability per se. They are, however,
> interested in RISK.
>
> You could pitch Sonar as a tool for identifying risks. If you have a
> project which is business critical, but that project has a unit test
> coverage of 5%, that is a risk for the company. If the project is too
> complex, that is a risk.
>
> This is doing at project level what you do at package/class level. You
> concentrate on those packages which are critical.
>
> One thing you will need is buy-in from the other projects. Sonar is a
> tool, like any other. You need to use it wisely, and make sure it is
> used as such. If this is imposed from above, it can be used as a stick
> to beat other projects. The figures given by Sonar are an indication,
> not an absolute value of the quality of a project.
>
> Matthew.
>
> 2011/4/25 Eric Winter <[email protected]>:
>
>
>
>
>
>
>
> > We are using it on my team which is composed of a half dozen
> > developers in a company with hundreds of developers.  We see value at
> > the team level.  What is the value at an enterprise level?
>
> > I am planning on presenting sonar to our leadership in hopes of
> > getting some traction there.  I think it could really help focus us
> > and our leadership on the quality and maintainability of our code.
>
> > Thoughts?
>
> > Cheers,
> > Eric
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "The Java Posse" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/javaposse?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to