Share this:

CISQ Tweetup

June 25, 2013

Does Agile Stink at Nonfunctional Requirements?


Join the Tweetup on June 25th at 11-00 AM EDT to discuss/debate the following proposition.




Whereas, Agile Methods eschew formal reviews and inspections which have traditionally been a focus for detecting non-functional defects in the architecture and design of software applications even if they are emergent, and


Whereas, the stories used to guide Agile development are stated primarily in functional rather than non-functional terms, and


Whereas, Agile quality strategies such as Test Driven Development and regression suites are developed primarily from these functional stories, and


Whereas, the backlog of stories focused on remediating technical debt, which is primarily composed of non-functional problems, grows stale from remaining unaddressed because of higher priorities given to new features and enhancements requested by the customer, therefore


Be it resolved that Agile Methods stink at managing non-functional requirements because of the accumulating odors from unaddressed non-functional code smells.


Please join in the dialogue regardless of your position! Do you agree/disagree with these assumptions? What is your experience with non-functional requirements? Tweets with clever ways to manage non-functional challenges are especially invited. The community knows the answers, the dialogue extracts them!


To download the tweetup transcript visit CISQ Member Page.

One thought on “CISQ Tweetup

  1. My experience leaves me with a different taste. I find that the Agile project teams that I work with welcome the notion that non-functional work is now recognized by SNAP and that their teams are now quantitatively justified in requesting certain work hours that they were not quantitatively justified in claiming before.

    If stories are not including non-functional requirementes, that really means to me that more training on the new SNAP metric is needed.

Leave a Reply

Your email address will not be published. Required fields are marked *



Comment validation by @