Skip to main content

How I cleared ISTQB Agile Extension Certification?

In this post I am going to share my experience and preparation for ISTQB Agile Foundation Level exam. The pre-requisite for this exam is ISTQB Foundation Level Certificate. This is an extension exam since it deals with only Agile development.

Who is eligible for this exam?
Every Tester who has ISTQB foundation level certificate is eligible. If you are planning to work in an agile environment or your current job demands so then you must go for this certificate since it will give you a basic idea of how Agile development works.

What you will learn from the certification?
After completing the certification, you will be able to understand how testing is a crucial part in agile. Role of a tester, how as a tester you can make a difference. Difference between Agile and Traditional methods. You will also learn about agile values and principles, continuous integration, planning, Kanban, XP and scrum methods.

What is the exam structure?
Exam consists of total 40 questions with multiple choice answers. You get 60 mins to complete all 40 questions. If you complete your exam earlier then you can utilize remaining of the time to review your answers.

What are pass % and Is there any negative marking?
In order to pass the exam, you should get minimum 65% or 26 questions right. There are no negative marking for wrong answers (Thank God!)

How to prepare for the exam?
ISTQB Agile Extension Syllabus is the main resource to prepare. It has around 3 chapters (40ish pages) and all of them are theory based. I read the syllabus once and then revised all the main points like 6-7 times before appearing for the exam. I also solved the sample questions given on the ISTQB official website and online mock tests.

Where would I find all the resources?
Here is the link to download all the needed resources click here.

How to register for the exam?
You need to register on ISTQB website. They need to check your ISTQB foundation level certificate number prior to send you the confirmation for this exam. Please visit the website for the detailed instructions since this can vary depending on what part of the world you are in.

I wouldn't say exam was on the easy side. Some questions were difficult and some were fine. Few were direct questions and few required to apply my gained knowledge on the topic. If you prepare from the syllabus and read it multiple times, exam would be easier to get through. I didn't refer any book but ISTQB website has recommendations if you are planning to dig deeper into the topic. There are training available as well.

Hope you found this post helpful. If you have any questions, please feel free to comment below.

Comments

Popular posts from this blog

Remove Blanks from Excel Sheet when Excel doesn't recognize field as blank

This is one of the tricks which always helped me in removing the blank fields from an Excel sheet especially when the values are copied from other sources. I have added screenshots of a sample data to show you all the actions step by step. Here are the steps to remove blanks by using one of the special functions in excel: 1. Select your data-set (Select the column which has blank values) 2. Press F5 3. Select "Special". You will see below screen: 4.Select Blanks and click Ok as shown 5. All the blank fields are now selected, you can proceed and delete all of them by selecting "delete" from the home menu.   Here is the final result: I hope this was helpful. Share this with your colleagues and friends to help them out.

The Agile Manifesto Values and Principles

Agile manifesto refers to the set of rules or values used in an agile project. It contains mainly 4 values: Individual and Interactions Working software Customer collaboration Responding to change Over (in traditional project): Processes and Tools Comprehensive documentation Contract negotiation Following a plan Let's discuss these four values in details: Individual and Interactions : Agile development follows a whole team approach and is very people centered. Development team builds software through communication and interaction among different teams and people instead of depending on tools and processes. Individual team member offers a specific skill set and whole team involves in planning the development and testing strategies.  Working software : It is always beneficial to see the working software instead of heavy documentation. It also helps developers in getting early feedback from the clients which in turn cuts down the cost of accommodating c...

How to write a detailed Bug report?

Welcome to Software Testing Techie Blog! Bug report sounds familiar, right? As testers, we all create one or more than one bug report in our everyday work but what mostly matters is how detailed do we create them? What details we put in and how other teams get benefit out of it. BUG!! I am going to share an example related to detailed bug report and how it affects the quality. Detailed bug report is one of the best gift you can give to your and also to development team. Let's see how: A detailed bug report should have 4 major things namely severity, steps to reproduce, expected result and actual result. There could be other fields depending on what defect tracking tool you are using for example, testing estimate, test cases reviewer etc. Consider an easy example where user logs into a website and found that home screen is distorted. So Let's define all above 4 major areas: 1. Severity: Since it is related to Home screen which is the most important part of ...