1. What is the duration of a scrum sprint?

Answer: Generally, the duration of a scrum sprint (scrum cycle) depends upon the size of project and
team working on it. The team size may vary from 3-9 members. In general, a scrum script complete
in 3-4 weeks. Thus, on an average, the duration of a scrum sprint (scrum cycle) is 4 weeks. This type
of sprint-based Agile scrum interview questions is very common in an agile or scrum master
interview.

2. What is Velocity?

Answer: Velocity question is generally posed to understand if you have done some real work and
familiar with the term. Its definition “Velocity is the rate at which team progresses print by sprint”
should be enough. You can also add saying the important feature of velocity that it can’t be
compared to two different scrum teams.

3. What do you know about impediments in Scrum? Give some examples of impediments.

Answer: Impediments are the obstacles or issues faced by scrum team which slow down their speed
of work. If something is trying to block the scrum team from their getting work “Done” then it is an
impediment. Impediments can come in any form. Some of the impediments are given as –

 Resource missing or sick team member

 Technical, operational, organizational problems

 Lack of management supportive system

 Business problems

 External issues such as weather, war etc

 Lack of skill or knowledge

While answering impediments related agile scrum interview questions remember that you may be
asked the way to remove any of the mentioned impediment.

4. What is the difference and similarity between Agile and Scrum?

Answer: Difference between Agile and Scrum – Agile is a broad spectrum, it is a methodology used
for project management while Scrum is just a form of the Agile that describes the process and its
steps more concisely. Agile is a practice whereas scrum is a procedure to pursue this practice.

The similarity between Agile and Scrum – The Agile involves completing projects in steps or
incrementally. The Agile methodology is considered to be iterative in nature. Being a form of Agile,
Scrum is same as that of the Agile. It is also incremental and iterative.

5. What is the increment? Explain.

Answer: This is one of the commonly asked agile scrum interview questions and a quick answer can
be given this way. An increment is the total of all the product backlogs items completed during a
sprint. Each increment includes all the previous sprint increment values as it is cumulative. It must
be in the available mode in the subsequent release as it is a step to reach your goal.

6. What is the “build-breaker”?

Answer: The build-breaker is a situation that arises when there is a bug in the software. Due to this
sudden unexpected bug, compilation process stops or execution fails or a warning is generated. The
responsibility of the tester is then to get the software back to the normal working stage removing
the bug.

7. What do you understand by Daily Stand-Up?

Answer: You may surely get an interview question about daily stand-up. So, what should be the
answer to this question? The daily stand-up is an everyday meeting (most preferably held in the
morning) in which the whole team meets for almost 15 minutes to find answer to the following
three questions –

 What was done yesterday?

 What is your plan for today?

 Is there any impediment or block that restricts you from completing your task?

The daily stand-up is an effective way to motivate the team and make them set a goal for the day.

8. What do you know about Scrum ban?

Answer: Scrum-ban is a Scrum and Kanban-based model for the software development. This model
is specifically used for the projects that need continuous maintenance, have various programming
errors or have some sudden changes. This model promotes the completion of a project in minimum
time for a programming error or user story.

Agile Interview Questions

In this section, we are going to cover Agile interview questions. You should be prepared for the agile
interview with the following agile interview questions.

9. State some of the Agile quality strategies.

Answer: Some of the Agile quality strategies are –

 Iteration

 Re-factoring

 Dynamic code analysis

 Short feedback cycles

 Reviews and inspection

 Standards and guidelines

  Milestone reviews

10. Do you know about Agile Manifesto & its Principles? Explain in brief.

Answer: This is the theory which most of agile/scrum roles aspirant should be on tips. Four
manifesto values and 12 principles should be explained as much as possible as part of this question.
Even if it’s not explained in 100% accurate manner it should be fine but intentions of values and
principles should come out e.g.

 Working Software should be demonstrated at regular intervals

 Individuals & interaction – self-organization, self-motivating should be encouraged

 Customer collaboration

 Welcoming change at any point in time in the project

11. Is there any drawback of the Agile model? If yes, explain.

Answer: Yes, there are some drawbacks of the Agile model, some of them are as follows –

1. It is not easy to make a prediction about the effort required to complete a task. It becomes
more problematic in case of large projects as it becomes difficult to get an idea of the total
effort required.

2. At sometimes, it’s not possible to properly focus on the design and documentation of the
project

3. In case the requirements of the client are not understood properly, the final project will not
meet the customer requirements. Thus, it will lead to the customer dissatisfaction.

4. Only the leader who has considerable experience in Agile methodologies is capable to take
important decisions. The team members with little or no experience are not involved in
decision-making, thus they don’t get chance to advance their knowledge.

It’s not always the case that you will be asked the questions about the characteristics and
advantages of the agile and scrum in an agile scrum interview. So, just prepare yourself for the
drawbacks and disadvantages related agile scrum interview questions.

12. What is the use of burn-up and burn-down charts?

Answer: The burn-up chart illustrates the amount of completed work in a project whereas the burn-
down chart depicts the amount of work remained to complete a project. Thus, the burn-up and
burn-down charts are used to trace the progress of a project.

13. Define Zero Sprint and Spike in Agile.

Answer: To answer this question, describe Zero Sprint and Agile in detail, as follows –

Zero sprint – Zero Sprint can be defined as the preparation step of the first sprint in Agile. There are
some activities that are required to be done before actually starting the project. These activities are
considered as the Zero sprint; the examples of such activities are – setting the environment for
development, preparation of backlogs etc.

Spike – Spike is the type of story that can be taken between the sprints. Spikes are commonly used
for the activities related to the design or technical issues such as research, design, prototyping, and
exploration. There are two types of spikes – functional spikes and technical spikes.

Scrum Interview Questions

While going for a scrum job interview, prepare yourself for some good scrum interview questions.
You may be asked questions related to scrum master, sprint, story point, sashimi, ceremonies etc. by
the interviewer. So, prepare yourself for these scrum interview questions.

14. What is the role of the Scrum Master?

Answer: Here’s how you can answer Scrum Master interview questions like this –

The scrum master is the leader as well as coach of the Scrum team. The scrum master is responsible
to serve and protect his team from any kind of distractions that could affect their performance. The
main role of the scrum master is to motivate his team to achieve the sprint goal. He is focused to
build a self-organized and motivated team where each member is familiar with the implementation
of Agile and Scrum principles and applications. The scrum master keeps a proper check on the scrum
team if they are executing committed tasks properly. He is also responsible to increase the efficiency
and productivity of the team so that they can achieve the sprint goal effectively.

15. What do you know about a story point in Scrum?

Answer: A story point in Scrum is the unit for the estimation of total efforts that are required to
perform or complete a particular task. So, here is how you can answer such agile scrum interview
questions on a single line.

16. What is the role of Sashimi in Scrum methodology?

Answer: Sashimi plays an important role in Scrum methodology. Sashimi is a technique used by
Scrum to check the completion of all the functions created by the developers. Using this technique,
all the requirements such as analysis, designing, coding, testing and documentation that are used in
the constitution of a product are checked and only after that the product is displayed.

17. What are the different roles in Scrum?

The three scrum roles i.e. Scrum Master, Product Owner and Team should be explained with the
details of few primary responsibilities of each role. You can add more details as mentioned below for
a particular depending on the role you are getting interviewed for.

Product owner – A product owner is actually the stakeholder of the project. He represents the
project requirements before the team. He is responsible to have a vision of what to build and convey
his detailed vision to the team. He is the starting point of an agile scrum software development
project.
Scrum team – Scrum team is formed by the collective contribution of individuals who perform for
the accomplishment of a particular project. The team is bound to work for the timely delivery of the
requested product.

Scrum master – Scrum master is the leader and the coach for the scrum team who checks whether
the scrum team is executing committed tasks properly. He is also responsible to increase the
efficiency and productivity of the team so that they can achieve the sprint goal effectively.

18. What are the responsibilities of a Scrum Master?

Answer: Key responsibilities of a Scrum Master involves:

 Tracking and monitoring

 Understanding requirements properly

 Work to reach the project goal

 Process checking master and quality master

 Protect the team from detachments

 Improving the performance of the team

 Lead the meetings and resolve issues

 Resolution of conflicts and impediments

 Communication and reporting

19. What are different ceremonies and their importance in Scrum?

 Scrum planning, Scrum – Daily stand up, Scrum review & scrum retrospective ceremonies
should be clearly expressed with the purpose of the ceremony. It’s important to remember
the time-boxing of the ceremonies for a standard 4 weeks of Sprint or as per the Sprint you
have used in your projects.

Advanced Agile Scrum Interview Questions

20. What do you understand by the term “Scrum of Scrums”?

Answer: This is one of the commonly asked scrum master interview questions. Consider a case to
understand the meaning of the term scrum of the scrums. Let us assume an active project on which
seven teams are currently working. The number of members of each team is also seven. Each team
is responsible to lead its own scrum meeting. But, in order to coordinate and communicate with
different teams, it is required to organize a separate scrum meeting. The scrum meeting organized
to hold a coordination between scrum teams is known as the scrum of scrums. There is one team
leader from every team, known as ambassador, who is responsible to represent his team in the
scrum of scrums.

21. Scrum is an Agile framework, right? Name a few other Agile frameworks.

Answer: Yes, Scrum is an Agile framework. Few other Agile frameworks are –

 Feature Driven Development

 Test Driven Development

 Kanban

While answering this type of Agile Scrum interview questions please note that name the frameworks
you are familiar with or have followed.

22. Explain some common metrics for Agile.

Answer: You may definitely come across agile scrum interview questions regarding agile metrics. The
question may be related to a particular agile matric or explaining all the metrics. So, the detailed
description of some common metrics for Agile is as follows:

Velocity – Velocity is the average number of points from last 3-4 sprints. It is measured by the
summation of the all approved estimates of the stories. It gives an idea of the capacity, progress etc.

Cumulative Flow Diagram – With the help of a cumulative flow diagram, an inspection is done over
the uniform workflow. In this diagram/graph, the x-axis represents time whereas the y-axis
represents the number of efforts.

Work Category Allocation – Work category allocation is an important factor that gives a quick
information of the time investment i.e. where the time is being invested and which task should be
given priority as a factor of time.

Time Coverage – It is the time that is given to a code during testing. It is calculated in percentage as
a factor of the number of lines of code called by the test suite and the total number of relative lines
of code.

Business Value Delivered – It is a term which denotes the working efficiency of the team. The
business objectives are assigned numerical values 1,2,3.. and so on, as per the level of priority,
complexity, and ROI.

Defect Removal Awareness – It is the factor that helps the team to deliver a quality product. The
identification of an active number of defects, their awareness, and removal plays an important role
in delivering a high-quality product.

Defect Resolution Time – It is a procedure through which the team members detect the defects
(bugs) and set a priority for the defect resolution. The procedure of fixing errors/bugs or defect
resolution comprises of multiple processes such as clearing the picture of defect, schedule defect
fixation, completing defect fixation, generation, and handling of resolution report.

Sprint Burn Down Matric – The sprint burndown chart is a graph to represent the number of non-
implemented or implemented sprints during as Scrum cycle. This matric helps to track the work
completed with the sprint.

23. Is it ever suggested to use waterfall over Scrum? If yes, explain when.

Yes, sometimes it is suggested to use a waterfall model over Scrum. It is done when the customer
requirements are simple, well-defined, fully understood, predictable, and are not subjected to
change until the completion of the project. It may the case that you would haven’t ever used
waterfall over Scrum but you need to prepare for such Agile Scrum interview questions.

24. Why does Scrum encourage the use of automated testing for projects?

Answer: Scrum encourages the use of automated (automated performance or automated

regression) testing to make the fastest possible delivery of the project. While answering this
question, you may explain some tools that you have used for automated testing.

25. What do you know about “Planning Poker” technique?

Answer: Planning poker, also known as Scrum Poker, is a card-based agile technique that is used for
planning and estimation. To start a session of planning poker technique, the agile user story is read
by the product owner. The steps performed in the poker planning technique are –

1. Each estimator has a deck of poker cards with the values such as 0, 1, 2, 3, 5, and so on, to
denote story points, ideal days or something else that the team uses for estimation.

2. Each estimator has a discussion with the product owner and then privately selects a card on
the basis of their independent estimation.

3. If the cards with same value are selected by all estimators, it is considered as an estimate. If
not, the estimator discusses the high and low value of their estimates.

4. Then again, each estimator privately selects a card and reveals. This process of poker
planning is repeated to reach a general agreement.

Experience-based Agile Scrum Interview Questions

In this section, the questions will be related to the experience you have in agile or scrum. You should
be prepared with the data of few of your old projects when answering these experience-based agile
scrum interview questions.

26. Name some methodologies and development where you have used the Agile model.

Answer: While answering this type of agile scrum interview questions, keep in mind to mention
those methodologies that are familiar with. Some of the methodologies and development where the
Agile model can be used are –
  Crystal methodologies

 Lean software development

 Dynamic development

 Feature-driven development

27. Share your experience as a Scrum Master/Product Owner/Agile team member and what were
your primary responsibilities?

Answer: Here you have to explain your project details where you worked in Scrum team and defining
your role with the responsibilities you held. The trick in this question is whether while explaining you
are showing self-organizing and self-motivational team. Also, the interviewer will try to judge how in
depth you have worked in the agile/scrum environment based on your explanation.

28. What was the length of sprints/iterations in your project?

Answer: This is probably the most common question asked in agile interviews. The idea here is to
judge in which kind of environment you have worked. There will be definitely follow up question like
was this length fixed in the beginning and never changed? Have you tried with more than this length
or less than that?

29. How have you done user story mapping & estimation of stories in your projects?

Answer: This question is to under how you have done story writing, mapping, and estimation. Have
you used any estimation technique like planning poker, t-shirt, sizing etc? Whatever technique you
used in your project just mention it very clearly.

30 . What is the biggest challenge you faced in your project while handling the Scrum team
members?

Answer: This question is pure to judge your experience. The better you articulate your challenges
working in agile better it will be. Challenges generally faced in the initial stages of scrum is stabilizing
the velocity, team members conflicts, sticking to time-boxing etc..

31. Have you ever performed the removal of impediments as a scrum master on behalf of scrum
team?

Answer: As the scrum master acts as a coach for his team, he should motivate his team to perform
every task. Although he can remove impediments on behalf of scrum team but he should not do this.
It is recommended for a scrum master not to over pamper nor overrule the team. There may be
something when the team can face failure, at that time the scrum master should help them. He
should guide them with an appropriate method t0 get out of the problem. Scrum master should
prompt his team members to become independent enough to face problems and take a decision by
themselves. This is one of the frequently asked scrum master interview questions, so prepare now
and get ready to answer.
32. What is the difference between the agile & traditional way of working?

Answer: This question is to judge whether one is aware of the environment of the agile way of
working. Here the answer is expected to cover few or all of below:

 The traditional way is sequential where design->Development->Testing etc. happens one

after another whereas in agile all of this is done in every iteration/sprint

 Changes are welcomed in agile as Scope is flexible whereas in traditional manner scope is
fixed in the beginning due to which changes have to follow change request path

 Progress is measured with % completion traditionally whereas working software is the

measure of progress in agile

 Project Manager as a central controlling authority is traditionally driving the project whereas
Self-motivated and self-organizing teams drive the projects in agile

33. What is the difference between Sprint Planning Meeting and Sprint Retrospective Meeting?

Answer: The difference between Sprint Planning Meeting and Sprint Retrospective Meeting is as
follows:

Sprint Planning Meeting – A meeting in which all the Scrum roles (product owner, scrum team, and
scrum master) have a discussion about the team’s priority features and product backlog items is
known as sprint planning meeting. This meeting is held every week and lasts for almost 1 hour.

Sprint Retrospective Meeting – A meeting in which all the Scrum roles (product owner, scrum team,
and scrum master) have a discussion about the good part of the sprint, the bad part of the sprint,
and the sprint improvements is known as sprint retrospective meeting. This meeting that is held at
the sprint review meeting or at the end of the sprint; it lasts for 2-3 hours.

This is one of the frequently asked Agile Scrum interview questions. You may be asked to define the
above terms separately or the difference between these two.

34. When can you say your story is ready to develop/groom enough to deliver?

Answer: Ready is a stable state of Scrum that is linked to a user story. As per the Definition of Ready
(DoR), a user story have to satisfy some conditions before picking it up for a sprint i.e. to be in the
ready state. So, the conditions that are essential for the development/grooming of a user story
specify if the user story is ready to develop/groom enough to deliver or not.

Basically, the following questions should be answered to consider a user story ready:

Why: Is it clear what the business or stakeholders are trying to achieve?

What: Is the goal or outcome of the user story clear?

How: Is the strategy for the implementation of user story clear? Is the story is small enough?

The conditions for the user story are defined by scrum master in coordination with the product
owner. Although the conditions vary for the different projects, some of the common conditions for
user story are –

 It is clear and well-written in a format to identify user type, function, and benefits
 It is self-contained i.e. independent of other user story inherently
 It is small so that can be delivered in a single sprint
 It has a defined acceptance criteria for all the functional requirements and appropriate
non-functional requirements
 It should have been estimated by the scrum team
 All the external blocking dependencies should have been resolved before starting the
sprint
 The resources/team have all the skills required to deliver the sprint
So, if the user story can give satisfactory answers to the above questions and meet the conditions
defined, it is considered to be ready.

35. How do you manage if the story is high priority and resources left before last day of sprint
completion?

Answer: The answer to this question will fully depend on the number of resources left.

If one or two members leave the story just before a day of the sprint completion, a scrum master
can handle the situation as described below –

First, analyze the pending tasks and the impact on the overall sprint. According to that, try to find an
alternative solution around to manage the situation. As a leader, you can decide to work for some
extra hours to complete the sprint and can also ask (remember to ask, not to tell) other team
members to do so. And this way, you can do the sprint completion on time.

In case, more or all the members leave just before a day of the sprint completion, then the situation
can be handled as –

Analyze the amount of pending work and its impact on the overall sprint.

Check if you can manage the situation and finish the task by yourself or try to get some other
resources to work. (Although this won’t be feasible as you will have to first explain everything about
the sprint and task done to the new team; of course it won’t be possible in a day.) So, if you can’t
manage to complete the sprint by yourself, it’s better to tell this to your product owner. You can ask
him to give some more time to complete the sprint, so you can get a new team or get it done by
yourself by working extra hours.
36. What is ‘Scrum of Scrums’?

 It is a terminology used for scaled agile technologies, which is required to control and
collaborate with multiple scrum teams. It is best used in situations where teams are
collaborating on complex assignments.

 It is also used to ensure that the required transparency, collaboration, adaption, and
adoption are established and to ensure that the products are deployed and delivered.

37. What is User-Story Mapping?

 User story mapping represents and arranges user stories that help with understanding
system functionalities, system backlog, planning releases, and providing value to customers.

 They arrange user stories based on their priority on the horizontal axis. On the vertical axis,
they are represented based on the increasing levels of sophistication.

38. What is Empirical Process Control in Scrum?

 Empiricism refers to work that’s based on facts, experiences, evidence, observations, and
experimentation. It is established and followed in Scrum to ensure project progress and
interpretation is based on facts of observations.

 It relies on transparency, observation, and adaption.

 The mindset of the team and the shift in thought process and culture are essential to
achieve the agility required by the organization.

39. What is a User Story?

 A user story is an agile software development/ project management tool that provides
teams with simple, natural language explanations of one or more features of the project
that’s written from the perspective of the end-user.

 The user story doesn’t go into detail but only mentions how certain types of work will bring
value to the end-user. The end-user, in this case, could be an external component or an
internal customer/colleague within the organization.

 They also form the building block of agile frameworks like epics and other initiatives.

 They ensure that the teams work towards the goals of the organization, with the help of
epics and initiatives.

 The requirements to make a user story a reality are added later, after discussions with the
team.

 They are recorded on post-it notes, index cards, or project management software.

40. How are user stories, epics, and tasks different?

  User Stories: They provide the team with simple explanations of the business’ requirements
created from the end user's perspective.

 Epics: An epic is a collection of related user stories. They are usually large and complex.

 Tasks: Tasks are used to break down user stories further. They’re the smallest unit in Scrum
that is used to track work. A person or a team of two people usually work on a task.

41. What are some risks in Scrum? How are they handled?

Some types of risks in Scrum are:

 Budget: The risk of exceeding budgets

 People (team): Team members need to be of appropriate skill and capability

 Sprint (duration and deliverables): Exceeding the duration, addition of the scope of work

 Product (user stories, epics): Having ill-defined user stories and epics

 Knowledge and capability: Having the appropriate resources

Managing risks involves identifying, assessing, analyzing, defining, and implementing risk responses,
monitoring, and managing them. These are done on a continual basis right from the starting of the
project until completion. It is essential to understand that the impact of the risk is based on the
proximity of the actual occurrence of the risk.

42. How to deal with Score Creep?

Score creep refers to a change that’s uncontrolled and added without checking its impact on scope,
time, cost, etc.

To handle it, here’s what needs to be done:

 Close monitoring of work being done on a day-to-day basis.

 Understanding and communicating the vision to the team and ensuring they’re aligned.

 Capturing, reviewing the project requirements regularly (against what is delivered), to

emphasize to the team & customer about the requirements signed off.

 Ensuring that any changes introduced go through change control & are implemented based
on the approval for change request.

 Avoid gold plating.

43. What are MVP and MMP?

 Minimum viable product (MVP) is a Lean Startup concept that stresses the impact of
learning while performing product development. This allows one to test and understand the
idea by getting exposed to the initial version for target customers & users. To accomplish
this, one has to collect all the relevant data and learn from that collected data. The thought
 behind MVP is to produce the product, to provide access to the users, and to observe how
the product is used, perceived, and understood. This will also provide more insight towards
what the customers’ or users’ needs are.

 The MMP (Minimal Marketable Product) refers to the description of the product, which will
have a minimal number of features that address the requirement of the users. The MMP
would help also help the organization reduce the time to market

44. What does DoD mean?

 Definition of Done (DoD) refers to the collection of deliverables, which includes written
codes, comments on coding, unit tests, integration testing, design documents, release notes,
etc. This adds verifiable and demonstrable values to project development. DoD is very
helpful to scrum while identifying the deliverables to achieve the objective of the projects

 It helps with:

 Defining the steps required to deliver the iteration

 The usage of appropriate tools like burndown to make the process more effective

 Ensuring on-time feedback throughout the project life cycle

 Ensuring the walkthrough of the product backlog items are done and understood
correctly

 The creation of a checklist for the product backlog items

 Ensuring the DoD is defined to become task-oriented

 Involving the product owner for reviewing during the sprint and sprint retrospective

45. How would you handle conflict within the team?

Giving individual coaching to team members is one of the most effective strategies to resolve a
problem. It is imperative for a Scrum Master to maintain positive relationships with team members
and provide guidance when they face challenges.

For a Scrum Master, paying attention to the source of the problem and listening and acting
accordingly would go a long way. Any disagreements should be shared with other team members in
a manner that they would be open to suggestions for resolving the issue. When a conflict arises, the
Scrum Master must intervene so that the process runs smoothly and without hiccups.

The following steps help in handling conflicts within the team:

Step 1 - Scene setting

First, we must determine the source of the team's quarrel. Before taking any action, it is necessary
to understand the discrepancy between two groups or two persons. In times of dispute, Scrum
Masters typically react aggressively against team members in the hopes of resolving the conflict on
their own. However, while this may temporarily cure the problem, it does not address any
underlying concerns. The Scrum Master must lead the team and teach them that disagreement is a
regular occurrence in the workplace and it can be resolved with assertiveness. It is the leader's
responsibility to guarantee that team members' concerns are acknowledged and addressed.

Step 2 - Gathering Information

Gathering facts about the conflict is usually crucial before coming to a conclusion about a certain
individual or suppressing the topic. This could be accomplished by listening to each party separately
and comprehending the situation from their point of view. The Scrum Master should also consider
other team members' perspectives and also respect every team member’s decisions. As a result, the
Scrum Master must elicit everyone's assistance in order to gain a picture of the workplace conflict.

Step 3 - Brainstorming to find a solution

It is often impossible for the leader to resolve problems on his or her own. Furthermore, several
members of the Scrum Team would have better answers that would quickly remedy the problem.
Organizing spontaneous group talks and sharing opinions on various activities would stimulate good
discourse between the two people or groups in these situations. This would urge both sides to see
things from the other's perspective. This also provides opportunities for superior ideas to be pushed
and for the disparity to be bridged.

Step 4 - Solution conferring

Listing all of the possible answers to an issue would only be useful if those solutions were put into
action. Scrum Master removes the team's roadblocks by implementing the solution in this step.
Throughout the conflict resolution process, remembering to stay calm and respectful will aid in a
speedier and more efficient resolution.

46. How would you deal with a difficult stakeholder?

The four strategies by which we can deal with difficult stakeholders are:

1. Listen to them carefully - Make an effort to comprehend their point of view. If what they say
aggravates you, consider whether their needs are in line with the project's goals. Is it
possible that they want things done a little differently? Make efforts to discover some
common ground. People desire to be understood and to believe that their voices are heard.

2. Estimate their motivation - Try to understand the motivation behind the stakeholders’
opposition. This will allow you to compromise, and come up with a win-win solution, and
complete the project. Answer questions like - Are they reporting to a board of directors that
has its own reservations? What's the source of your stakeholders' sudden opposition? Are
they concerned about exceeding their budget? Concerned that the project may not turn out
as planned?

3. Meet them one after another - Meeting without other stakeholders in the room relieves
stress and allows the stakeholders’ to be more at ease. So, make time to meet with each
challenging stakeholder separately. This results in interactions becoming clearer and calmer.
Take advantage of this chance to learn more about their point of view and recommended
 solutions. However, don't ask them why they don't like your plan outright. Ask open-ended
inquiries about their thoughts and how the project is moving instead.

4. Watch the stakeholders closely by identifying them - Determining the stakeholders and
finding out what inspires them should be the first step. Anyone who is influenced by our
work has control or influence over it or is interested in its success is referred to as a
stakeholder.

47. What are the three pillars of Scrum?

The three pillars of Scrum are summarized below -

Adaption: The method being processed must be changed if an inspector determines that one or
more aspects of a process are outside of permitted limits. A correction must be made as quickly as
possible to avoid future deviation.

Transparency: Transparency mandates that those elements be specified by a consistent standard in

order for viewers to understand what they are viewing. For example, while referring to the process,
all participants must use the same terminology. Those reviewing as well as those executing the job
and the resulting addition must have the same definition of "done."

Inspection: Scrum users must check Scrum artifacts and progress toward a Sprint Goal on a regular
basis to discover unwanted deviations. Inspections should not be carried out so frequently that they
constitute a burden to their work. Inspections are most successful when skilled inspectors do them
attentively at the point of work.

48.How can you assure that the user stories meet the requirements?

A good user narrative includes both a description and acceptance criteria. It should be completed in
a sprint with the fewest possible dependencies. The team should be able to develop and test while
still delivering estimations within the sprint's constraints. In short, good user stories adhere to the
INVEST concept.

I → Independent: The user story should be wri en in such a way that team members are less
dependent on one another.

N → Nego able: it should define the func onality of the user story and is subject to the Product
Owner and the Team’s approval.

V → Valuable: It should offer value to the customer's experience.

E → Es mable: This lets us be able to roughly approximate in terms of time.

S → Small: The user story should be ny enough for the team to finish in a sprint.

T → Testable: Good acceptance criteria a er tes ng is required.

49. Explain Requirement Prioritization?

Requirement prioritization is mainly used in software product management, and it helps in
determining the candidate requirements of a software product that includes certain releases.

Here, the requirements are prioritized in order to minimize the risk during the development process
so that the high-risk requirements are implemented first.

50. Can You Explain The Techniques Used For Requirement Prioritization?

The list of Requirement Prioritization techniques are listed below:

1. Ranking: You have to rank the requirements on an ordinary scale so that each numerical
value you give is based on importance. For example, if you assign a number 1, then it means
that the requirement is very important, and you have to implement it first. This method
works best when you deal with a single stakeholder.

2. Numerical Assignment: Based on the grouping requirements into different priority groups in
such a way that each group represents something that a stakeholder can relate to. We can
group the requirements into moderate priority, optional priority, and critical priority.

3. Moscow Technique: It allows the stakeholders to prioritize the requirements in a

collaborative manner. It has four groups, namely MUST have, SHOULD have, COULD, and
WOULD. The acronym stands for

MUST (Mandatory)

SHOULD (Of high priority)

COULD (Preferred but not necessary)

WOULD (Can be postponed and suggested for future execution)

4. Bubble Sort Technique: In this technique, you take two requirements and compare them,
and if you find that one requirement should have given a greater priority than the other,
then you swap them.

5. Hundred Dollar Method: It is used with multiple stakeholders, where they have to vote for
the requirement, which is most important dramatically. Here all the stakeholders get
conceptual 100 dollars. Later they can distribute among the requirements.

6. Analytic Hierarchy Process (AHP): This method was designed by Thomas l.Saaty. It works on
the entire framework to make correct decisions in fields like business, government,
healthcare, and many other sectors. Here the stakeholder divides the goals into smaller sub-
problems so that they can be easily solved.

7. Five Whys: Sometimes, a stakeholder may want to implement certain features that are not
founded on logical grounds, then with the FIVE WHys, the analyst can ask the stakeholders
repeatedly about the requirement until the importance of the requirement is known.
 51. Explain TimeBoxing in Scrum.

Timeboxing is an important time management technique or tool that is used to limit

the amount of time that is being spent to complete a task. It simply allows a fixed
unit of time for each and every task and this unit is known as a time box. The
maximum length of the time box is 15 minutes. It not only helps to improve focus
but also results in an increase in productivity. There are some events in Scrum and all
these events are timeboxed which means all these events are allotted with a
maximum and fixed unit of time for the task. The events that are time-boxed are
listed below:

 Sprint
 Sprint Planning
 Daily Scrum
 Sprint Review
 Sprint retrospective