Barely Sufficient Software Design: Difference between revisions
From charlesreid1
(Created page with "Link to paper: Barely Sufficient Software Design.pdf =The Ten Practices= # Use issue-tracking software for requirements, features, and bugs # Manage source (beyond the basi...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Link to paper: [[Barely Sufficient Software Design.pdf]] | Link to paper: [[File:Barely Sufficient Software Design.pdf]] | ||
=The Ten Practices= | =The Ten Practices= | ||
Revision as of 20:41, 22 April 2013
Link to paper: File:Barely Sufficient Software Design.pdf
The Ten Practices
- Use issue-tracking software for requirements, features, and bugs
- Manage source (beyond the basics)
- Use mail lists to communicate
- Use checklists for repeated processes
- Create barely-sufficient, source-centric documentation
- Use configuration management tools
- Write tests first, run them often
- Program tough stuff together
- Use a formal release process
- Perform continual process improvement