...
In my opinion surveys wont work and as someone mentioned, focus groups promote group think.
Get all your stakeholders into a room , use simple post it notes and get the participants to note down user stories ...." As a ( role ) I would like the system to do ( Functionality ) so that it helps me do ( Business benefit ) "
Get your business analyst or you do the task of grouping similar requirements
This is your Product backlog .
Now you need to "Refine" the user stories further and it may be that they are at a "Feature Level" and need to be broken down further into Epics and then User Stories.
The next steps would be:-
1) User Stories Refinement Workshops (more than one) with Product Owner . The User stories must be
Independent.
Negotiable.
Valuable.
Estimable.
Small.
Testable.
2) Work with your product owner and Business Analyst to define and record acceptance criteria for each user story.
3) You must then Prioritize the user stories with your Product Owner and Business Analyst . You can use MoSCoW
Must Have
Should Have
Could Have
Won't Have
4) Then get an agreement with your product owner what your Minimum Viable Product is that is to be delivered ....It's definitely Must Haves and Most of Should Haves...If time permits, you will deliver the Could have's but the Won't haves are out of scope.
5) This final set of requirements and user stories are your Scope Statement for the Product .
Remember that a Project Scope Statement is more than just the product - it should include
Documentation:- Test Plan/Strategy , Test Cases, Test Report, Design Specifications , Project Plan, Risks and Issues Log, Implementation plan , Support plan , Project Schedule (includes product sprints ) .
Activities :- Solution increment or functionality should be Designed, Developed, Implemented, Deployed, Tested , Shipped . (Using Agile , all these activities could be happening in parallel in each sprint)
So your Overall Project Scope = Product Scope + Project Management Deliverable and activities
