Agile Testing Question:
Tell me what is your approach when requirements change continuously?
Answer:
This question can be asked if you are interviewed for an agile QA position where requirements are likely to change frequently during development. Although a complete change in requirement is possible, most of the time, it is the technical details that are subject to change. e.g. the intent of the requirement or behaviour of the feature is the same but implementation details can change
A: Some possible answers can be:
☛ Write generic test plans and test cases which focus on the intent of the requirement rather than its exact details
☛ Work very closely with the product owners or business analysts to understand the scope of change so testing can be updated
☛ Make sure the team understands the risks involved in changing requirements especially towards the end of sprint
☛ If you’re going to automate this feature, it is best to wait until the feature is stable and requirements are finalized
☛ Negotiate to see if the changes can be kept to a minimum and/or implement the changes in next sprint
A: Some possible answers can be:
☛ Write generic test plans and test cases which focus on the intent of the requirement rather than its exact details
☛ Work very closely with the product owners or business analysts to understand the scope of change so testing can be updated
☛ Make sure the team understands the risks involved in changing requirements especially towards the end of sprint
☛ If you’re going to automate this feature, it is best to wait until the feature is stable and requirements are finalized
☛ Negotiate to see if the changes can be kept to a minimum and/or implement the changes in next sprint
| Previous Question | Next Question |
| What is test driven development in Agile Testing? | Tell me what is Spike and Zero sprint in Agile? What is the purpose of it? |