Agile Methodology Interview Questions & Answers
In software development, agile practices involve discovering requirements and developing solutions through the collaborative effort of self-organizing and cross-functional teams and their customer/end user. Here you will find the most commonly asked Agile Methodology interview questions with answers which are faced by interviewee. Also these questions will get you acquainted with the nature of the questions you may be ask during your interview.
1. What is Agile Methodology?
Answer:- Agile is a software development methodology to build a software incrementally using short iterations of 1 to 4 weeks so that the development is aligned with the changing business needs.The advantages of agile methodology are customer satisfaction by rapid, continuous development and delivery of useful software.
2. What are the Roles in Agile?
Answer:- There are two different roles in a Agile methodology. These are the Scrum Master and Product Owner.
1. Scrum Master: A Scrum Master is a team leader and facilitator who helps the team members to follow agile practices so that they can meet their commitments. The responsibilities of a scrum master are as follows -
1. They enable the close co-operation between all the roles and functions.
2. They remove all the blocks which occur.
3. They safeguard the team from any disturbances.
2. Product Owner: A Product Owner is the one who drives the product from business perspective. The responsibilities or a Product Owner are as follows −
1. Defines the requirements and prioritizes their values.
2. Sets the release date and contents.
3. Ensures that the team is working on the most valued requirement.
3. What is a User Story?
Answer:- The user requirement defines the requirements of the user in terms of functionalities. There may be of two type of functionality.
1. As a <User Role> I want <Functionality> so that <Business Value>
2. In order to <Business value> as a <User Role> I want <Functionality>
During software release planning, a rough estimate is given to a user requirement using relative scale points. During iteration planning, the requirement is broken down into tasks.
4. What is Acceptance Criteria?
Answer:- Acceptance Criteria is defined as the functionality, behavior, and performance required by a product owner. It defines what is to be done so that the developer knows when a user requirement is complete.
5. What are the Advantage and Disadvantage of Agile Methodology?
Answer:- There are various advantages and disadvantages of using agile methodology over traditional waterfall model or others.
Advantage of Agile Methodology
1. Customer satisfaction is rapid, continuous development and delivery of useful software.
2. Customer, Developer, and Product Owner interact regularly to emphasize rather than processes and tools.
3. Product is developed fast and frequently delivered (weeks rather than months.)
4. A face-to-face conversation is the best form of communication.
Disadvantage of Agile Methodology
1. It is not useful for small development projects.
2. There is a lack of intensity on necessary designing and documentation.
3. It requires an expert project member to take crucial decisions in the meeting.
4. Cost of Agile development methodology is slightly more as compared to other development methodology.
6. What is Daily Stand-up?
Answer:-
1. A daily stand-up is a daily status meeting among all team members and it is held roughly for 15 minutes.
2. Every member has to answer three important questions −
-> What I did yesterday?
-> What I'll do today?
-> Any impediment I am facing.../ I am blocked due to...
3. Daily stand-up is for status update, not for any discussion. For discussion, team members should schedule another meeting at a different time.
4. Participants usually stand instead of sitting so that the meeting gets over quickly.
7. What is the Agile Project Management?
Answer:- Agile project management is an interactive approach to manage software development. The agile project management focuses on continuous releases and covers customer feedback with every iteration.
Traditionally the agile project management is classified into two frameworks: scrum and kanban. The scrum framework focused fixed-length project iterations, whereas kanban framework focused on continuous releases. After competition of project first iteration (or steps) project management activity immediately moves on to the next.
8. Who is involved in releasing the plan?
Answer:- Following person are involved in product releasing plan- Scrum Master, Product Owner, Agile Development Team, Stakeholders.
1. Scrum Master: The Scrum Master is a team leader and facility provider who helps the team member to follow agile practices so that they can meet their commitments and customers requirements.
2. Product Owner: The Product Owner is one who runs the product from a business perspective. He defines the requirements and prioritizes their values.
3. Agile Development Team: Agile development team provides the judgment on the technical feasibilities or any dependencies.
4. Stakeholders: Stakeholders are the customers, subject matter, program manager act as advisers in decisions which are made around the release planning.
9. What is Velocity Calculation?
Answer:- An agile team calculates velocity based on past iterations. Velocity is an average number of units required to finish user stories in an iteration. For example, if a team took 12, 14, 10 story points in each iteration for the last three iterations, the team can take 12 as velocity for the next iteration.
Planned velocity tells the team how many user requirements can be completed in the current iteration. If the team instantly finishes the work assigned, then more user requirements can be pulled in. Otherwise, the requirement can be moved out too to the next iteration.
10. What is a Task capacity?
Answer:- Three factors determine the capacity of the team:
1. Total number of ideal working hours in a day
2. A person gives total days in each iteration
3. Percentage of time a member is entirely available for the team.
Suppose a team has 5 members, committed to work full time (8 hours a day) on a project and no one is on leave during an iteration, then the task capacity for a two-week iteration will be −
5 × 8 × 10 = 400 hours
Also check :