Cracking job interviews is just as important as being a master in the field. While you may have the CPMCD (Communication, Planning, Modelling, Construction and Deployment) process on your fingertips, you will need to display your skills in front of the interview panel in order to land that superb job, that is talk your way to success! Not just competency, the companies require you to have a deeper understanding as well. After all, being able to solve queries and issues is the essence of software development.
What Agile questions can I expect during my Interview?
Interview questions vary from interviewer to interviewer and company to company. Many companies look for a basic understanding of the software, while others give you challenges to test your core skills. Here are a few questions you can prepare. Tip: You can answer them side by side and test your hold on the subject!
1. What is Agile?
This is the most basic and the most important question. If you aren’t aware of the crux of your subject, you won’t be able to explain the same to your clients or train your juniors in the future, and this is very important while taking up a job in a reputed firm. While answering this, remember that Agile is a method that works on iterations.
It is a heavily customer centric method that enables you to develop a software based on feedback provided from human interaction. That is the beauty of this method; it is what the name suggests, a flexible system.
2. What is velocity and how do we measure it?
Velocity helps us to create accurate timelines and is mainly used for planning by the development team. The team calculates estimated efforts at the end of each iteration, giving the team an approximation of how long the project might take. This is usually accurate and can help the team define timelines. It can be calculated by checking the user point or user hours in a sprint. The developers can calculate how many sprints it will require completing the project, thus calculating the velocity.
3. Explain Increment.
Simply put, an increment is the process in which a developer delivers the software in bits. It is system functionality or a step that the developing team takes towards the finished product. So basically, it is a completion of all the Product Backlogs created during a sprint.
Now, this might lead the interviewer to ask what a product backlog is, so be aware of that as well! You must be ready to justify and define any jargon you use during the interview.
Product backlog is a list containing every requirement of the product, ranging from changes to fixing bugs. Note that it keeps on changing with the modifications in your product to keep up with the feedback. Remember, agile is a method based on constant changes.
4. Tell us about Daily Stand-up.
Now, any leading SAFe training in Bangalore, Delhi, Pune, Hyderabad, you go to will always ask you to expect this question in an interview. You’re probably thinking how difficult is it to remember a daily stand up and why is it even that important? As a developer, you should know while daily stand-ups are 20-30 minute meetings at the start of the day to discuss your progress, plans or any blocks faced, it’s very useful in working as a team.
It becomes a ritual for the team to help their mates, find out any blockages or breaks in the system that needs fixing, and keeping up with the entire process, i.e. making sure that the entire team is properly aligned without any confusion.
5. What do you think are the drawbacks of Agile?
Developers are aware of the fact that no system is perfect. Hence, we strive each day to create something improved. Just like all the methods before it, Agile too has its shortcomings. Agile requires the entire team to agree, understand the concepts and be dedicated towards the process. You need to deliver quick, therefore the team needs to be on its toes, ready to take on challenges and have a solution-based approach.
Sometimes the requirements of the clients are not completely understood by the entire team – here is where daily stand-ups come into practice – and leads to an unsatisfied customer. When there’s no sharp end to a project, they tend to last longer, leading to lack of documentation and confusion for the new team.
6. What is Agile testing, and how can you be an efficient tester?
Note, they can also ask you to explain if you hold the ability to be a good agile tester. Do remember to mix your qualities with that of a good agile tester and present your answer.
Often when you create a software, you make sure that its user friendly before marketing it. The same happens during Agile, however, the testing starts way before the finished product is presented. It is a continuous process that goes on with the development and happens after the feedback and changes.
A good agile tester will be invested in the process and keep track of the entire operation. S/He will not just have good technical skills and be thorough with the tools, be able to write fast automated scripts, but also be analytical and observant. They must be able to clearly communicate with the product owner and implement the changes in the system. They must be able to share ideas, find defects and come up with quick responses.
Add that you follow TDD – Test Driven Development approach – for brownie points!
7. What function does a taskboard have?
Many teams prefer to make their own taskboards creatively. The basic points that a taskboard contains are User Stories, To be done, In progress, To be tested, and Completed. It keeps track of your progress while informing the team of what is going on. While you can experiment with the look, feel, and functions of a taskboard, the essence remains the same.
8. What is Scrum of Scrums?
It is a scaled technique used to keep multiple teams updated with the working of the project. Basically, it is used to align the teams to streamline integrations. The Scrum Master (The leader or the coach that guides, helps, and enables a scrum team) needs to bring the teams together in order to work efficiently towards the desired goal, with less mishaps and challenges.
9. How to run a successful Scrum of Scrums?
The foremost requirement for a successful scrum of scrums is creating an environment of comfortable information sharing and participation. Each team should be aligned with the information that they have to share, and that needs to be shared in order to ensure a smooth working of the project. The right people should join the scrum, i.e. those who are completely aware of the progress and the status of their team, and can communicate effectively, putting forward the required points. Keep a problem solving approach during the scrum of scrums so that there is less friction and more solving.
10. Tell us about the length of sprints of your last project.
This is usually asked to get an overview of your previous work and how you prospered under your scrum master or team lead. Usually, interviewers want to know if you’ve worked on different frequencies, i.e. changed the lengths, or worked on the same length, or whether you determined the length in the beginning or it changed during the process.
There are many more questions that you can be asked. You just need to know you basics and be confident in answering them and you are set! All the best!