New implementations (of QA code, anyway) are harder. There are a lot of stopping spots that are conceivable. How do you know when to say that you're done with this project? It's inefficient to say that we're going to do the whole thing before we check it in. It's also silly to check in something that flat out doesn't work. We have to chunk our projects just like software chunks functionality into releases.
So, what are our rules of QA project chunking?
- getting something in is more important than getting all the features
- continuing to add is perfectly acceptable
- meet your current goal before you start your future goals
- incomplete is better than not at all