Room
Room F3 - Track 3: Talks
Audience
Tester, Developer, Manager
Key-Learnings
- Advantages and disadvantages of non-unified, context based development processes
- How to decide if context based processes are right for your team/organization
- Tactics for determining best practices/processes for teams based on the context of the project and team members
- How to get buy in to use different processes across teams
So, what’s your testing process like at *insert company name here*?”. We’ve all been asked this question. It comes up all the time when you tell someone that you work in testing and who you work for. People want to know what your cookie cutter process is for testing at your company; either out of genuine curiosity, a search to find a fit for their skills or to find issues in it that they think you could solve by changing “just one thing”.
What happens when the answer is “we don’t have one.”? In the tech industry things are changing every single day, and every individual has their own skills and experiences that they bring to the table, so why would we have one specific process for our entire organization?
In this talk, we will discuss what it looks like to have a constantly evolving test process within a company, and to have multiple teams within a development org working with different processes and workflows. We will discuss how we all stay on the same track, how we discuss our successes (and our failures), and how we use individual and team strengths to have an organic, and changing process that still keeps us all moving forward and working together.