• info@helpingtesters.com
  • helpingtesters

Top 41 Agile Software Testing Interview Questions

November 1, 2017
Agile, Agile Interview Questions, Agile methodology

Below is the top 41 software testing interview questions on Agile Methodology.

1. Which software development methodology you are using for your organization or project?

To crack the interview, many times candidates bluff and respond that they are using Agile. Depending on your answer, the interviewer will judge your knowledge about Agile and later on candidates are not in a position to answer fundamental questions. It is good to tell truth about current software development methodology adopted in a project or organization. 

2. What is Agile?

Agile is an approach used for Software Development which is iterative and incremental. Agile is basically a set of values and principles that focus on customer satisfaction by continuously delivering values via shippable working software.

3. What do you mean by Agile Manifesto

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

4. Can you explain Agile Principles you are aware of

There are basically 12 agile principles. These are:

  • The customer should be satisfied by delivering the software continuously at regular intervals.
  • Project and people should accept changes in the requirement at any stage of software development
  • The team should deliver working software in a shorter time intervals and continuously.
  • Agile focuses on a collaborative effort of everyone throughout the project including business and scrum team
  • You should motivate, support and trust the team to get your work done.
  • Face-to-face communication is the most efficient way of delivering information within the team.
  • The basic method of measuring a progress of a project is working software.
  • The agile team should work and sustain a constant speed of delivering software.
  • In agile, the better technical excellence is within the team, the better it is for the project.
  • The team should also simply disclose what is not done.
  • The more an agile team is organized, higher is the probability of getting better outputs from them.
  • After a period of time, a mature agile team sets an example of being effective and frames themselves accordingly.

5. Why should an organization adopt Agile methodology OR what are the advantages of Agile methodology

  • Focus on customer
  • Helps in mitigating the risks
  • Agile offers a value-driven approach rather than plan-driven approach
  • Facilitates waste elimination within organizational processes

6. Are there any disadvantages of Agile methodology

  • Requires high level of discipline
  • Continuous involvement of stakeholders is needed
  • Expects working trained people
  • Management may not understand it too well
  • No lengthy documentation

7. How is agile beneficial to testers?

  • Testers’ involvement is from the beginning till end
  • Quality of deliverables is responsibility of entire team, not only of testers
  • Testing is also done by developers, and not only by testers
  • Facilitates early testing of the product in development
  • Implementing changes in requirement or functionality is easier and faster
  • Testers have sufficient time to write test cases and test the application
  • Time and Cost of fixing the defects are reduced to a great extent
  • Improved communication among testers and developers
  • Can’t skip testing while following Agile
  • Testers’ end-to-end knowledge of the application helps improving product quality
  • Can’t skip testing while following Agile
  • Testers’ end-to-end knowledge of the application helps improving product quality

 8. According to you which software development is better from Agile and Waterfall?

  • The interviewer asks this question to test how much knowledge you have for these methodologies. Actually, it depends on many factors viz. client requirement, project feasibility, etc.
  • Explain few advantages and disadvantages of both the software development models
  • Ideal answer should be such that is should not clearly favor one model over another. Candidate should be diplomatic while answering.
  • Finally one can add his personal likings towards Agile.

9. Which scrum ceremonies do you follow in your project?

  • Sprint Planning – on the first day of sprint
  • Daily scrum meeting / Daily stand up meeting – during sprint
  • Sprint Demo – on last day of sprint
  • Sprint Retrospective – on last day of sprint followed by Demo

10. What are the roles in scrum

  • Product Owner – voice of customer
  • Scrum Master
  • Scrum Team

11. How scrum master’s role is different than team leader

  • Scrum Master is a servant leader who is responsible for scheduling sprint ceremonies, removing scrum team’s impediments, shields the team, doesn’t tell team what to do, guides the team
  • Team leader controls the team, assigns tasks to team, takes periodic updates

12. What are the sprint duration and sprint planning duration in scrum

  • Ideally, sprint duration in a scrum is 2 to 4 weeks.
  • If sprint is of 4 weeks, sprint planning should take 1 day
  • If sprint is of 2 weeks, sprint planning should take no more than 0.5 day

13. How does the sprint start in the scrum?

Sprint starts with planning activity on day 1.

14. What is planning poker?

Planning poker is a consensus-based technique for estimating user stories during sprint planning.

15. What is a user story?

A user story is nothing but in scope requirements for a sprint written in simple and easy to understand format

16. Are you aware of the acronym INVEST?

INVEST is an acronym that characterizes a user story.

  • Independent
    • A user story should be independent of the other user stories in a sprint.
  • Negotiable
    • There should be a scope for negotiation in terms of scope, complexity, estimates, etc.
  • Valuable
    • It should provide a business value to customer when delivered
  • Estimate
    • Scrum team should be able to estimate in order to complete it.
  • Small
    • The user story should be sizable enough to get completed within the same sprint only. No roll-over.
  • Testable
    • Scrum team should be able to test the functionality developed as part of the user story

17. How many types of backlogs are there in the scrum?

There are mainly 2 types are the backlog in scrum:

  • Product Backlog: Product backlog contains a list of all the user stories, epics (i.e. group of related user stories) for a product. These user stories are prioritized as per the business needs.
  • Sprint Backlog: Sprint backlog is a prioritized subset of product backlog

18. What are the most common charts prepared in the scrum?

The most common charts in scrum are:

  • Sprint Burndown Chart
    • The sprint burndown chart shows the daily progress of the sprint in terms of how many story points in a sprint are remaining.
  • Release Burnup Chart
    • The release burnup chart shows the work progress against total work planned in a release.

 19. How frequently does release happen in Agile?

As such, there is no specific duration for a release in Agile. This decision depends on Client and business need.

20. What do you discuss in the daily stand-up meeting? How long should it take?

  • Every scrum team member should say only 3 things in the daily stand-up meeting.
    • What did I complete yesterday?
    • What will I do today?
    • What are the impediments in completing my today’s task?
  • The daily stand-up meeting should not take more than 15 mins.

21. What if user stories committed in a sprint are incomplete at the end of the sprint?

  • If entire story is incomplete, it should be moved to next sprint
  • If the partial story is incomplete, after a logical break point, a new story should be created and moved to next sprint. The completed portion should be accepted in the current sprint.

22. What is an ideal size of a scrum team?

It is always good to have 7 members, plus or minus 2 in a scrum team.

23. What is an acceptance criterion?

Acceptance criteria set the basis for a user story to be accepted or not. Testers create and execute tests as per acceptance criteria defined.

24. What is the definition of done?

In simple terms, it is a checklist to accept or reject a piece of work done, be it a user story, sprint, or release.

25. If you are asked to eliminate one scrum ceremony, which one would you like to?

All the four scrum ceremonies have their own importance, and hence none of them should be eliminated.

26. What is scrum?

Scrum is a team-based approach to develop application or product in an environment where requirements are changing rapidly.

27. Name any tool used for Agile Project Management

JIRA, Rally, VersionOne, Agilo

28. Suppose you get a user story on last day of the sprint. Testing can’t be completed in one day. What will you do?

Rather than waiting until last day, tester should highlight it in daily stand-up meeting to all participants well in advance so that necessary actions can be taken to deliver user story in time for testing

29. As a tester, how do you cope up with frequently changing requirements?

  • The tester should understand and highlight the risk or impact of such changes.
  • If possible, don’t automate the test cases until changes are fixed
  • Try to write test cases as generic as possible

30. What is CI?

Continuous Integration is a practice of integrating developers’ code in a shared repository using version control. Check-in of the code is verified using automatic build which ensures latest code availability and detects problems early if any.

31. What is TDD?

Test Driven Development is an approach to writing test cases before development begins. Developers write small and automated test cases and then code for the functionality such that the test cases pass. Later on, they refactor the code to improve performance.

 32. How can automation/performance testing be included in a sprint?

Ideally, during the Nth sprint, automation/performance testing for N-1 sprint should be carried out because stories up to N-1 sprint are developed, tested, and accepted.

33. Has your story point estimation gone wrong any time?

Estimations are bound to go wrong. No one is a perfect estimator. Candidate can give such an example which s/he experienced in past.

34. How does user story estimation and task estimation differ?

The user story is estimated in terms of story points while tasks are estimated in terms of efforts.

35. What is velocity?

Velocity is nothing but a summation of all the estimated story points of in scope user stories in a sprint

36. In sprint demo, who provides a demo for a user story – tester or developer?

Generally, owner of the story demonstrates the user story. However, based on mutual understanding of developer and tester as well as based on functionality within the user story, anyone can demonstrate.

37. What are the qualities required to be a good agile tester?

  • Should know Agile concepts, own roles & responsibilities
  • Should be a good communicator
  • Should have the ability to prioritize testing activities based on requirement.

38. What is a spike?

Sometimes before actually starting any work, some discussion, details or R&D kind of stuff is required. Time taken to do such activities is called spike which is not included in user story estimation.

39. Does exploratory testing help in agile?

Using exploratory testing in agile has advantages and disadvantages:

  • Advantages:
    • Not much preparation is needed
    • Easy to change in case requirement changes
  • Disadvantages:
    • Measuring coverage is not always possible

40. What is a story point?

Story point represents the complexity of the user story. It doesn’t have any relation with no. of man-hours or man-days required to complete the user story.

 41. How is a user story scaled or estimated?

A user story is scaled in any of the following ways:

  • Fibonacci Series (i.e. 0, 1, 2, 3, 5, 8…..)
  • T-shirt Sizing (i.e. XS, S, M, L, XL…)
  • Linear scale (i.e. 1, 2, 3, 4…n)
  • Power of 2 (i.e. 1, 4, 8, 16…)

About the author

Bansi Adhia author

Leave a Reply

Your email address will not be published.