Submitted by ScottWAmbler on Sun, 2010-09-26 18:04. *
If you insist on force fitting this into a user story, one option to format it would be:
As a end user I expect the system to conform to the X11 standard so that the system is usable to me
That's a bit goofy, seeing as this is really a QoS requirement (assuming that X11 is the Linux standard that you're referring to). On agile teams, QoS requirements are typically:
1. Documented in a separate doc, hopefully as concisely as possible.
2. Considered part of your "done means done" definition for your iteration.
3. Validated through confirmatory testing by the agile development team, and perhaps by an independent test team in the case of complex systems or in regulatory environments.
There are several ways
If you insist on force fitting this into a user story, one option to format it would be:
As a end user I expect the system to conform to the X11 standard so that the system is usable to me
That's a bit goofy, seeing as this is really a QoS requirement (assuming that X11 is the Linux standard that you're referring to). On agile teams, QoS requirements are typically:
1. Documented in a separate doc, hopefully as concisely as possible.
2. Considered part of your "done means done" definition for your iteration.
3. Validated through confirmatory testing by the agile development team, and perhaps by an independent test team in the case of complex systems or in regulatory environments.
- Scott