How to adopt this practice

The following is a list of points you’d need to consider when you adopt this practice.

Process Scope:

• Test coverage: component/feature/(sub)system.
• Review this practice with a focus on its main elements: tasks, artifacts, guidelines.

Team Organization Impact:

• Team composition: the Testers are part of the team, not external resources that are only involved at specific points.
• This practice needs to be adopted also by Developers and make sure that they provide tested components.
• Need for Testers to adopt a more technical skill set. Developers could play the Tester role.

Development Approach Impact:

• Design impact: focus on frequently achieving stable builds that are testable from end-to-end.
• Developers need to focus on providing smaller increments of functionality.
• Institute walkthroughs to determine that a micro-increment is correct.
• Frequent builds and testing throughout an iteration.
• Incorporate a passing automated test as the team’s definition of “done” for a requirement.

On the high end of adoption, you should reach a pattern where the Team continuously develops micro-increments, tests them, and then regression tests the product throughout the day.  Obviously, this involves a high degree of regression test automation.
Achieving this level of automation requires the concerted effort of the whole team across all the levels of testing (automated unit, integration, system, and acceptance tests).