I am assuming the product owner role during our Scrums and we have just completed our Sprint 0. Now that we have developed a detailed backlog of user stories with acceptance criteria for each story, my question is "what is the best practice" for writing a 'general acceptance criteria' to be added to a contract. For example, site loading speed, search speed, architecture, etc. What do you think would be a 'must' add to any contract.
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
Zigster, as regards site loading speed and search speed, I would add non functional requirements at the user story level. They can be expressed in the form of acceptance criteria. For example if one user story is:
As a customer I want to run a search based on product name So that the products with matching name will be displayed
Among the acceptance criteria you could specify: The search results are displayed to the customer within 3 seconds
In other user stories where for example you might be doing a checkout you will be defining the max time you consider acceptable for the customer to perform such action.
I would not define such acceptance criteria at the site level but at the user story (value) level, this will encourage the development team to build performance tests early and at that specific level.
As per the architecture, what do you mean, do you want to impose a specific architecture?