We came up with a quick plan focussing on the purpose of the 'backlog buster' - who was it for? what kind of problems would it solve? and we sketched out a few user personas.
"Backlog Buster helps dev teams ship sh!t quicker!"
"It's a collaborative tool to help startup teams prioritise feature requests and work out WTF they should build next!"
"Less shouting. More Shipping!"
The primary users we had in mind were:
User #1 - Derek a product owner, experienced with tech teams and the inefficiencies of pro-longed decision making. He is the middle man who gets frustrated with never ending client requests. He wants collaboration from the whole team, to create a good atmosphere where he can easily act as the facilitator.
User #2 - Phillip is a freelance developer who needs a tool to communicate between client requests and a to-do list. He's on the go, a versatile worker, picking up multiple projects in one go. He currently uses Google Docs and/or spreadsheets to keep track of what's on the pipeline but wants a tool to improve efficiency, workflow and communication so he doesn't have to stop-start all the time.