Shared bookmarks for del.icio.us user Synesthesia on 2009-11-05:
- Non-functional Requirements as User Stories on Agile Projects
Mike Cohn article suggesting that using the standard “As a <type of user>, I want <some goal>, so that <some reason>” user story template is a useful way to capture non-functional requirements and system constraints.
Good discussion in the comments about whether these should sit in the backlog or be held as ongoing cross-cutting items.
agile requirements non-functional_requirements - Complex Requirements On an Agile Project
Scott Ambler on strategies for handling the complexities of large real-world systems through agile:
- look ahead in the backlog for complex items coming soon – pre-model
- recognise where usable lumps of functionality rely on several work items at different points in the backlog
- recognise where usable lumps of functionality rely on several work items in the backlogs of several teams
agile requirements - Beyond Functional Requirements On Agile Projects
Scott Ambler on addressing non-functional requirements / constraints on agile projects:
– identify in requirements envisioning and formulate technical strategy in architectural envisioning (Iteration 0)
- explore JIT during contruction
-validate with parallel independent investigative testing
- train developers to understand the issues
agile non-functional_requirements requirements
