Difference between revisions of "Category:Quality"

Latest revision as of 09:26, 9 October 2014

Focus on quality, speed will follow.

—W. Edwards Deming

Quality can be quantified, for example, by using planguage. Keep in mind, though, that metric drives behavior.

Quality requirements should be specified in terms of:

Quantifiable, preferably testable, value ranges
Which context and inputs produce distinct outputs
Consideration for typical vs. atypical circumstances
Which particular functional aspects of the system (possibly which user stories), if any, are specifically relevant to that quality
Possible scenarios under which conditions should hold
Priority among them

The following 8 pages are in this category, out of 8 total.

@@ Line 1: / Line 1: @@
 :'''Focus on quality, speed will follow.'''
-::—W. Edwards Deming
+::—{{author|W. Edwards Deming}}
 Quality can be quantified, for example, by using {{p|planguage}}. Keep in mind, though, that {{p|metric drives behavior}}.
-==Pearls and other pages==
-*[[Mission Critical Agile]]
-*{{p|babushka of value}}
-*{{p|refactor code}}
 Quality requirements should be specified in terms of:
@@ Line 19: / Line 13: @@
 ==Sources==
-*SunTone Architecture Methodology
+{{WebSourceListItem
+|url=http://www.infoq.com/articles/create-culture-quality
+|site=InfoQ
+|person=Jonathan Levene
+|title=Creating a Culture of Quality
+}}
+{{WebSourceListItem
+|url=http://www.mountaingoatsoftware.com/blog/what-is-quality
+|site=Mountain Goat Software
+|person=Mike Cohn
+|title=What Is Quality?
+}}
+{{WebSourceListItem
+|url=http://www.infoq.com/interviews/agile2014-hendrickson-quality
+|site=InfoQ
+|person=Shane Hastie
+|title=Elisabeth Hendrickson on Building Quality In
+}}