Q #1) What is Agile Testing?

Answer: Agile Testing is a practice that QA follows in a dynamic environment where testing requirements
keep changing according to customer needs. This is done in parallel to the development activity where
the testing team receives frequent small codes from the development team for testing.

Q #2) What is the difference between burn-up and burn-down charts?

Answer: Burn-up and burn-down charts are used to keep track of the progress of the project.

Burn-up charts represent how much work has been completed in any project whereas Burn-down chart
represents the remaining work in a project.

Q #3) Define the roles in Scrum?

Answer:

There are three main roles that a Scrum team has:

Project Owner is responsible for managing the product backlog. Works with end-users and customers
and provides proper requirements to the team to build the proper product.

Scrum Master works with the scrum team to make sure each sprint gets completed on time. Scrum
master ensures proper workflow for the team.

Scrum Team: Each member of the team should be self-organized, dedicated and responsible for the high
quality of the work.

Q #4) What is Product Backlog & Sprint Backlog?

Answer: Product backlog is maintained by the project owner which contains every feature and
requirement of the product.

Sprint backlogs can be treated as a subset of product backlogs that contain features and requirements
related to that particular sprint only.
Q #5) Explain Velocity in Agile.

Answer: Velocity is a metric that is calculated by the addition of all effort estimates associated with user
stories completed in an iteration. It predicts how much work Agile can complete in a sprint and how
much time it will require to complete a project.

Q #6) Explain the difference between a traditional Waterfall model and Agile testing?

Answer: Agile testing is done in parallel to the development activity whereas a traditional waterfall
model testing is done at the end of the development.

As done in parallel, agile testing is done on small features whereas, in a waterfall model, testing is
performed on the whole application.

Q #7) Explain Pair Programming and its benefits?

Answer: Pair programming is a technique in which two programmers work as a team in which one
programmer writes code and other one reviews that code. They can both switch roles.

Benefits:

Improved code quality: As the second partner reviews the code simultaneously, it reduces the chances of
mistake.

Knowledge transfer is easy: One experienced partner can teach another partner about the techniques
and codes.

Q #8) What is Re-factoring?

Answer: Modification of the code without changing its functionality to improve the performance is called
Re-factoring.
Q #9) Explain the Iterative and Incremental Development in Agile?

Answer:

Iterative Development: Software is developed and delivered to the customer and based on the feedback
again developed in cycles or releases and sprints. Example: Release 1 software is developed in 5 sprints
and delivered to the customer. Now, the customer wants some changes, then the development team
plan for 2nd release which can be completed in some sprints and so on.

Incremental Development: Software is developed in parts or increments. In each increment, a portion of

the complete requirement is delivered.

Q #10) How do you deal when requirements change frequently?

Answer: This question is to test the analytical capability of the candidate.

The answer can be: Work with PO to understand the exact requirement to update test cases. Also,
understand the risk of changing the requirements. Apart from this, one should be able to write a generic
test plan and test cases. Don’t go for the automation until requirements are finalized.

Q #11) What is a test stub?

Answer: The test stub is a small code that mimics a specific component in the system and can replace it.
The output is the same as the component it replaces.

Q #12) What qualities should a good Agile tester have?

Answer:

He should be able to understand the requirements quickly.

He should know Agile concepts and principals.

As requirements keep changing, he should understand the risk involved in it.

The agile tester should be able to prioritize the work based on the requirements.

Communication is a must for an Agile tester as it requires a lot of communication with developers and
business associates.

Q #13) What is the difference between Epic, User stories & Tasks?

Answer:

User Stories: It defines the actual business requirements. It is generally created by the business owner.

Task: To accomplish the business requirements, the development team creates tasks.

Epic: A group of related user stories is called an Epic.

Q #14) What is a Taskboard in Agile?

Answer: Taskboard is a dashboard that shows the progress of the project.

It contains:

User Story: It has the actual business requirements.

To Do: Tasks that can be worked on.

In Progress: Tasks in progress.

To Verify: Tasks pending for verification or testing

Done: Completed tasks.

Q #15) What is Test Driven Development (TDD)?

Answer: It is a Test-first development technique in which we add a test first before we write the
complete production code. Next, we run the test and based on the result refactor the code to fulfill the
test requirement.

Q #16) How can QA add value to an agile team?

Answer: QA can provide value addition by thinking outside the box about the various scenarios to test a
story. They can provide quick feedback to the developers about whether new functionality is working
fine or not.

Q #17) What is Scrum ban?

Answer: It is a software development model that is a combination of Scrum and Kanban. Scrumban is
considered for maintaining projects in which there are frequent changes or unexpected user stories. This
can reduce the minimum completion time for user stories.

Q #18) What is the Application Binary Interface?

Answer: Application Binary Interface or ABI is defined as an interface for complied application programs
or we can say it describes the low-level interface between an application and the operating system.

Q #19) What is the Zero sprint in Agile?

Answer: It can be defined as a pre-preparation step to the first sprint. Activities like setting development
environment, preparing backlogs, etc. need to be done before starting the first sprint and can be treated
as Sprint zero.

Q #20) What is Spike?

Answer: There may be some technical issues or design problem in the project which needs to be
resolved first. To provide a solution to this problem “Spikes” are created.

Spikes are of two types- Functional and Technical.

Q #21) Name some Agile quality strategies.

Answer: Some Agile quality strategies are-

Re-factoring

Small feedback cycles

Dynamic code analysis

Iteration

Q #22) What is the importance of daily stand up meetings?

Answer: Daily stand up meetings are essential for any team in which the team discusses,

How much work has been completed?

What are the plans to resolve technical issues?

What steps need to be done to complete the projects etc.?

Q #23) What is a tracer bullet?

Answer: It can be defined as a spike with the current architecture or the current set of best practices.
The purpose of a tracer bullet is to examine how an end-to-end process will work and examine feasibility.

Q #24) How is the velocity of the sprint measured?

Answer: If capacity is measured as a percentage of a 40 hour week then, completed story points * team
capacity

If capacity is measured in man-hours then Completed story points/team capacity