Testing is not an isolated activity. It interacts with and influences other disciplines in software development such as design, coding, release management, and deployment. As testers, our skills and experiences add value far beyond the immediate context of verifying functionality. Threats to value other than software errors exist.
Yet our discussions are often constrained to the testing space, omitting the connections to, and dependencies on, other roles and activities. Testing is an integral discipline of software development, and often plays an active and important role in bridging gaps between technical and business-focused roles, between leaders and engineers, and between makers and users.
How does the testing piece fit into the software development puzzle? How does – and how should – testing interact with other disciplines in software development? How can we most effectively add value to the software development projects we participate in?
Please join us for our 11th annual conference at the Simon Fraser University Harbour Centre campus in downtown Vancouver, Canada, August 8-10 2016.
IMPORTANT NOTE: Creating a profile on this site does not constitute registering to attend the conference. If you would like to attend and have not yet registered, please Learn More »
Some days it appears as if the entire software world is deciding to “go agile”, usually without tester input. To those uninvolved in the decision agile becomes simply a moniker for change and as a result of this testers often view the approaching transition with trepidation, if not abject horror.
In this session, Mike Hrycyk will explore 17 reasons why agile makes a tester’s project, success factors, even life, better. From the pragmatic to the humorous, Mike will familiarize and humanize agile, relating it to what we already know and are comfortable with to help demonstrate that the change agile brings is really just a refocusing on what we already know works.
Some of the reasons include: Test involvement in early requirements discussions isn’t by chance anymore it’s a necessity; with two week sprints, Test can’t receive builds more than 10 days late; and of course – agile meeting toys.