Industry Best Practices

1
Industry Best Practices

• CS2335
• Fall 2001

2
Agenda

• Test next Wed
• Lab 5 being graded
• Lab 6 (Final Project Design) due next Wed 11PM
• Lab 5 (A Solution)
• Best Practices

3
Miniature Milestones

• Problem Im 90 done.
• Technique
• Developers create their own estimate.
• Keep mini (no more than 1-2 days (hours))
• Milestones are 0/1
• Cover all tasks
• Use to cover short-term
• Assess and re-estimate frequently.

4
Change Board

• Problem Uncontrolled changes, lack of
  prioritization on bug fixes, Code/Fix cycle
• Technique
• Create a board of representatives
• Board has authority to accept/reject changes
• Changes are considered before they are made
• Side Effects are considered

5
Daily Smoke and Build Test

• Problem Unsuccessful Integration, low quality,
  poor progress visibility
• Technique
• All code modules turned in frequently.
• Developers keep code in buildable form.
• All interfaces are stubbed out.
• Smoke tests run automatically.
• Dummy code used where necessary.
• Breaking the build usually earns a prize.

6
Incremental Integration

• Problem Code integration fails. Big-bang
  approach frequently used. Excessive schedule
  spent in integration phase.
• Technique
• Use proven integration technique
• Top-down
• Bottom-up
• Hybrid