What should be in a user story?
- A need
- A reason
- Implementation notes
- A user
Click to show the answer
1 & 2 & 4: User stories should be independent of any possible implementation, but should contain a user, a need, and the reason the user has that need.
Validation is checking that the code...
- Correctly implements an interface
- Corresponds to what users want
- Corresponds to a user story
- Can be mathematically proved correct
Click to show the answer
2: It's about the "end-to-end" task of checking with users, not with what we think users want such as user stories or interfaces, and it is by definition not a formal process since it involves humans and subjectivity.
Which of the following are requirements?
- A specific feature
- A level of security set by law
- A choice of programming language
- Usability for the hard of hearing
Click to show the answer
1 & 2 & 4: aside from the programming language, which is an implementation detail, these are all good examples of requirements.
Internationalization involves...
- Adapting to regional sensitivities
- Validating the user interface around the world
- Avoiding cultural blunders
- Using proper currency symbols
Click to show the answer
All of the above, and more!
A user story must...
- Not be too large
- Be specified like a contract
- Have a clear definition of the result
- Refer to previous user stories
Click to show the answer
1 & 3: it should be a high-level story rather than lengthy implementation details, and it must clearly state what users want. However, user stories are not formal, and they must be self-contained.