Testers often struggle with estimating and planning testing in agile development, enhancement and maintenance projects. Agile, which promises cross-functional teams and test driven development, has often been implemented using the historical functional silos. This has lead testers to estimate and plan to test separately. However, the size and complexity of user stories and releases are critical inputs into planning any slice of work. This presentation will provide examples of using size to plan how much testing work can be done in an iteration, how many test cases are required for user stories and releases, and how size can be used to help define and monitor when work is “done.” The discussion will include story points, function points and using size in test first techniques (TDD, ATDD, and BDD). Join Tom to get a grasp on the testing effort required using size as the parameter.