How would you advocate not using a shared spreadsheet to track bugs / issues ?
Posted
by
Sylvain Defresne
on Programmers
See other posts from Programmers
or by Sylvain Defresne
Published on 2011-01-06T10:43:20Z
Indexed on
2011/01/06
10:58 UTC
Read the original article
Hit count: 632
In our company, the developers want to use a proper bug tracking tool to manager issues in our application. The management however insists on using a shared spreadsheet (formeerly a shared excel file, now a spreadsheet on a web base solution allowing concurrent access).
Their argument is that the spreadsheet allow them to have a more highlevel view of the state of the project as they can see how many bugs are open with a quick glance. This also allow them to see who is working on each bug, and get estimation of the time required to close them all (as developer are required to fill time estimation of the bug they are working on).
As you can understand, this is not really practical to use for the developers (bug tracking software were invented for a reason). So how can I advocate bug tracking software to ease the work of the developer ?
As a bonus, which software would you recommend that would allow the management to be able to get their feedbacks (number of bugs opens, who is working on them, time estimation) with a high level view ?
© Programmers or respective owner