At Borland, we have a adopted a agile way of working on product roadmaps, keeping the roadmap as a "live" document which is shared constantly with stakeholders instead of being a "snapshot" document.
This helps us to bring more cohesion between engineering teams and our strategic customers and stakeholders by providing current view of our direction and eliminating long periodic pauses and "out-of-sync" commitments.
One of the key aspects of this document is understanding of market segments that is going to be catered to, with every planned release.
In my opinion, there are 4 aspects to understand the most suitable segment for a release
- Role of the user (e.g. developer, project manager, business analyst) : Who is going to use the product, what are his/her general capabilities, what are the other tools used by such role.
- Size of the group (individual, SOHO, SME, large enterprise): What is the collaboration level required, what is the spending capacity
- Maturity (unstructured, follows standards, decides standard): What processes and work flows impact usage of product
- Exposure (direct sales, inside sales): How is the product going to reach the customer? How close is the customer to out business?
Posts
No comments:
Post a Comment