A new feature in your product refers to added functionality. It’s making your product do something that it didn’t do before. Keep a unified list of your feature requests. Prioritize them, and keep a basic estimate of the time involved to investigate or add the feature. You may also want to keep a list of the top items on your white board for better visibility.
How Do I Get Started?
Same list as with Issue Tracking.
Am I Doing This Right?
- do you use this system as a first stop when it's time to generate the next release's feature list?
- do you routinely record new product ideas in the system?
- do you reject many of the submitted feature requests?
- can you generate the last product version's "new feature" list by running a report?
- can your stakeholder easily check on a feature's status?
This is an interesting idea and I don't know if it has ever been used on my past projects. Typically, somebody would send a document that said "build this" and we would, no questions asked. I'm wondering what the risks are, if any, of letting your customers have access to the feature list? Do you want to put up your ideas for a super secret project for your customers, and possible competitors, to see?
No comments:
Post a Comment