I would find the whole scope (or requirements) of the project so that when we start it we know exactly what we need to do and where we need to go within a specific timescale.
– Who is this for? (the user)
– What do they need?
– What evidence do we have about the problem (fault reports, our own experiences, interviews with users)
– Do we have a particular process or technology we want to use?
– How much can it weigh?
– How much can it cost?
– How much can we spend on tooling?
– When do we want to begin selling it?
– What safety requirements & legal requirements are there?
Basically as many questions as you can think of. In my experience the more you work out the project scope at the beginning, the better the end product.
Comments