Editing Talk:Objective:One place to track feedback

:There is one (important?) detail in the way new features are introduced in the Maemo SW official products. Small enhancements, really small ones going down to the code and not touching much the UI, can be implemented directly by lead developers without much internal negotiation. You have example with Marius with the Application Manager or timeless with the browser. However, anything bigger than that e.g. a new feature that introduces an API change, a visual change or a new entry in a menu, will easily involve the development team and very likely the related product manager. In this case timings and processes are different, and the developer alone can't just go and hack. The ''worst'' is to fall in between, something too big for a developer alone to hack in an afternoon but too small to fall in the priorities of the team and product management.  

:There is one (important?) detail in the way new features are introduced in the Maemo SW official products. Small enhancements, really small ones going down to the code and not touching much the UI, can be implemented directly by lead developers without much internal negotiation. You have example with Marius with the Application Manager or timeless with the browser. However, anything bigger than that e.g. a new feature that introduces an API change, a visual change or a new entry in a menu, will easily involve the development team and very likely the related product manager. In this case timings and processes are different, and the developer alone can't just go and hack. The ''worst'' is to fall in between, something too big for a developer alone to hack in an afternoon but too small to fall in the priorities of the team and product management.  

:I see that IdeaStorm might work well to drive the attention of product managers on those well formulated features that are clearly pushed by the community. Better than bugzilla supported by plans in wiki pages, I still don't know. This has a lot to do with users voting and the information being well organized. If IdeaStorm is seen as more attractove by users and they participate more and better than in bugzilla, then fine. But we have one tool more to feed and maintain, and this is why I prefer that we are totally sure that it's going to be used and useful. What I don't see is this workflow you describe from IdeaStorm to bugzilla, as I don't see bugzilla as a tool to organize tasks (others do, certainly).--[[User:qgil|qgil]] 19:10, 24 July 2008 (UTC)

:I see that IdeaStorm might work well to drive the attention of product managers on those well formulated features that are clearly pushed by the community. Better than bugzilla supported by plans in wiki pages, I still don't know. This has a lot to do with users voting and the information being well organized. If IdeaStorm is seen as more attractove by users and they participate more and better than in bugzilla, then fine. But we have one tool more to feed and maintain, and this is why I prefer that we are totally sure that it's going to be used and useful. What I don't see is this workflow you describe from IdeaStorm to bugzilla, as I don't see bugzilla as a tool to organize tasks (others do, certainly).--[[User:qgil|qgil]] 19:10, 24 July 2008 (UTC)