Below are some risks which we would consider in our previous projects-
1. Delayed releases to QA environment
2. Requirements/changes not communicated quickly to QA team
3. Other ongoing activities on database (if in case multiple activities can't be carried on that server)
There could be more...but above are few generic which I feel can fit here. Please revert in case of suggestions.
Also, this is a good idea to have risks listed here...along with that if we can have mitigation strategy/plan discussed here...would be good.
Hi , thanks for the response, I did some draft, here after the main idea:
A part of project is outsourced to another country (India/Asia). The project team is splitted into differents country
QA leader leadership & efficiency:
Be sure the QAL has a good Leadership and enough trained to manage the project
Validation Quotation under-estimated:
The workload is not enought
Requirements (specification) not accurate:
The requirements are too "open" or not enough accurate to secure the scope for validation
Additional time taken by dev/build and deployment activities
For some reason the internal Milestone are not respected, Deliveries will be not in time, it will "shrink" the validation as the final milestone (ATP) does not move
Team Communication problem
Bad communication inside the project team : valid and dev are fighting .
Even inside Valdia team they are some problems
UAT/FOA under estimated
Be sure the ATP phasis and tasks are properly understand to avoid loss of time & extra workload spending too much time on site
I like to join you guys on this. Much has been said about this important topic. I have read a paper or book from Capers Jones (think that is the correct spelling) and he has done a great job categorizing risks in an experimental way.
Please contact me on CarlosJrFerrer@gmail.com ... we can probably create/share a document in google docs. When we believe we are finished, we can put the results back here to the forums!