Abstract: Test-First is a larger umbrella than many think. It ranges from more than Acceptance Test-Driven Development and Unit Testing. Done properly, it starts with product management and goes through value realization. This talk will not discuss all of test-first but will center on how Test-First affects the developer – from a requirements point of view to development to release. It will discuss how test-first with the product owner sets the stage for good design as a side-affect of getting clarity on requirements. This “side-effect” is something called out in design patterns, but not often discussed. The talk will also discuss on how the use of test-first needs to focus on value realization, not merely writing the code. The talk concludes by discussing the relationship of developers to ops and other post-production roles in the organization.
Learning Outcomes: - how test-first is useful virtually throughout the value stream
- how design patterns espouse a test-first mind set
- the relationship between the code quality of "testability" relates to quality design
