New: SQA in an easy-to-swallow pill!!!

Congratulations. Dave implemented your ideas and there has been improvement. The group has changed their standard development schedule:
- they do not start design until requirements are finished
- they now review the requirements for completeness, consistency, etc.
- they also conduct reviews of the design before coding
- they now have an elementary error reporting system

The next two projects saw only modest improvements in both shorter project duration and fewer bugs in the delivered product. But, the third project was completed in only 11 weeks and the number of bugs was about 30% less than normal. Most importantly, the team generally agrees that the extra SQA work is not too terrible.

So, it appears that your SQA ideas are beginning to yield fruit. In fact, The Big Boss is impressed. He would like to see a little more improvement. He has asked Dave to present an enhanced SQA Plan including cost estimates. Naturally, Dave has delegated this task to you.

What should be the next two or three steps to better SQA?