Barely Sufficient Software Design
From charlesreid1
Link to paper: 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