Agile interview questions

Top Agile Methodology Interview Questions You Must Prepare

Last updated on

Nowadays, agile is a widely used methodology in software management and there is a high demand for scrum masters, developers, testers in agile projects. In this article, we have compiled a list of top Agile interview questions.

Agile Interview Questions

Ques.1. What is Agile methodology?
Ans. Agile methodology is used in software development. It focuses on incremental development methods where the objective of the methodology is to quickly deliver the product. 

Ques.2. How is agile methodology different from traditional methodologies?
Ans. The main difference between agile methodology and other traditional methodologies is that agile methodology follows an incremental development model whereas traditional methodologies follow a sequential model.

In agile methodology, the development phase and testing phase run simultaneously. In traditional methodology, the testing phase starts once the development phase is over.

The agile methodology provides flexibility as introducing changes is easier. In traditional methodology, incorporating changes is difficult as before the development work starts, requirements are frozen.

The agile methodology needs less documentation. Due to quick delivery, developers make the changes in the code based on the need. While in traditional methodology, the development process starts only after the completed documented requirements are available with the team.

Customers are involved in every stage of the agile software life cycle, reviewing the product and suggesting changes if required. In traditional methodology, customers are mainly involved in the requirements gathering phase. They usually see the finished product during the last stages of the development life cycle.

Ques.3. Can you name some agile frameworks?
Ans. The following are some agile frameworks:

  • Scrum
  • Crystal
  • Dynamic Systems Development Method (DSDM)
  • Feature Driven Development (FDD)
  • Kanban
  • Adaptive Software Development (ASD)
  • Lean Software Development (LSD)

Ques.4. What is an agile manifesto?
Ans. The agile manifesto is a document for agile software development prepared by 17 likeminded software development practitioners, and it was published in February 2001. It is built on 4 foundation values and 12 supporting principles.

Ques. 5. What are the four values of an agile manifesto?
Ans. The following are the four foundation values of an agile manifesto-

  • Individuals and interactions over processes and tools.
  • Working Software over comprehensive documentation.
  • Customer collaboration over contract negotiations.
  • Responding to Change over following a plan.

Ques. 6. What are the 12 principles of an agile manifesto?
Ans. The following are the 12 principles of an agile manifesto:

  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • Business people and developers must work together daily throughout the project.
  • Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
  • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  • Working software is the primary measure of progress.
  • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • Continuous attention to technical excellence and good design enhances agility.
  • Simplicity–the art of maximizing the amount of work not done–is essential.
  • The best architectures, requirements, and designs emerge from self-organizing teams.
  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Ques. 7. What is extreme programming?
Ans. Extreme programming or XP is one of the popular approaches to agile software development. It uses an object-oriented approach and it follows the same practices included in the agile manifesto. 

Extreme programming is responsible for introducing concepts that are now widely used as standard practices such as user stories, continuous integration and test-driven development. One of the advantages of extreme programming is that it gives the flexibility of incorporating changing requirements at any point in the development life cycle. 

Ques. 8. What are the five core principles of extreme programming?
Ans. The following are the five values or core principles of extreme programming:

  • Communication – This principle focuses on timely and close communication between relevant parties (mainly developers and stakeholders).
  • Simplicity – The basic idea behind this principle is to work on the immediate features first and keep it simple. The code should be such that it can easily be implemented and if any changes are required, refactoring can be done. 
  • Feedback – There are three sources that are used to gather feedback. By conducting unit testing, feedback of the system is captured. By conducting acceptance testing, feedback of the customer is captured and by conducting the planning game, feedback of the other software team members is collected.
  • Courage – This principle focuses on the courage required to design for immediate features, focusing only on the present. An agile team should also have the courage to recognize the fact that the requirements may change in the future and they will have to be incorporated in the code.
  • Respect – This principle focuses on self-respect, respect gained from others and respect given to other team members.

Ques.9. What are the four framework activities of extreme programming?
Ans. The following are the four framework activities of extreme programming:

  • Planning
  • Design
  • Coding
  • Testing

Ques.10. What is refactoring?
Ans. Refactoring is the process of changing the existing source code without changing its functionality.

Ques.11. What is pair programming?
Ans. Pair programming is a technique used in agile software development where two developers work as a team. One of the two developers writes code and is known as a driver, while the other reviews the code and is known as an observer. When required they can switch their roles.

Ques.12. What are the benefits of pair programming?
Ans. The following are various advantages of pair programming:

  • Pair programming results in improved code quality and fewer mistakes in the code as the other developer keeps reviewing the code as it is written.
  • Pair programming makes it easier to find solutions to any problem faced during the coding as the other partner can help.
  • It allows easy knowledge transfer as if one partner is more experienced, s/he can teach the other developer.

Ques.13. What are the various estimation techniques in agile?
Ans. Agile estimation techniques are used to estimate work efforts. The following are some of the agile estimation techniques:

  • Planning Poker
  • T-shirt sizes
  • Affinity Estimation
  • Sorting Method
  • The Bucket System
  • Three-Point Method
  • Dot Vote

Ques.14. What is the planning poker technique?
Ans. Planning poker is an estimation technique that involves collaboration among team members. It is conducted before an iteration starts with the help of developers. 

  • Each member is given a deck of planning poker cards. The values of the cards are similar to Fibonacci numbers. These numbers represent story points or days. 
  • The product owner reads and explains the user story to the team. Developers can discuss further if they have any questions.
  • After the discussion, each member estimates the efforts in developing the story and selects any card privately that represents the effort. 
  • All the cards are revealed simultaneously and if all are same then the story is estimated based on the card value.
  • If there are different card values, further discussion happens, and it goes on until all the team members agree upon the same number. 

Ques.15. What is a t-shirt sizing technique?
Ans. T-shirt sizing is an estimation technique used to measure the size of the user story and it is mainly used when there are relatively large backlog items to be estimated. In t-shirt sizing, the sizes of the t-shirts (XS, S, M, L, XL) are used to estimate the story. The decision about the size requires an open discussion. 

Ques.16. What is Lean Software Development (LSD)?
Ans. Lean software development is an iterative agile methodology that has borrowed principles of the lean manufacturing process and implemented them in the software development process. 

Some of the lean principles that have been adapted are fast delivery, elimination of waste, optimization of development time and resources, building quality in the product, etc. 

Ques.17. What is Kanban?
Ans. Like Scrum, Kanban is also one of the popular frameworks used in agile software development. Kanban is a Japanese word for signboard. In this framework, work items or user stories are displayed on the Kanban board, the team can see the status of each user story on the board. Kanban allows the product to be developed in one large development cycle rather than having iterations (like scrum). Kanban is incremental, not iterative.  

Ques.18. What is Scrumban?
Ans. Scrumban is an agile development methodology that is a combination of scrum and Kanban.
Scrumban is mainly used for maintenance projects where scrum processes are improved with the help of Kanban principles. It helps the project team in optimizing the processes.
The scrum part of the scrumban is to decide the amount of work that can be done in a sprint and prioritization of tasks.
The Kanban part of the scrumban is used to improve the processes and visualize the workflow. Scrumban uses a pull system of the Kanban; in which the items are continuously pulled from the backlog.

Ques.19. What is Test-Driven Development (TDD)?
Ans. Test-Driven Development (TDD) is a software development process where the test cases are written first and then the coding is done. Test cases are written to validate what the code should do.

The following are the basic rules of TDD development process:

  • First, a unit test is written to describe a feature of the system
  • The next step is to run the test. It will fail because the feature does not exist in the system
  • Write the code to accommodate the feature in the system. Basic idea is to write a simple test so that the test case will pass
  • Refactor the code as required
  • Repeat the above steps for other features of the system

Ques.20. What is DevOps?
Ans. DevOps is a set of ideas and practices that combine software development (Dev) and information technology operations (Ops). DevOps brings together the development and operations team in order to provide high-quality and reliable software and reduce development time.

Ques.21. What are the difference and similarities between scrum and agile?

  • Agile methodology is used in software development. It focuses on incremental development methods where the objective of the methodology is to quickly deliver the product. Whereas scrum is one of the frameworks of agile that falls under the agile project management umbrella. It is also used for software development. 
  • Agile follows an incremental and iterative approach to complete the projects. Scrum is also incremental and iterative in nature.

Ques.22. Can you explain agile testing in brief?
Ans. Agile testing is a software testing process that follows principles of agile software development. The agile development process is an iterative process where requirements keep on changing as per the customer needs. Agile testing is a continuous process that is done simultaneously with the development process. Agile testing includes testing the system continuously until the desired software quality is achieved. 

Ques.23. What approach should you follow as an agile tester when requirements change continuously?

  • First, while creating test cases, an agile testing team should focus on writing generic test cases that can be helpful in changing the test cases in the future.
  • An agile tester should collaborate with the product owner and business analyst to understand the changed requirement and risks associated with the change to modify the test cases. 
  • The testing team should go with automation testing only after the requirements are frozen.

Ques.24. What are some qualities of a good agile tester?
Ans. The following are some important qualities that a good agile tester should possess:

  • An agile tester should have in-depth knowledge of the agile principles and concepts.
  • An agile tester should be able to understand project requirements quickly and clearly.
  • S/he should be a good communicator as an agile process encourages continuous interaction with business analysts, developers, and other testers.
  • An agile tester should be able to handle changing requirements. S/he should be able to understand the risk arising due to the change and should be able to modify the test cases based on the changing requirements.

Ques.25. What are some agile testing methods?
Ans. The following are some agile testing methods:

  • Behaviour Driven Development (BDD) 
  • Acceptance Test-Driven Development (ATDD)
  • Exploratory Testing
  • Session-Based Testing

Ques.26. What are the stages of an agile testing life cycle?
Ans. Agile testing lifecycle is split into the following stages:

  • Agile Test Planning – In this phase, test plan schedules and the deliverables to be tested are created by the stakeholders.
  • Daily Scrums – These meetings include discussion of the status of the testing activity done on the previous day and setting testing goals for the day.
  • Test Agility Review – These meetings are conducted weekly with the stakeholders to review the progress.
  • Release Readiness – In this phase, the review of features is conducted to check the readiness of the features to go live on the production.
  • Impact Analysis – In this phase, feedback from the stakeholders is collected and goals for the next life cycle are prepared.

Ques.27. What is the difference between Incremental and iterative development?
Ans. In an iterative development method, the software is developed and delivered to the customer. Once the feedback is received from the customer, it is accommodated in the software and it is developed again in sprints and then delivered to the customer.

In an incremental development method, the software is developed in increments. Each increment contains completed features of some sub functionality of the system. 

Ques.28. What is a release candidate?
Ans. A release candidate is a build of the system that is functional and is released internally for testing purposes. They are not used for production deployment. Testing is done on the build to make sure no critical issues are present in the system.

The release candidate is a code /version /build released to make sure that during the last development period, no critical problem is left behind. It is used for testing and is equivalent to the final build.

Ques.29. What is a build breaker?
Ans. Build breaker is a situation in which a bug in the software stops compilation and causes warnings or failures in the automated test environment. It happens when developers accidentally commit bugs in the software.

Ques.30. How QA can add value to an agile team?

  • Testers participate in risk analysis sessions to identify risks and steps to prevent them.
  • Testers study the user stories, help in creating acceptance criteria.
  • They perform exploratory testing of the newly developed features.
  • They can provide continuous and quick feedback of the system to the developers as s/he has tested the software.
  • Testers participate in automation testing.
  • Tester helps in finding out any defects that are found in the system.
  • Testers can try to think differently on various scenarios to be tested in order to widen the test coverage and find more defects in the system.

Ques.31. What are the advantages of an agile model?

  • An agile model encourages quick and continuous delivery of the software.
  • Being a flexible model, an agile model helps in accommodating any changes suggested by the customers.
  • An agile process involves high interaction between various team members that helps in identifying any issues in the development process quickly.
  • An agile model helps in increasing customer software as the delivery is quick and after every increment, a working product is delivered to the customer.
  • Customers can review the product in and after each increment that gives them an assurance that the development process is going on the right track.

Ques.32. What are the disadvantages of an agile model?

  • As the requirements change frequently, the developers may not be able to quantify the full extent of the efforts required in the development process.
  • An agile method puts less emphasis on the documentation that might create problems in the future especially for new joiners in the project.
  • Continuous involvement from the client team is expected that requires the client team to be available for the meetings.
  • If the client team is not able to clearly explain the final outcome of the system, the project might get taken off track.
  • An agile development process requires experienced developers who have the skills to develop the system with the ability to make some quick and crucial decisions during the process.
  • Continuous interaction of each team member is expected that increases the time and energy required from the team.

Scrum Master Interview Questions

Ques.33. Can you explain Scrum in a brief?
Ans. Scrum is one of the most widely used frameworks of agile methodology. Activities of scrum framework are requirements, analysis, design, evolution and delivery.
In scrum, a list of requirements is added to a backlog called a product backlog. To achieve the requirements, work units called sprints are created. Each sprint contains certain requirements from the product backlog, and it can be of 2 to 4 weeks long. 

Ques.34. Why the scrum framework is called a lightweight process framework?
Ans. The agile scrum framework is a lightweight process framework as it has a few rules and practices. This framework is flexible and adaptable, and it can incorporate changes in requirements easily. In the scrum framework, product development is divided into sprints that are of small duration.

Ques.35. When do we use agile scrum methodology?
Ans. The following are some instances when the scrum framework should be considered for software development:

  • When requirements are not clear.
  • When there are high chances of changes in requirements during the development.
  • We can also use scrum when there is a demand for fast product delivery .
  • When the development team is self-organizing and cross-functional.

Ques.36. What are the three pillars of scrum?
Ans. The following are the three pillars of scrum:

  • Transparency – All the aspects of the product development process should be visible to the relevant parties such as the development team, the client, scrum master, etc.
  • Inspection – On a regular basis, the scrum participants should review the scrum artifacts and see if there is anything that is blocking the progress. 
  • Adaptation – If any issues or problems are found during inspection, adjustment or changes to the process should be made in order to remove the problems.

Ques.37. What is a sprint?
Ans. In scrum, a sprint is a short and time-boxed period where a certain amount of work is done by the development team in order to produce a releasable product. It is a basic unit of development in the scrum. 

Ques.38. How long the scrum cycle lasts?
Ans. The scrum cycle or sprint depends on the team and project size. A sprint cannot exceed a month i.e. 4 weeks. Normally, on average a sprint lasts for weeks. 

Ques.39. What are the primary artifacts of the scrum process framework?
Ans. Scrum artifacts are responsible for providing key information to the development team and the client. It helps in having the same understanding of the product development details.

There are mainly three artifacts:

  • Product Backlog – Product backlog is a list of to-do items maintained by the product owner. It consists of requirements, enhancements, features, etc. 
  • Sprint backlog – Sprint backlog is a list of to-do items, selected from the product backlog, to be completed in a particular sprint.
  • Increment – Increment consists of a list of all the product backlog items that were completed during the sprints. It is one of the deliverables of the scrum.

Ques.40. Can you tell about the various events conducted in each scrum sprint?
Ans. Scrum consists of the following four events that are used for inspection and adaptation-

  • Sprint Planning – In sprint planning, a detailed discussion of the project work to be done in the sprint is done. 
  • Daily Scrum – Daily scrum is time-boxed to 15 minutes to discuss the development team’s activities for the next 24 hours. It also includes discussions regarding the work performed in the last 24 hours.
  • Sprint Review – Sprint review is conducted at the end of the sprint. It is done to discuss the increment. 
  • Sprint Retrospective – Sprint retrospective is conducted so that the development team can inspect itself and they discuss the improvements or changes that can be done in the next sprint for more efficiency.

Ques.41. What is sprint planning?
Ans. In sprint planning, the plan for the work that needs to be done in a particular sprint is generated. For a month-long sprint, sprint planning is time-boxed to a maximum of 8 hours. The scrum master is responsible for making sure that the participants understand its purpose.

The following are two questions that are answered in sprint planning:

  • What can be delivered in the sprint? – The product owner discusses the goal of the sprint and items from product backlog will be selected to be included in the sprint backlog.
  • How will the work get done? – Based on the sprint backlog, the development team needs to decide how it will work towards developing a usable increment.

Ques.42. What is a daily scrum?
Ans. The daily scrum is an event to discuss the development team’s activities for the next 24 hours. It is time-boxed to a maximum of 15 minutes. In this event, the following questions are answered-

  • What did I do yesterday?
  • What will I do today?
  • Do I see any impediment which prevents the team from meeting the sprint goal?

The goal of the daily scrum is to inspect the progress of the sprint backlog items.

Ques.43. What is a sprint review?
Ans. The sprint review is conducted at the end of the sprint to inspect the increment. Stakeholders and development teams participate in sprint review. In this event, participants go through what was done in the sprint, discuss any challenges faced by the development team, provide feedback, etc. If needed, product backlog will be updated and inputs for next sprint planning will be provided. 

Ques.44. What is a sprint retrospective?
Ans. The sprint retrospective is conducted after the sprint review and before the sprint planning. It involves inspection of the last sprint and adaption of changes for improvement in the upcoming sprint.

Retrospective is time-boxed to a maximum of 3 hours for a month-long sprint. It is a scrum master’s responsibility for conducting the event and motivating other team members to increase the efficiency of the sprint.

Ques.45. What is a product backlog?
Ans. The product backlog is a list of to-do items. It consists of requirements, features, enhancements, changes, etc. It is maintained by the product owner who is responsible for its content.
The product backlog keeps evolving with product development progress and changed requirements. 

Ques.46. What is a sprint backlog?
Ans. Certain product backlog items are selected for a particular sprint and they are worked upon by the development team. This list of items is called Sprint backlog. The sprint backlog is a subset of the product backlog.

Ques.47. What is a zero sprint?
Ans. Before the first sprint starts, there are certain activities such as set up of development environment, preparation of product backlog, other upcoming sprint related planning, need to be done. This phase is called a zero sprint. It is also known as Inception Sprint, Initial Sprint or Sprint Zero.

Ques.48. What is a story point?
Ans. A story point is a unit of measurement to estimate the total effort required to implement a product backlog item or any other work. There are some factors that can be considered while calculating the required effort: the amount of work to do, the complexity of the work and any risk that may arise during the work.

Ques.49. What is a burn up chart?
Ans. Burn up chart is used in project management to keep track of the progress of the project work.
Burn up chart depicts how much project work has been completed and it also shows the total amount of work in a project.
The vertical axis in the burn-up chart represents the total work and the completed work. The unit of this axis can be story points, workhours or workdays. The horizontal axis represents the time that can be sprits i.e. iterations, days or weeks.
In the burn up chart, the scope change effect can be seen clearly as it shows the total amount of work. 

Ques.50. What is a burn down chart?
Ans. Burn down chart is used in project management to keep track of the progress of the project work.
Burn down chart depicts the amount of pending project work.
The vertical axis in the burn down chart represents the remaining amount of work. The unit of this axis can be story points, workhours or workdays. The horizontal axis represents the time that will be measured in sprits i.e. iterations.
In the burn down chart, the scope change effect is shown as a negative progress by the development team as it does not show the total amount of work.

Ques.51. What are the different types of burn down charts?
Ans. There are four types of burn down charts:

  • Defect burn down chart
  • Release burn down chart 
  • Product burn down chart
  • Sprint burn down chart

Ques.52. What do you mean by a defect burn down chart?
Ans. The defect burn down chart is a visual representation of the remaining work of a defect backlog. 
The vertical axis in the defect burn down chart represents the remaining amount of work in a defect backlog. The unit of this axis is defects in the defect backlog. The horizontal axis represents the time that will be measured in sprints i.e. iterations.

Ques.53. What do you mean by a release burn down chart?
Ans. The release burndown chart is used to monitor release progress. It represents the remaining work of the release. 
The vertical axis in the release burn down chart represents the remaining amount of work in a release. The unit of this axis can be hours, days or story points. The horizontal axis represents the time that will be measured in sprints i.e. iterations.

Ques.54. What does a product burn down chart represent?
Ans. The product burn down chart is a visual representation of remaining work of a product backlog. 

The vertical axis in the product burn down chart represents the remaining amount of work in a product backlog. The unit of this axis is story points. The horizontal axis represents the time that will be measured in sprints i.e. iterations.

Ques.55. What does a sprint burn down chart represent?
Ans. The sprint burn down chart is a visual representation of remaining work of a specific sprint.

The vertical axis in the sprint burn down chart represents the remaining amount of work in a sprint. The unit of this axis can be story points, workhours or workdays. The horizontal axis represents the time that will be measured in days.

Ques.56. What is a spike?
Ans. ‘Spike’ term was originated with extreme programming. Sometimes it is possible that for a certain user story, developers and other team members encounter a problem. They are unaware of the solutions of the same. They might need to conduct research or an experiment to find the solution. It is called a spike.

Spike is an experiment or an investment that helps the development team to estimate the story. Spike is entered into a backlog by the product owner. Spikes have two types – Functional Spikes and Technical Spikes.

For example, a user story contains requirements for integration with a 3rd party software. Developers have never worked with this software and they need some time to understand it. The product owner can keep a day or two for this research and create a spike in the backlog. 

Ques.57. What is a tracer bullet?
Ans. Sometimes it is possible that certain user stories are complex and hard to estimate, and they contain a new architectural element that is unknown to the developers. In such cases, a tracer bullet can be used with the help of a spike to examine the feasibility of the solution.

In the tracer bullet, one of the components of the user story will be built into an end-to-end solution with minimal code and feedback will be gathered. Based on the implementation of one component, other components of the story can be coded.

Ques.58. What is a velocity in scrum?
Ans. Velocity is a key metric in the scrum, and it is used to measure the amount of work the development team can cover in a single sprint. Velocity can also be used to estimate delivery time for further releases.

Ques.59. How to measure velocity in scrum?
Ans. There are two types of velocity i.e. actual velocity and expected velocity.

The actual velocity is calculated using the below formula-
Actual velocity = Total no. of story points completed / No. of sprints

The expected velocity is calculated using the below formula-
Expected Velocity = Total no. of estimated story points / No. of sprints

Ques.60. What is a user story?
Ans. User stories are simple descriptions used to represent business requirements from an end user’s perspective. User stories are easier to understand compared to conventional requirements or use cases. 

Ques.61. What do you mean by acronym ‘INVEST’ in scrum?
Ans. INVEST depicts the quality criteria of a good story. It stands for-

I – Independent; User story should be such that it does not depend on another story 
N – Negotiable; There should be a scope of negotiation in every story
V – Valuable; It should deliver value to the end user
E – Estimable; User story should be such that it can be estimated so that proper sprint planning can be done
S – Small; It should be a small work that can be completed in 3-4 days
T – Testable; it should be testable i.e. it should include acceptance criteria

A good user story meets all these criteria and if it fails to do so, the team should consider a rewrite.

Ques.62. What are the three components of a user story?
Ans. The following are the three components (3Cs) of a user story-

  • Card – Card depicts the user story in its raw form. The user story is written n a physical form on a card (post-it note). User story’s standard format is: As a [type of user], I want [goal] so that [some reason].
  • Conversation – The conversation happens between customers, product owners, testers, etc to discuss details of the card.
  • Confirmation – The confirmation means deriving acceptance criteria so that the team can confirm that the story has been implemented successfully.

Ques.63. What is an epic?
Ans. An epic is a large user story that can be divided into multiple small user stories. Once epic can be spread across multiple sprints.

Ques.64. What is a task in scrum?
Ans. A task is a technical work that the development team does in order to finish a product backlog item in a prescribed time frame.

Ques.65. What are the major roles in Scrum?
Ans. The following are major roles in scrum:

  • Product Owner – The product owner is responsible for representing requirements to the team. S/he should have a clear vision of what the product should be, and this vision should be communicated with the team effectively by the product owner. 

    The product owner is also responsible for managing a product backlog. S/he is responsible for listing the product backlog items, ordering the items, ensuring transparency of product backlog, ensuring product backlog items are understood by the development team, and optimizing the work done by the development team. 
  • Development Team – Development team mainly consists of developers who perform the development of the product by coding, testers who test the developed product, and business analysts. The development team is responsible for delivering quality software in the form of a usable increment at the end of the sprint. The development team should be self-organizing and cross-functional. It is important to note that scrum recognizes no titles for the development team other than the developer no matter what tasks are performed by the person.
  • Scrum Master – Scrum master is the leader of the development team. S/he is responsible for making sure the development team is executing sprint tasks properly. The scrum master is the one who is responsible for managing the sprint. 

Ques.66. What is a sprint goal?
Ans. The sprint goal is an objective decided for a particular sprint. The sprint goal is created during sprint planning before the sprint begins. In the sprint goal, a list of product backlog items is selected to deliver reasonable functionality. 

Ques.67. What is a task board in scrum?
Ans. Task board is a tool used to keep track of the progress of the current sprint. It is a visual representation of sprint backlog where the team can see tasks that are done, that are in progress and that are yet to be started.

Ques.68. What is an impediment in scrum?
Ans. An impediment is something that affects the productivity of the team and slows down the progress. 

Ques.69. Can you give some examples of impediment?
Ans. In scrum, impediments can be:

  • Technical issues
  • Organizational issues
  • Unskilled team members
  • Stakeholder issues
  • Infrastructure issues
  • Natural calamities

Ques.70. What is the scrum of scrums?
Ans. Scrum of scrums is an agile technique to scale up the daily stand-up meetings when large teams are working on the same project. In this technique, the groups are divided into agile teams of 5-10 people. Each sub-group or team designates an ‘Ambassador’ from their team. The ambassador participates in a daily meetings with the other team’s ambassadors.

This completes our list of top Agile interview questions and answers. In case of any query or suggestion, you can let us know in the comments.

1 thought on “Top Agile Methodology Interview Questions You Must Prepare”

Leave a Comment