Difference between revisions of "Mission Critical Agile"

From Pearl Language
Jump to navigation Jump to search
(Yesrterday's Weather)
(using an ordered {{p|refactoring wish list}})
Line 18: Line 18:
*{{p|gilb p-language}}
*{{p|gilb p-language}}
*{{p|behavior-driven development}}
*{{p|behavior-driven development}}
*{{p|slash the code base}} and {{p|prune any code}}—smaller code bases are easier to grasp, contain less bugs; continuously {{p|refactor code}}.
*{{p|slash the code base}} and {{p|prune any code}}—smaller code bases are easier to grasp, contain less bugs; continuously {{p|refactor code}} using an ordered {{p|refactoring wish list}}.
*{{p|stable teams}}
*{{p|stable teams}}
*{{p|elegant design}}—simplicity, efficiency, consistency, completeness, coherence
*{{p|elegant design}}—simplicity, efficiency, consistency, completeness, coherence

Revision as of 13:43, 29 February 2012

Adopting agile practices for mission critical systems:

Sources

Other pearls