INTERVIEW QUESTION:

How are non-functional requirements defined and managed on Agile projects?


Non-functional requirements (NFRs) are typically defined as backlog constraints on an Agile project, and are managed as part of both product backlog and scrum backlog. They are revisited as part of the ‘Definition of Done’ for each iteration or sprint. If the system does not meet any given NFR, that NFR may spawn new backlog items such as refactors or performance enhancements.

Well-defined NFRs should meet the following criteria:

--
Sandy Lambert
Business Architect
LinkedIn Profile


posted @ Friday, May 9, 2014 11:02 AM by Chris Adams