<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY>
On Fri, 2006-09-29 at 14:29 +0200, Adrian Brock wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Thu, 2006-09-28 at 13:08 -0600, Andrig T Miller wrote:</FONT>
<FONT COLOR="#000000">> Having them unscheduled doesn't hid them under any rug. They are</FONT>
<FONT COLOR="#000000">> just as visible in JIRA. </FONT>
<FONT COLOR="#000000">And just as unprocessed as when we used sourceforge and nobody</FONT>
<FONT COLOR="#000000">was trying to monitor the problem.</FONT>
<FONT COLOR="#000000">> > </FONT>
<FONT COLOR="#000000">> > Assigning to a release, forces somebody to remove</FONT>
<FONT COLOR="#000000">> > them from that release. So they are least looked at.</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> All it really does is force someone to go into JIRA and change</FONT>
<FONT COLOR="#000000">> the fix version, not to actually evaluate the issue.</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">That just comes down to how good a project lead you are.</FONT>
<FONT COLOR="#000000">If you are continually bumping problems to the next release</FONT>
<FONT COLOR="#000000">then we have to ask what are you doing?</FONT>
<FONT COLOR="#000000">> To really solve this, is we need a formal review process. It doesn't</FONT>
<FONT COLOR="#000000">> matter whether something is assigned to a release or not. We have to</FONT>
<FONT COLOR="#000000">> have formal, mandatory review as a team.</FONT>
<FONT COLOR="#000000">I'm a great believer that you cannot replace human intervention</FONT>
<FONT COLOR="#000000">with automation when it comes to effective management.</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
I agree completely. <BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">But the person that manages things needs to have reasonable metrics.</FONT>
<FONT COLOR="#000000">Forcing people to go through a process of review (even if it is</FONT>
<FONT COLOR="#000000">just bumping it to the next release) gives an indicator</FONT>
<FONT COLOR="#000000">of how much on top of the problems we are.</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
What I envision for the review, is we will not allow issues to be moved from release to release to release. I also think that we will be able to put the right incentives in place to make sure that issues are resolved in a timely manner.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Rather than the current situation, where we don't have a clue</FONT>
<FONT COLOR="#000000">what is getting reviewed, because according to JIRA it is nothing!</FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
Andrig (Andy) Miller<BR>
VP, Engineering<BR>
JBoss, a division of Red Hat
</TD>
</TR>
</TABLE>
</BODY>
</HTML>