Luciene May 11, 2012, 01:21:07

, you have only written down IMHO why a bug rersttgaiion is inefficient, not agile enough, not fast enough, not good enough for communication. So why not just improve the software instead of completely dismissing the reasons people created a bug tracking system/process software in the first place.Administrator on whatever level have also to keep the system/software alive after it has been handed over. A bug tracking system is sometimes invaluable regarding the information how things were done the way it was done.The Oracle database has a wait interface , extra code which keeps track in the Oracle database how long things need to execute and finish. Someone from Oracle was once asked, Why was it implemented in the first place, doesn’t it make the database slower all this extra book keeping ? This time and processing could have been used for the actual code to finish . His reply wasa0along the lines of The database is nowadays a factor XX faster because it helped us to measure, identifya0and improve what we a0needed to improve . If you don’t measure, you will never know if your agile approach is better than the other way of doing it.I say. Automate, improve the way of gathering this information and its quality. I know for sure that software support and administration people would greatly benefit from all this information gathered during the software cycle way things were done the way they were done while the agile team was communicating and discussing the functionality they have delivered. There was a reason why people started creating bug tracking systems; there are people out there that earn a living creating it. If it didn’t sell, than there wouldn’t be a reason. I say, find out the reason, implement and improvea0the way of doing it or dismiss the reason within a certain context, but If you don’t measure, you don’t know and if you don’t know my arguement is as solid as yours regarding pro or contra. Don’t guess, prove it.