May 2012
M T W T F S S
« Apr    
 123456
78910111213
14151617181920
21222324252627
28293031  

Getting user feedback on new designs, but do you go totally by user feedback ?




This is a tricky topic. Conventional wisdom says that when you are planning a new product, it is very important to get user feedback through the process, multiple times. The logic: When the team is working on a new application or software product, they tend to get too involved with their own thoughts, their rationale [...]



The compromise between having a Product Owner who tries to detail out too much ..




Scrum suffers from problems where you have a Product Owner role that needs to have a person who has understood the role in good detail. In a lot of cases, just transitioning the role from that of a regular Product Management role to that of a Product Owner role takes some amount of getting used [...]



Scrum problem – When the Product Owner does not have enough time for detailing the requirements




All those who work in a Scrum project are familiar with the concept of the Sprint Planning meeting where the Product Owner works through the various User Stories from the Product Backlog (reading off the prioritized list), details them out enough that the Scrum team can prepare estimates for these, and answers all queries that [...]



How to get the Design team integrated with the Product owner, including the scheduling (as a part of Scrum)




A part of the problem with using Scrum for product development is about when to get the Design team involved with the user stories. As a part of any development process, whether this be Scrum or Waterfall, or any other development process, it is necessary that the Design team works with the Product Owner (and [...]