Suppose you are taking notes on the requirements of an app enhancement for software that sells products X1 - X100 on the internet. The marketing people have a laundry list of features that the software should be able to do, but aren't mentioning things like reporting, feature interoperability, or version testing.
In the same way that you scope in the creation of database tables and classes, should you be assuming, scoping, and designing the stats, scripts, and reports for things like conversion rates, page views, popularity calculation, and versioning (or A/B testing)?
Should I (or other team members) be bringing this stuff up during the scoping meetings, just dropping it in the project spec assuming it is wanted, or not doing any of it, assuming that the marketing team knows the feature set they want, and is leaving these things out on purpose?
If I should be bringing it up during scoping meetings, what is the list of things that I should bring up for inclusion in the project spec, each time we do a project.
The list I have so far is:
- SEO design review
- A/B display version testing
- popularity reporting
- page view/conversion rate reporting
- RSS/XML feed capabilities
- feature compatibility (i.e. discounting - if a particular product should be able to have a 10% discount, should a bundle of products also be capable of having a discount)