So, situation is quite tough. As a test-manager, I have a need to create an approach when the team has a situation: when requirements and specifications are not accomplished and don't satisfy the definition of ready for testing quite often. To be honest — we don't always have 100% requirements on that project.
Situation with requirements seems to be incorrigible at the moment, so I need to create an approach when testers will check product without requirements, which sounds a little bit crazy. But we need to be adaptable.
In my mind, we could try ad-hoc sessions before we have any clarity about what should we have in a requirements. Developed feature should be tested in an ad-hoc style (30 minutes), testers would collect lists of questions and problems, deliver those lists to the other members of team (developers, designers, manager).
Next step is a collecting the answers about functionality and design. And after that, exploratory session starts (90 minutes). After that it is supposed to store much more information about feature, more questions, more defects, more answers, and after that testers should create a test-design for most important test-cases. Why? To have a documentation for regression checks (it is not supposed to be automated soon in that project).
So scheme is like:
ad-hoc -> collect information -> exploratory -> collect information -> test-design (most important cases) -> exploratory + documented testing (final checks) -> moving to regression
Do you have any ideas about that? Should it work, and how can I improve that approach?