Thanks for your comment Avi. Personally, I am not a great fan of technical stories. I prefer to use a modelling language like UML to describe requirements for a technical product like an internal software platform, as I find natural language too ambiguous for the job. Hope this helps!

Hi Mag, Thanks a lot for sharing your approach to gather and manage user feedback at Planbox! It’s great to hear that you value feedback and act upon it. My preference is to combine qualitative and quantitative techniques, for instance, interviewing users and measuring which features they actually engage with. This makes me think I should write about the different approaches and their strength and weaknesses in a future post. Thank you!

I regularly read your blog and my eye caught the image of this post. We have an image on the Planbox home page that looks almost the same!

I totally agree that user feedback needs to be regularly integrated to the backlog and that it greatly helps in defining priorities. At Planbox, we get back to all the users that submit feedback – big our small.

We were finding it hard to keep track of all our user feedback so we developed a widget through which users submit feedback so we can then wither create a story from that feedback or add it to an existing story.

What’s also important is to communicate with the users who have submitted the feedback. To let them know they have been heard and have helped.

Mag

Thanks for your feedback, Yi.

Glad to see your post on emphasizing the emergent property of good product backlog. Static backlog is a clear smell. I happened to write on the same topic recently, http://blog.odd-e.com/yilv/2012/01/we-dont-have-emergent-requirements.html

Thank you!
Yi