[PLUG] Bug-tracking software.

[Kenneth B. Hill]

On May 15, 2007, at 10:09 PM, Ronald Chmara wrote:

>
> On May 15, 2007, at 10:31 AM, Rogan Creswick wrote:
>
>> On 5/15/07, alan <alan at clueserver.org> wrote:
>>> On Tue, 15 May 2007, Aaron Burt wrote:
>>> > On Mon, May 14, 2007 at 10:12:43PM -0700, Ronald Chmara wrote:
>>> >> Something I've found helpful is to not introduce new  
>>> *software* to a
>>> >> team, but instead introduce new *process*.
>>> >
>>> > +1.  It's all about tha process.
>>>
>>> Sometimes the process gets overdone.
>>
>> The last company I worked for had nothing but process for reporting
>> bugs.  To give a bit of context, I was working in a cube less than  
>> 15'
>> from the data entry people who used the application I was writing,
>> when they found a bug, this is what happened:
>
> Oh dear. This *really* belongs here:
> http://worsethanfailure.com/Default.aspx
>
> Process is not a replacement for sanity, or rational thought... and  
> the fix to a broken process is *not* to keep adding steps until  
> it's so franken-horrid that the whole process itself is rejected...  
> unless rejection is the desired end-goal, of course. :)

I believe a commitment to bug tracking process is the 'key' point. A  
bug tracking application is just like any database application. All  
participants using the bug tracking application must be committed to  
using it and keeping the information updated. This is were good  
project management is necessary.

>
> -Bop
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>