Comments on: Prioritizing software requirements across releases http://tynerblain.com/blog/2006/03/08/prioritizing-software-requirements-across-releases/ Software product success. Fri, 12 Mar 2010 01:42:39 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Scott Sehlhorst http://tynerblain.com/blog/2006/03/08/prioritizing-software-requirements-across-releases/comment-page-1/#comment-353 Scott Sehlhorst Sun, 12 Mar 2006 16:18:19 +0000 http://tynerblain.com/blog/2006/03/08/prioritizing-software-requirements-across-releases/#comment-353 Another benefit of multiple releases is sustained interest in the software. I read an article by someone who tracked his software sales for a product over a couple years. He found that both revenue and revenue growth correlated with frequency of update of the software. I wish I had tagged the link to share it, but I didn't. Sorry. Thanks for the comment/trackback! Another benefit of multiple releases is sustained interest in the software. I read an article by someone who tracked his software sales for a product over a couple years. He found that both revenue and revenue growth correlated with frequency of update of the software. I wish I had tagged the link to share it, but I didn’t. Sorry.

Thanks for the comment/trackback!

]]> By: Harry Nieboer http://tynerblain.com/blog/2006/03/08/prioritizing-software-requirements-across-releases/comment-page-1/#comment-335 Harry Nieboer Thu, 09 Mar 2006 21:59:57 +0000 http://tynerblain.com/blog/2006/03/08/prioritizing-software-requirements-across-releases/#comment-335 Differentiating features are important. When doing a RUP project, the differentiating features are looked after and documented in the Vision document, in the "Product position statement". That statement has the form: For our customers Who have Our product has Unlike our competitors products We even have The product position statement is a great tool for MoSCoWing (deciding whether a proposed new feature is Mandatory, Should have, Could have or Would/Won't have). It the proposed feature aligns with the product position statement, include it, otherwise drop it! Another rule of thumb on including/excluding features is that you need to keep some features for the next release in order for the customer to be willing to do an additional pay. If all nice features are in your first release already, why would he bother bying your next release... Differentiating features are important.

When doing a RUP project, the differentiating features are looked after and documented in the Vision document, in the “Product position statement”. That statement has the form:

For our customers
Who have
Our product has
Unlike our competitors products
We even have

The product position statement is a great tool for MoSCoWing (deciding whether a proposed new feature is Mandatory, Should have, Could have or Would/Won’t have). It the proposed feature aligns with the product position statement, include it, otherwise drop it!

Another rule of thumb on including/excluding features is that you need to keep some features for the next release in order for the customer to be willing to do an additional pay.
If all nice features are in your first release already, why would he bother bying your next release…

]]>