Agile development inspires a transformation wave in almost all organizations. No agile implementation can be really agile unless (1) testing and continuous QA are considered and applied as key activities, and (2) teams become really one-team mind-shaped.
In this context, two questions repeatedly arise: who test in agile? And, how to organize and perform agile with focus on quality in large organizations, where more than one agile team coexist?
Albert will explain how to address agile testing in large organizations, with more than one agile team, by means of 10 tips for implementing it, with a clear focus on delivering software continuously with quality.
Given that there are different types and levels of testing that need to fit into agile approaches, he will explain which tasks need to be performed by each role and how to organize them, taking into account that agile pushes better time-to-market and quality.
Albert will support his session with a dynamic questions/answers game, in order to consolidate the concepts, best practices and conclusions about the original questions: who and how we test in agile?
After having attended this talk, you’ll gain insights into:
How to adapt the organization, the testing strategy, and the work environment (supported by analytics and AI) in order to support agile testing, by means of 10 tips.
Which roles are needed for ensuring quality in agile?
Who tests in agile?
How to deal with different agile teams in the same organization (“agile of agiles”) with shared objectives, including quality.
How to monitor the evolution of quality in such agile approaches?
Test Leads, Test Managers, QA Managers, Agile / DevOps Transformation Managers, Test Engineers, SCRUM Masters, Product Owners and Agile Team Members
Process models are immense popular in IT and from the right abstraction level they seem to solve ‘every’ problem. A framework (or model) have one thing in common: they are never true because they have a limited reflection of what we hit upon in real live. This is also the case for the Scaled Agile Framework (SAFe).
SAFe provides guide lines how to tackle collaboration within a large organization to deliver valuable software with no concession on quality (?). But how difficult is it to implement SAFe in your organisation: how do you get the collaboration going between (scrum) teams and over different systems.
Ard Kramer had the privilege of working in different organisations where they were struggling with the question: how to create a comfortable and safe level of testing using SAFe within DevOps?
In this master class, Ard will use his experience to share the challenges the organisations faced. These challenges will be analysed by attendees and together with Ard you'll define possible solutions. For example, how to deal with non-representative test environments or if your test automation hasn’t the right level of coverage in DevOps processes and don’t forget the mental factor: how to prepare people around you for a safe environment with focus on value and risk.
Having attended this master class, you'll understand how to scale QA processes within DevOps. You'll learn how to answer questions such as: what will be a safe implementation of the Scaled Agile Framework in a big organisation applying DevOps?
This class is oriented towards QA Managers, Agile / DevOps Transformation Managers, Test Engineers, DevOps Engineers, Product Owners and Agile Team Members
Nowadays, many technology companies, especially in the IT or startups field, focusing on the leading companies in their sector, are choosing to implement the Spotify success model based on concepts such as Squads, Chapters, Guilds or Tribes.
In this master class, Javier Amate and Toni Robres will present a case of success in the implementation of this model, from the point of view of QA.
In this masterclass, Javier and Toni will present the problems that have arisen during the process of implementing the Spotify model, the actions that have been taken and what has been the result.
Specifically, you will see how to avoid duplicate people among Squads, the initial team of 4 people has become one of 20, applying the concepts of flat structure, hybrid QA, independence between Squads and Chapter of QA as a mediator of good practices. They will explain how they have managed to scale this growth through the Guilds concept.
Javier and Toni will also expose how the management of releases has evolved, from making large monthly revisions of 15 days in frozen versions to having the ability to promote at the same time that a feature reaches the Definition of Done.
And finally, as business needs that require closed dates fit into the model, by creating specific Squads to avoid impacting the independence of the rest of Squads.
After attending this master class, you will have seen a case of successful implementation of the Spotify model, how QA has been able to fit in the model and then, going into more detail, how it has managed to sign the necessary people, such as It has been possible to climb without having hierarchies and how deliveries have been managed.
Kubernetes has won the battle of container orchestrators, so more companies are creating and / or adapting their applications to be deployed on this platform. KinD is a tool that helps to easily generate clusters of Kubernetes using Docker containers to easily test different scenarios.
Testing applications designed to be deployed in a Kubernetes cluster, especially those that interact directly with the K8s API (known as Kubernetes operators), implies new challenges and scenarios: how does our application react if a cluster node falls? How do you scale by adding more replicas? How do you interact with the Kubernetes API itself? And with different versions? These and other issues will be discussed in this master class, including practical examples using the KinD tool.
In this masterclass, attendees will get a brief review of Kubernetes basics and will learn how to use the KinD tool to test applications for Kubernetes.
Testers, Developers and IT professional interested in Kubernetes.
Continuous Testing, monitoring the code 24 hours a day
At a time when agility is key to differentiate from the competition, having an automated system defined by pipelines that performs the most relevant tests and ensures proper operation, saves considerable time to be able to make more deployments, in less time, and ensuring the quality.
In this masterclass, Oscar Moreno will teach us how to create a continuous deployment ecosystem defined in a pipeline for a web application.
Oscar will start with continuous integration, where attendees will collect the changes made in the repository in an automated way. Then, the continuous inspection will help attendees to perform code analysis and interface tests that will allow them to detect the most important possible problems before they reach the users. Finally, with continuous deployment, Oscar will show how to deliver our product in the hands of the user and, also being performed based on rules that must be adhered to, Oscar will largely avoid production bugs and delays due to human interaction.
To achieve this, attendees will only use open source tools such as Jenkins, Selenium, Sonarqube, etc ...And to be able to orchestrate all these elements, the key will be the development of a file in Jenkins that allows to direct the operations that Oscar considers appropriate.
Attendees will learn, in a practical way, to define a continuous inspection and deployment pipeline with which to deliver their applications to users more safely and quickly, avoiding bugs and vulnerabilities.
Developers, QA Automation Engineers, QA Managers
Create a robust, solid and scalable continuous delivery agnostic system
Nowadays where we have such a wide range of deploy solutions in the cloud, we run the risk of getting lost in the tools if we don't have a solid base.
In this master class with Xavier Hidalgo, you will see an agnostic system of continuous deploy and how to attach to any cloud if necessary.
Xavi will teach us what to expect from continuous delivery without losing sight of the logical components involved in each step. You will see how concepts are transformed into elements present in our deploy architecture. Xavi, will go down to the minimum necessary, going through the seeds, docker, docker swarm, jenkins (DSL) and the necessary inclusion of automated test systems.
In this master class you will learn:
The elements that make up the continuous delivery in detail and without links to technology.
How to work with the Jenkins DSL to orchestrate continuous delivery, plus some other tools.
How to create a seed of continuous delivery.
How to migrate the project to the cloud as necessary
Testers, Developers and teams that have adopted or want to adopt DevOps practices.
Nowadays setting up, configuring and maintaining a complete pipeline workflow is still a huge challenge and it is normally done by DevOps engineers given it requires a special skills set.
With Testing roles overlapping DevOps (DevTestOps) and being quality a whole team responsibility we need to find some methodologies and instrastructure applications that allow us to build a QA Pipeline that short delivery cycles and bring higher quality software.
In this master class, Fran will talk about how to become an authentic Super Mario and implement the best Pipeline within your team. You choose:
Pipeline: is how a story from a product backlog makes its way through to development, testing and deployment to production.
Pipe dream: is an idea or plan that is impossible or very unlikely to happen.
After the master class, you will learn:
Everything you need to configure a complete Pipeline.
How to include different levels of automatic tests to get a Pipeline focused on quality.
And what is more important, how to do it using the minimum possible time to continue focusing on your application.
To level up in your work by taking the Red Mushroom!
Production testing has always been a taboo, something very badly seen in the software industry, but things are changing, and fast. The increasing complexity that the systems are reaching and the tendency to constantly increase the speed with which we deliver value to users means that many of the practices established when developing and operating software are being questioned.
In this master class, David Lluna will show the current production testing techniques, which allow those who apply them to have much shorter development cycles without sacrificing quality, while maintaining risk control. These techniques also allow building confidence in complex systems where traditional testing practices cannot.
David will teach the main characteristics and phases of testing in production, and will go into detail of some practices, such as traffic shaping, dark launch or testing chaos.
After the master class, you will learn:
How production testing is able to reduce development cycles
The different existing strategies to introduce testing in production
How to use tools like Traefik or Envoy to implement some of the production testing strategies such as shadowing or canarying