If you want to be a successful software development company, you have to make sure you work on the stories that bring most value to the customer. Ideally you have an on-site customer that can tell you which story can bring most value. What do you do if you don't have luxury of having the on-site customer? Or how does on-site customer decide what is of the biggest importance to him? How does your company prioritize epics, stories and projects?
On XP2009 conference I will be running a game devoted to making participants feel the business value origins and flow. Players will form software development companies, prioritize their customers requests by business value and feel for themselves how different strategies help to earn money and maintain healthy relationship with the customers. This game has been run on several conferences and it always brings a lot of fun.
Register for XP2009 if you haven’t done so yet, come to this workshop and learn where the business value comes from.
Bookmark/Search this post with:
In a perfect world,
there is one product owner who knows the market, knows the
application and can assign business value to each function on the
backlog. But coming up with a dollar value for a feature can be
difficult and in a joint venture the problem is compounded, because
stakeholders with complementary interests may have a very different
basis for valuing a function. There are two product owners, so the
situation can be very delicate. How can the two parties agree on
priorities for the next release?
Bookmark/Search this post with: