1. History of DevOps and Why it’s actually called DevOps
2. Three principles of DevOps: Flow, Feedback and Continuous learning
3. How Testers fit into a DevOps team

Jitesh has over 14 years Test experience working with a wide variety of companies from Mobile manufactures to OS builders and app developers. He is currently working with the Mobile Platforms team within the BBC to help identify their Test approaches and how the teams move to DevOps and beyond.

There is a lot of talk about DevOps recently, the tools used and how it will help your teams move faster.

Terms like CI, CD, infrastructure as code, automation at every level of development and even DevSecCon – more security focused developer and operations collaboration

It almost sounds like once you’re “DevOps-ing”, your teams will magically move faster than ever before and that it only involves Developer and Operations. It is called DevOps after all!

So what does everyone not in Dev and Ops do?

For Testers the DevOps movement appears to replace them with automation and other tools based feedback loops. And you’d be right to wonder why you would need Testers when you can do it without them?

I’m here to tell you that Testers are still going to be needed in a DevOps world but the work we’ve traditionally done is about to drastically change. For the better.

It’s not just about the tools, it’s so much more than that. It’s how you fundamentally work as a team and more importantly as an organisation. DevOps is pulling together all the different threads in what we call agile into a more coherent way for teams to work

In this talk I’ll go into the brief history of DevOps (and why it’s called DevOps), what it actually means, why it’s more than just tooling and why Testers are needed in a DevOps culture.