We are doing a new project on Agile and wondering for some thoughtful suggestions in a unique scenario.
We have an idea of what users want to achieve - high level requirements and are currently designing the system. At this point what would be the role of QA in Inception?
Other than integrating them on the team and giving them testing tasks for the Project Tasks as well as having QA give input into the requirements and design since they also have experience with the application?
Typically in requirements gathering QA is useful in pulling out requirements as well as helping to think about issues that might come up such as compatability and supportability.
Nothing learns better than experience.
"So as I struggle with this issue I am confronted with the reality that noting is perfect."
Well...this is a obvious question that what would QA do during requirement and design phase of a system. Well to answer that I would say a QA should be rather say must be involved from the day 1 of the project. That helps QA to understand the product requirements clearly and completely. Also QA can get involved in foreseeing some issues, risks, identifying gaps during requirement and design phase only. This definitely avoids some issues to carry forward and leads to a better quality product.
During these phases QA can come up with test plans, test strategy and scenarios, test cases etc.
Please share your thoughts on the same [img]/images/graemlins/smile.gif[/img]