Use of separate tracking system for system with many defects

[blacklp]

The Scrum Primer v2.0 says "(A system with many defects usually has a separate defect tracking system.)" at the end of page 6. I am wondering if this is something that should be mentioned in this guide as a usual practice done by Scrum teams. The reason I am questioning this is that I am afraid that, when keeping a separate tracking system for defects, transparency might be compromised due to the fact of having to look at two different tracking systems, one for defects and another one for features, continuous improvement, etc. Despite not being enforced in this guide to use a separate tracking system if the system has many defects, I would challenge the need for mentioning it and implicitly considering it a usual Scrum practice. Looking forward to hearing your feedback on this. Thanks! :)

[basvodde]

Thanks for raising this. We'll consider it when planning an update, which I'm not at the moment!

I partially agree. The emphasis is on "many". Otherwise, there is no need for a separate system.