comment on

One way to enforce code quality and integrity in the process is to choose a process model that can facilitate it. Agile methods are good at it. Especially I would recommend looking at Scrum and pay attention to the Definition of Done.

A self guiding process is the best tool to get teams happy, efficient and committed. This includes code quality and standards. I would not dictate them except on a very high level (setting some thresholds). IMO the tools do not matter that much, the result is what I would be interested in. And a good process that includes tools for correcting bad ways of working is priceless.

--
seek $her, $from, $everywhere if exists $true{love};

In reply to Re^3: On Coding Standards and Code Reviews by puudeli
in thread On Coding Standards and Code Reviews by eyepopslikeamosquito

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks