Scott (Tyner Blane) introduced some (to me) new terms describing approaches he uses to build the right software.
The problem he addresses is: how to decide which features to include on your first release.
Even though we all know the including 100% of the ‘must have’ requirements rule, that does not differentiate you from your competitors, since they will be implementing the same ‘must haves’.
In Prioritizing software requirements across releases Scott describes two ways to ensure that the differentiating features are included in your first release:
– fun stuff Fridays
– dedicate one developer as the “differentiator” on your team.
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 <needs>
Our product has <some features>
Unlike our competitors products
We even have <differentiating features>
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!