3 Courses for Success!

AU - Certified Practitioner in Agile Testing (CPAT)

AU - Certified Specialist in Agile Testing (CSAT)

AU - Capturing Agile Requirements by Example (CARE)

Syllabus coming February 2022
adult-brainstorming-business-1181622 (1)

Training

Get prepared to become a CPAT, CSAT or CARE.

IMG_1249.jpg

Certification Exam

Get AU-CPAT, AU-CSAT or AU-CARE certified via Brightest!

gettyimages-157282209-612x612.jpg

Accreditation Support

We will be happy to support you becoming AU recognized.

Agile United - Certified Practitioner in Agile Testing  (AU-CPAT) 

Agile United - Certified Practitioner in Agile Testing (AU-CPAT) has been designed for Agile team members, and testers in particular, who are looking to improve their knowledge, people skills, Agile skills, testing skills and technology skills by taking this hands-on and interactive training course. This training will help you and your team develop better software by teaching you about testing and quality. We will cover learning objectives that may surprise you, such as teaching you interactively about mental models and critical thinking, we will also help you do highly effective risk analysis with modern tools, and we will implement hands-on exploratory testing with real software and hardware that runs throughout the training.

Day One

To kick-start the course, we will briefly explore what Agile is, what it means to be Agile and what an Agile way of working means. We will also dive into the challenges that teams face which lead to quality related issues. We understand the importance of mental models, critical thinking skills and beneficial questioning.

During the second half of day one, we will introduce a product which we will work with during the whole training. We will learn about the product by play, exploration and making several models to help us think about risks and the best strategy to use to test the product.

By the end of day one, you will be able to:

  • Describe the concepts of Agile and how they affect software development

  • Explain how testing and quality fit in an Agile way of working (using Scrum)

  • Explain what Agile means for the skills of a tester

  • Talk about testing in an Agile context

  • Describe what models are

  • Explain how models benefit and enact thinking and talking about testing and quality

  • Create different types of models using the heuristic test strategy model

  • Create models with mind maps

  • Describe what risks are

  • Apply different techniques for discovering risks, such as horror plots, the headline game & risk storming

  • Hypothesise and construct different types of risks that might affect a product or project

  • Construct testing activities from risks

  • Explain what a test strategy is

  • Talk about the parts of a test strategy

  • Build and expand a test strategy fast

  • Ask efficient questions to learn about the product, the context and

  • Identify situations where ambiguity is slowing us down.

Day Two

At the beginning of day two, we will do actual testing on the product, based on the risk analysis and test strategy made on day one. While testing, we will further expand our strategy and risk models. We will learn how to construct and expand testing activities and learn how to document your testing as lean as possible while still being useful.

During the second part of the day, we will move on to the topic of collaboration and communication within an Agile team. We will explore refinement and sprint planning to learn how a tester can add maximum value in a variety of situations.

By the end of day two, you will be able to:

  • Explain what session-based testing is

  • Create charters for sessions to learn about the product and test it

  • Document what you learn using a variety of approaches

  • Explain why note-taking is important

  • Take efficient and concise notes

  • Explain the basics of critical thinking

  • Explain why critical thinking is important in software development

  • Identify claims, conclusions and reasoning in your own thinking

  • Identify cognitive biases, false reasons and logical fallacies

  • Describe different software development activities and zoom in on communication and collaboration from a quality and testing perspective

  • Discuss some of the challenges surrounding communication and how to overcome them

  • Explain the role of testing and quality in Scrum ceremonies

  • Review user stories

  • Identify challenges in your team using user stories

  • Explain the benefits of splitting user stories in smaller parts from a quality perspective

 

Day Three

During the first part of day three, we will do some more testing on the product in sessions. We will learn how to explain the status of the product, what we did and the remaining risks using the testing story.

We will later dive deeper into the topics of collaboration and communication in an Agile team, using retrospectives and Sprint reviews.

 

Finally, we will discuss how tooling can help accelerate teams' work.

By the end of day three, you will be able to:

  • Explain how to report your testing, using a variety of approaches in and outside of scrum ceremonies

  • Give your stakeholders insight into the testing and quality of the product

  • Use the basics of storytelling in your daily work

  • Explain what feedback is

  • Provide feedback in an effective way, using different approaches

  • Explain the purpose and benefits of a retrospective

  • Facilitate basic retrospectives to help accelerate the team performance by removing waste and reflect on the way of working

  • Explain how tooling can accelerate teams' performance

  • Guide your team to talk about testability and the appropriate use of automation and tooling

  • Talk to your stakeholders about the benefits and traps of using automation

  • Explain what quality coaching is and how teams benefit from it

  • Explain how professional Agile testers add value in a variety of ways, depending on the context you are in

Prerequisites:

Although there aren't any mandatory prerequisites, you will get a lot more from the course if you already hold the ISTQB Certified Tester Foundation Level (CTFL) & ISTQB CTFL-Agile Tester (CTFL-AT) Certificates — as this course will not cover the fundamentals and terminology of Testing and Agile.

Other recommendations are that you hold another Agile or Scrum certificate, such as PSM or CSM or ASF or at least reading through the Scrum guide. Please refer to the syllabus for more ideas and literature  recommendations. 

Agile United - Certified Specialist in Agile Testing  (AU-CSAT) 

The Certified Specialist in Agile Testing (AU-CSAT) training has been developed for agile team members, and specifically testers, who want to deepen their knowledge even further in the field of personal skills, team skills and testing skills. This practical and interactive training helps you and your team to deliver faster and better quality software by teaching you the more complex tricks of the trade of testing and quality improvement. As a logical follow-up to the AU-CPAT training, we now discuss topics such as leadership, negotiation, biases, visual improvement, probability, but also bug hunting and we go deeper into the power of exploratory testing and the complexity of risks and risk assessment. Do you want to be the specialist in the field of quality within your organization or team and really help your team(s) a step further by delivering better software? Then this course is for you.

Day One

On the first day, you and your new colleagues form a team that, as a consultancy unit, will help a fictitious customer with the launch of a new product. To immediately look good, there is a boost in your visual presentation skills. After you hear the customer's story, the team is asked to develop an approach to the problems. The logical consequence of this is the first part of our comprehensive approach to risk, or better yet, potential harm, and how to manage it.​ ​

 

At the end of the first day you are able to:

  • tell your colleagues in a compact way what you bring, what the best conditions are for you to work in, and what absolutely does not work for you

  • Have you realized together with fellow students the first foundation of a team by recording team values ​​and working agreements.

  • Do you know a number of methods that enable you to visualize different parts of your work (a static situation, progress, or a process) in clear ways.

  • Can you use visualization for at least your testing strategy, system status, improvement cycle and experimentation

  • Do you know how to perform a potential damage analysis (PDA) (with new tooling) and monitor it

  • Have you become aware of a number of often unknown pitfalls.

Day Two

On the second day you will be initiated into the world of negotiation. You understand the pitfalls of negotiation, and you practice negotiating a way of negotiating that will enable you to better take care of your unique concerns and wishes that you simply have as a test analyst within a team. We will also look in more detail at potential damage. Where on day 1 we looked at risks that we are familiar with, on day 2 we enter new territory: what do you do with hazards that you are not aware of? You will then be introduced to the product to be launched by your virtual customer, and you will be taught how to conduct a bug hunt, after which you also organize and execute it immediately. Finally, you will learn that exploratory testing has a number of dimensions, which you can use to give your testing activities more depth and structure when you are exploring. You will also get started with that right away. ​

 

At the end of day two:

  • You know what positional negotiation is.

  • You know what principled negotiation is and you are able to conduct such a  negotiation.

  • Do you know what to look out for and what the mindset is for those parts of the software that are not yet available at all.

  • Do you know what a bug hunt is and when you can use it.

  • Can you explain the value of a bug hunt to your team or within your organization.

  • Do you know how a bug hunt works and can you organize bug hunts.

  • Are you familiar with some dimensions of exploratory testing

  • Do you know how to use those dimensions in your performance

Day Three

On the last day we will go deeper into the skill 'negotiation'. Here you will learn new ways of negotiating in order to effectively achieve a win-win situation for everyone, with the timely delivery of quality software in mind. You will also be initiated into the world of biases through illuminating examples. You will learn the different types of biases, how to recognize biases and how to arm yourself against them. Finally, we discuss the fundamentals of leadership, with an emphasis on how you can help to create an effective and enthusiastic team.

 

At the end of day three:

  • Do you have knowledge of the most modern negotiation techniques

  • Can you apply situational negotiation methods

  • Have you practiced with different approaches in negotiation

  • Do you know what a bias is

  • Can you distinguish the different types of biases

  • Are you able to recognize biases in both others and yourself

  • Do you know the influence of psychological safety and accountability on a team and you know the frameworks of a highly motivated team

  • Can you explain how leadership contributes to a stronger team

  • Do you know the building blocks with which you can make a substantial contribution to the effectiveness and efficiency of your team

Prerequisites:

Although there are no mandatory requirements, you must master all concepts from the AU-CPAT training to be able to follow this training. Extensive experience with working in an agile environment is also strongly recommended.

How can Agile United support you?