Unclear requirements - alexanderteplov/computer-science GitHub Wiki
Estimation with unclear requirements
Go for Agile. The good thing is that we can start with what we have and go for an iterative development cycle by requesting feedback from customers at every stage of development.
Try phased. Divide the project into different phases and work with the unknowns.
Add to risk. When the requirements are not clear we need to record that the estimates are based on unconfirmed assumptions.
Make assumptions. Normally the PM can start the project with some carefully planned assumptions based on the best knowledge on the domain.
Communicate with stakeholders. Report that the requirements are not clear to stakeholders.