We don't have an agreement on how to go about this process.
The characteristics of what we are building:
- There is already a market, and its already saturated. Meaning there is established competition.
- We don't know how our competitors do it.
- No two customers are the same. Its easy to define features. Its not easy in deciding how to implement them. [Point 2 is emphasized here again].
Given this plight of things, I am of the opinion that we sit together (may be for a day or two) and generate a matrix of common problems faced by the business (I think we call this business case), and jot down their solutions - i.e. the traditional business solution (with its pros and cons), our product's solution to the problem (with pros and cons). We can freeze on this by having it reviewed with stake holders.
Post this we can begin the task of creating user stories, wireframes, etc.
However, we actually go about building the user stories with a few business cases which on the whole fail to convince us on the acceptance of the system, or gives a false assumption of acceptance.
What is the actual way to go about it?