Difference between revisions of "Mission Critical Agile"

From Pearl Language
Jump to navigation Jump to search
(Set a {{p|bug count ceiling}} and {{p|technical debt ceiling}} and make them come down.)
(Added sources.)
Line 11: Line 11:
*{{p|continuous integration}}
*{{p|continuous integration}}
*{{p|continuous deployment}}
*{{p|continuous deployment}}
*{{p|acceptance test-driven development}}
*{{p|acceptance test-driven development}} using Gherkin language to specify acceptance criteria that can be tested automatically.
*{{p|vibrant persona}}s
*{{p|vibrant persona}}s
*{{p|persona team}}s
*{{p|persona team}}s
Line 35: Line 35:
*Aim for {{p|low defect density}}, defined as the number of SIT (System Integration and Test) found defects per KLOC.
*Aim for {{p|low defect density}}, defined as the number of SIT (System Integration and Test) found defects per KLOC.
*Set a {{p|bug count ceiling}} and {{p|technical debt ceiling}} and make them come down.
*Set a {{p|bug count ceiling}} and {{p|technical debt ceiling}} and make them come down.
*Define {{p|criticality class governs rigour}} (see http://artisansoftwareconsulting.com/blogs/?tag=agile-development)




Line 40: Line 41:
*http://www.tem-sw.com/library/XP%20for%20Large%20System%20Mission%20Critical.pdf
*http://www.tem-sw.com/library/XP%20for%20Large%20System%20Mission%20Critical.pdf
*see sources at {{p|broccoli planning}}
*see sources at {{p|broccoli planning}}
*http://www.niwotridge.com/PDFs/ADC%20Final.pdf
*http://arxiv.org/pdf/cs/0701010.pdf
*http://artisansoftwareconsulting.com/blogs/?tag=agile-development
*http://www.agilejournal.com/articles/columns/case-studies/313-case-study-war-stories-fighter-jets-and-agile-development-at-lockheed-martin
*http://www.agilejournal.com/articles/columns/case-studies


==Other pearls==
==Other pearls==
*{{p|yesterday's weather}}
*{{p|yesterday's weather}}

Revision as of 14:09, 29 February 2012

Adopting agile practices for mission critical systems, creating a “insurance policy”:


Sources

Other pearls