Tech Culture: Teams, Tribes and Pirates
Welcome to this biology post, because in a high-level, I’m going to share part of our Agile DNA. We will cover 3 ways we interact with other Tech colleagues:
Our Scrum Master are going to explain this information in other post but Teams at Ebury are responsible of few microservices (API, Faster Payment, SEPA, Website …) or a larger application (Back Office System, Salesforce, Ebury Online…). These cross-functional groups from 4 to 8 people are aligned with the business roadmap and goals for the next few months.
Our teams are cross functional and fully responsible for the quality of the product they produce. We apply an end-to-end philosophy to our daily work, that is, we are responsible from user story creation through to ensuring that story is delivered, working and supported in production. Every team member will be involved in supporting the QA process.
With this in mind, what can we expect from the QA tribe? Why are QAs still important? If we have great developers that use automated tools to check their workflows, are focused on increasing the quality of their daily work and the company is aligned with a quality-first philosophy, then why do we need dedicated testers?