When should test analyst get involved in a project?
Will it be immediately the requirement specs are complete or before that,
When is the ideal stage to get involved.When should the creation of test cases commence ( after requirements) ?
Although I agree with Darrel I want to remind that it is not as black and white as he pictures... what if a company is not willing to invest in requirements, i.e. given that customer is happy with requirements AS IS they may or may not want fixing it based on tester's feedback
Term optimal for managers means maximal ROI. The earlier testers are involved the bigger investment is. The return is however hardly measurable.
?:the art of a constructive conflict perceived as a destructive diagnose.
Ainars, I don't agree with you. As long as you have such document, it has to be clear to avoid any misunderstanding between functional and technical teams, or between the company and the customer. In my view, tester feedback is important prior to submit the document to the customer to reach such objective.
That's true that some customers prefer to have unclear requirements in order to be able to tune the product (or even to define their real needs) by raising issues. By, for sure in this case, ROI is not maximal.