Predict issue when investigating requirement


Please briefly explain why you feel this question should be reported .

Report Cancel

Hi all,

Almost development teams apply the Agile process now, it means that QA/Tester member will join the team when the requirement comes from client. So, my concern is, when investigating the requirement, and you think there is something risk, may cause some bugs when coding the application/system. Should or shouldn't we raise the risk in this phase? Because, there just a risk, and maybe Dev team know their job and nothing happen in the end.

Lan Huynh

in progress 1
General 1 Answer 1364 views 1

Answer ( 1 )

  1. Thanh Huynh
    October 22, 2015 at 9:14 pm

    Please briefly explain why you feel this answer should be reported .

    Report Cancel
    Hi Lan,

    I like the question.

    To answer your question if we should or should not raise the risk, we need to consider what is the role of testing. To me the role of testing is to find any issue that may threaten the quality of system...and risk is one of them.

    Risk will become worse when we assume it's not a risk :D. My suggestion is raise the risk, bring it to the table to discuss and analyze with Product Owner, Managers, and Team. Not matter what decision is made with the risk you raise, just move forward and you're done your great job as a tester.

Leave an answer

lanhuynh R

About [lanhuynh]

A QA engineer who interesting in Software Development, especially in Software Testing. Willing to learn/research new technology and share knowledge with everyone.