Peer review, structured walkthrough is more useful than otherwise imagined

I started to believe it is highly beneficial when some form of feature and code walkthrough within the software team is conducted prior to delivery to the test team. This can serve several purposes

- verification of requirements are fulfilled (and subsequent change request raised), as a walkthrough of unit test
- verification of that all possible exceptions on a particular requirement are covered (or as much as possible)
- providing other oversights (in the form of "what if" questions) -- this is particularly useful!
- peer review and learning, and transfer of module knowledge (for either mutual backup or share of production support activities or handover)
- promote sense of sharing responsibility and sharing stress with the main owner of the feature -- important!

This would certainly add workload to the owner of the feature for
- spending effort in organizing the review and walkthrough session to match the organization of requirement

But overall it is able to re-sync wavelength between software team and test team, as well as prevent some possible rework or oversight, and reduce the number of iterations of delivery/re-test at the integration center. Proven.