QA Project RISKs management

It was found that RISK (unavailability of test data, test phones, Software, Skills etc) identified in QA projects are not

1) Communicated to all stakeholders

2) Tracked and current status is not known

3) Assigned to someone to take action

4) Prioritized

5) Action taken etc are not documented

RISK management is done on ad hoc basis and we cannot continue this trend.

QA will be using bugzilla to manage project RISKs by introducing component “RISK” to all bugzilla project.

Note: We thought of using a new system. But bugzilla has all the features required to manage RISKs.