Answers to Top Agile Interview Questions
Testers (developers) ensure that the whole process of testing (development) is broken down into as small steps as possible, and just a small unit of code is tested (developed) in each of these steps. The team of testers (developers) consistently communicates the results of their work and changes the short-term strategy and even the development plan on the go, based on the results of the agile testing. The agile methodology encourages a flexible and rapid response to change, which leads to better end results.
Each day, at a specific time and at a specific place (in front of the task board), the team meets to share updates about their tasks and tickets resolved for the day. This meeting addresses Scrum’s three questions listed below.
- What have you completed since the last meeting?
- What do you plan to complete by the next meeting?
- What is getting in your way?
A release candidate is a build or version of software that can be released to production. Further, testing such as UAT may be performed on this version of the product.
The key features of agile are:
- Daily stand-up meetings
- CRC (Class Responsibility Collaborator) cards
- Timeboxed task boards
- TDD (test-driven development), continuous integration, regular code reviews, pair programming, continuous deployment and delivery, automated builds, etc.
- Iteration planning meetings and iterative development
Agile has a new breed of PM tools including Rally Software, VersionOne, XPlanner, EasyBacklog, IceScrum, Agilefant, and Agilo. These tools bear no resemblance to the waterfall PM tools like MS Project or Clarity.
A storyboard is a visual representation of a software project’s progress. There are generally four columns, namely, ‘To do’, In Progress’, ‘Test’, and ‘Done’. Different colored post, its notes are placed in each column indicating the progress of individual development items. A storyboard is typically used in Agile development.
A Scrum Master should make this role their top priority to focus on the benefits of the overall team. Their load will vary from sprint to sprint depending on what impediments and issues the team is dealing with. Newly formed teams typically take more Scrum Master time, 50–100 percent; while experienced Scrum Masters with established well-functioning teams might spend 50 percent or less time on the Scrum Master role.
- Agile Testers should be able to understand the requirements quickly.
- They should know Agile concepts and principles.
- As requirements keep changing, Agile Testers should understand the risk involved in it.
- Agile Testers should be able to prioritize the work based on the requirements.
- Communication skills are a must for Agile Testers as they are required to constantly communicate with developers and business associates.
- An Epic is a group of related user stories.
- User Stories define the actual business requirements. They are generally created by the business owner.
- Task: To accomplish the business requirements, the development team creates tasks.
If capacity is measured as a percentage of 40 hours weeks, then completed
= story points * team capacity
If capacity is measured in man-hours, then completed story points/team capacity.
Before the Scrum sprint initiates, the product owner reviews the list of all new features, change requests, enhancements, and bug reports and determines the priority. If the project is new, it includes new features that the new system must provide. This list of items is referred to as a product backlog. The items that are kept on the sprint are referred to as sprint backlog.
If you have any doubts or queries related to DevOps, get them clarified from DevOps experts on our Agile Community.
Velocity is a metric that is calculated by the addition of all effort estimates associated with user stories completed in one iteration. It predicts how much work Agile can complete in a sprint and how much time it will require to complete a project.