Here are some of the thoughts from the workshop:

• Non-functional requirements can be treated as separate streams (to functional requirements).
• Non-functional requirements can be captured as user stories.
• Do not talk about -ilities. Write failing tests.
• Tests for non-functional requirements are much harder to write and execute than tests for user stories.
• Create a staging environment on the production servers for system testing.
• Non-functional requirements are orthogonal to user stories.
• Dialog about non-functional requirements extends beyond the planning game.
• Velocity can be a measure of maintainability.
• Should customers talk about maintainability?
• Is maintainability a genuine non-functional requirement?
• Non-functional requirements change over time too.

For a personal account of the workshop, see my blog: [1].

The slides are also available: [u1].