1. What is Scrum?

Scrum consists of a processed framework for helping teams develop a project in an

incremental and iterative manner.
2. As a Scrum Master, How can You Track the Sprint Progress?
I would use the burndown chart to track a sprint’s progress. The horizontal axis indicates the
number of sprints while the vertical one shows the remaining work.

3. What is the Objective of “User Story” in Scrum?

In Agile software development, a user story is a tool that describes a feature based on the
end-users’ perspective. Written in natural language, user stories act as boundary objects
that facilitate communication and sense making. In other words, they enable the software
development team to understand the system and its context.
4. As a Scrum Master, how will You Help the Product Owner?
I can support the product owner in various ways. I can help him or her with efficient
management of the product backlog and in practicing and understanding agility. Besides, I
can assist the product owner by promoting scrum events as needed or required and
enabling the scrum team to adopt a shared vision.

5. Why is it Necessary to Adopt the Agile Methodology?

The Agile methodology enables developers to achieve customer satisfaction by delivering
useful software swiftly. With Agile, potential changing requirements are eased, even later on
after a company develops. It facilitates daily and better partnerships between the developers
and the company. Besides, Agile methodology offers simplicity in software development and
promotes face-to-face communication.

6. What Techniques Can You Use to Perform Estimations in Scrum Projects?

The Agile estimation techniques that I can use to carry out estimations in scrum projects are
the T-shirt estimation, planning poker estimation, Estimation by analogue, and
disaggregation estimation techniques.

7. What is scope creep and how would you prevent its occurrence?
A scope creep occurs when new features whose requirements were not clearly defined at
the beginning are added to a product that is being developed.
It can be prevented by specifying all the requirements clearly from the start, ensuring
to monitor the project progress, and grooming the sprint backlog effectively.

8. How is the change management in Waterfall different from an Agile scrum?

In Waterfall, change management is based on the change management plan, the change
tracker and the release plan based on which the consultants deliver their work.

However, in Agile, a change management plan doesn’t exist. Thus work delivery is based
entirely on what is defined in the product backlog.

9. In Scrum, what is Minimum Viable Product (MVP)?

Minimum Viable Product or MVP consists of the smallest product part available to the public
that clearly shows its main functionality. The MVP doesn’t have to be functioning; it can be
just a prototype. The main aim of MVP is to receive feedback from users or stakeholders.

10. As a Scrum Master, what is Your Role during the Daily Scrum?
My role would be to arrange the scrum meeting whose main player is the development
team. Besides, I would guide the team to ensure that the daily scrum is performed within
the set time-box. I would also ensure that there are no other participants other than the
development team members.
11. As a scrum master, what would you do when you realize Agile principles are being
broken?
First, I would make sure the customer and development team agree on a regular sprint as
well as release schedule and ensure that they adhere to it.
Second, I would make sure that the product owner retains a well-organized product backlog
so that all change requests are addressed by the product owner.

Thirdly, I would ensure sprint and release workshops are attended by all development team
members.

12. What artifacts are maintained in scrum?

There are three artefacts in Scrum: Product Backlog, Sprint Backlog and Product Increment.
The product backlog and sprint backlog are the two scrum artifacts. The product backlog
consists of the prioritized list of requirements while the sprint backlog comprises user
stories, which the scrum team will do for a sprint.

13. What role does a product owner perform in the scrum framework?
The product owner acts as a point of contact between the business and the scrum team. He
or she identifies and refines the items of the product backlog. Ultimately, the product owner
concentrates on the product success.

14. State three main tools utilized in a scrum project?

The main tools that are used in scrum projects are JIRA, Rally, and Version One. JIRA is
mainly used for tracking issues and bugs associated with the software. Rally assists in
tracking every phase of development releases and iterations. Similarly, Version One makes
reporting, tracking, and planning easy across programs and teams.

15. Describe your Daily Routine as a Scrum Master

Resolving problems or removing impediments is at the top of the daily tasks performed by a
scrum master. This is particularly at the onset of the project when many internal and
external issues arise. He or she reports team performance, which helps to improve the team.
The scrum master offers facilitation to the team and helps out as need arises to enable the
team to achieve sprint goals. Other daily responsibilities include driving organizational
change, educating the organization, and breaking up fights or quarrels.

16. What do You Understand by Timeboxing?

Timeboxing is the practice of assigning specific amount of time to an activity. The fixed time
unit allocated to the activity is known as a time box. In scrum, the maximum time box is 15
minutes.

17. What is Done During Sprint Review and Retrospective?

Sprint review involves walking through stakeholders or demonstrating to them the story or
feature implemented by the scrum team.
On the other hand, retrospective consists of identifying what went well collaboratively as
well as determining what may be done better including coming up with action items for
continuous improvement.

18. Do You Find any Disadvantage with Scrum?

I have not found any shortcomings with scrum. However, problems occur when the
members of the scrum team lacks understanding of the principles and values of the scrum.
Issues may also arise if they are not flexible to change.

19. In your opinion, can scrum be applied in the development of all kinds of software?
Scrum is particularly useful when developing complex projects. In addition, it is appropriate
for projects with a strict or early deadline. Besides, scrum is most suitable when developing
an application from scratch.

20. Describe Velocity in Scrum?

In scrum, velocity is the measure of the total work that a team can handle during one sprint.
The measure is determined by adding story points from the previous sprint. Velocity acts as
a guide for understanding the stories that the scrum team can perform.

21. What are the key components of well written user story ?
Written from end user’s perpective.

22. Agile principles and scrum framework?

23.Passion for Agile and Scrum

Share some past stories.

24.Demonstarte your leadership and ability to work with cross-functional teams.

How you managed conflicts and fostered a positive culture, set clear goals., provide
opportunity for learning and development, address the issue promptly.; recognise individual
achievement.
25. Be a good listener.
Show interviewer that you’re interested in his/her perspective; ask about the challenges.

26.During sprint retrospective, team member express dissatisfaction regarding current

sprint length , how as a scrum master you’ll facilitate this resolution?
We have first and find out why does the team member feel so? Do other team members feel the same, if
not, is it due to the particular stories he is assigned? If so, what is the difficulty he/she is facing in
completing the tasks. Are the tickets too difficult for him due to lack of business understanding or technical
difficulties or is it some other reason. Once we drill down in to a problem he is facing, we can then come
up with a solution to address this issue.

27. In the middle of the sprint, team member encounters technical issues, how as a scrum
master you’ll facilitate this issue ?
There are a few scenarios for facing technical issue middle of the sprint. 1. The Team missed the
functionality while sprint planning. 2. The Developer does not do proper brainstorm on the sprint point
that he/she needs to develop.

At this stage as SM needs to check and discuss with developers, how we fix and complete the story point
as per our timeline. If there are major changes in that then needs to be talk and discussion with the PO
and stakeholders and be transparent, - If this story point we need to hold and move to the next sprint. If
they are agreed, then it will solve the issue. OR - If not agreed, then need to check other story points
which we are not important and move to that in the next sprint and we focus on this issue and complete
it. OR - If they want all the story points in the same sprint, then we have to manage another resource to
help the developer or the developer needs to stretch the timing.

28. How do you track team performance in scrum framework?

Determining dod

29.Challenges faced as a scrum master?

30. How as a SM how do u ensure you give timely reporting to management and stakeholders?

Understanding the priority (do not assume take surety)

31.How do u facilitate collaboration, organization within the team, and everyone is working toward the
common goal?

Keep team motivated.; bible management, agile manifesto, scrum guide.

32.How do you assess the team performance?

33. How do you ensure team is making progress?

34. Greatest strength as a scrum master?

35.How will you help new team member who comes in the team ?

36.Achievement so far as a scrum master?

Being working in global team.

37. Scenario when other collegues comes to you and asks about safe and other framework ?

If no knowledge be an active listener, interact and learn.

38.Metrics, business value

Infront of client, says business value, how project is looking, how many defects. , quality of
the product

39.Lead time and cycle time

Used in kanban framework.

40.Purpose of scrum sos?

When we are in scaled agile framework, there are multiple teams, talks about individuals
teams. Depends organization to organization. Where agile is adopted at individual level.

41.Are you aware of spike in technical debts ?

Spike – user story or epic for which dev do not have clear understanding, they dedicate time
in which they do research and depends on that they estimate time how much they’ll take to
complete
Technical debt – feature that developer has developed because of the deadline developed
due to short time and later on they can re develop it.
42. What is a good user story?
Something which has characteritcs it follow, independent on it and it is not dependent on
others, should be negotiable. Should be able to deliver the value. Small enough to deliver
and testable and dod is achieved.

43. How we can increase team productivity?

44. Difference between burn up and burn down chart?

Burn up – based on metrics
Burn down- figure out how many stories are burned, each day how many stories have been
burned if lesser than what we expect., how far or near we are to the sprint goal.

45. What is your favourite scrum event and why?

Retrospective – what went well and hat did not

46.What is refinement and sprint planning as a scrum master?

Estimation is done during the refinement meeting

47.Strength and weakness as a scrum master?

Emphatetic person and collaborate well, come to me anytime and share challenges and
concerns
Multi teams and therefore there are delays

48.what is burnup and burndown chart?

2 of the metrics used in scrum framework. Progress and purpose, Burndown – how much
work is done and completed ; burnup

49. How you will explain to your grandmother?

Agile – smarter and faster, basic understanding, doing dishes, cooking, washing, basic
functions , instead of hiring someone for 24 x7 hire someone for 2 hours. Increase the time
to 4hrs – 6hrs
50.What is mvp(minimum viable products)and mmp(minimum marketable products)
Mvp – minimu features that we should develop which will help us ensure assumptions or
idea we have take is going to work or not. decides future of the product
Mmp – launch to the market, ready enough to be delivered.

51. Multiple offers why you’re looking for other opportunities?

It changes for person to person, grow my skills and financially didn’t had an opportunity to
build myself, financially match to the market standard.

Situational SM questions-:
52.You have a project and instead of 12 months it has been cut down to 6 month. What
would be your approach?
First understand why we are doing it. Reduce the scope, increase the budget, increase the
resources. Transfer the knowledge to the new associate. He/she would take time to
understand the project.Iron triangle of Project management.

53. How do you think how you can adapt to the constant change in the organisation.
Adapt to the change, We are agile. Responding to the change over following the plan. Many
types of change. Personal, Managerial change. If manager is changed and you had good
rapo with him and if any new manager comes then it takes time to build that rapo again.
Technology changes – if any new technology is introduced it takes time to move tothat
technology.
Process changes-: Wfh, increments etc.. Adaptive to particular way of working then again
move into new way of working..
How changes impact positively and what are the benefits you’re getting. It would be
comparatively easy to adapt.

54.Past incident where you made mistakes?

As human being we are prone to mistake open and transparent to accept those mistakes.
Open vulneberabilities infront of the team. Try and experiment different things and give
solutions. Neede to test a particular functionalities as a tester and it passed went into
production. Didn’t had any issue earlier. Went back and checked. Realised that there was
aparticular condition that neeed to met therefore it wasn’t identified. Review first and
should not be overconfident. Learned and accepted infront of the team.
55. If po comes and ask for development coding or testing?
As a SM I have different set of responsibilities. Not into development testing. So would I be
able to do it. First need to figure out can I do it. Figure out other solution. Can there be other
resources who can work on it. Can help with functionalities. Need of the hour then we can
really look for the solutions.

56. How would you release the bad news to the clients?
First take permission to discuss bad situations. Deliver the situation as early as possible. On’t
keep it for the last day or last minute.

57. What is the reason for sprint review and what happens in sprint review? Role of scrum
master.?
To inspect the outcome of the sprint and determine future adaptations. Working sessions.
Sprint review is second to last event. Timeboxed to maximum of four hours for one month
sprint.

58. If PO is not available during the sprint planning and closure what would you do as a
Scrum Master ?
1. Short term -: (anything from one day to a week)
-rely on self organization.
2.Medium term-: (anything from one week to four weeks)
- Representatives should take care of po’s role.
-does limited product backlog management and stakeholder communication
-intermediate impact , find a representative , and leverage scrum master or agile coach to
support them
3.Long term -: (for a month or so)

59.What will happen if the user story is not finished , spill over, ? will you re-estimate the
whole user story or only work which is not done ?
Tthere are two ways-:
Split-: Don’t get credit for storypoints , get credited for hours.
60. How are story points estimated in jira/scrum ?
Relative estimation , Absolute estimation
61. Pre requisites for scrum master before joining morning meeting?

62. what is not a technique used for splitting user stories?

Split compound user stories.

63. Who typically participates in SoS planning connects?

Each scrum team has its scrum master or designated team member who attends SoS
meetings.

64.What is the purpose of having SoS in Scrum ?

A Scrum of Scrums (SoS) is a meeting between two sprints, where the development team
discusses their inter-team dependencies. The scaled agile framework is run by the
development team members, who are best positioned to discuss inter-team dependencies
and find a solution.

65.Story estimation should be provided by whom in the team ?

Story points are relative measurements of the complexity of user stories. Story points
estimation is a team game, not a solo one. This task shouldn't be relegated to a single
person; instead, it's the whole team's responsibility.

66.When does a Sprint retrospective occur ?

After sprint review and prior to sprint planning.

67.When can SoS be used in Sprints or in scrum ecosystem ?

68.Kanban is suitable for which kind of project ?

Options-: support,design,projects where ambiguity is high, all of the above
Support project
Many teams, especially those in Lean and Agile IT organizations, rely on Kanban boards to
visualize, track, analyze, and measure their work.
69. How often is PI planning conducted ?
Every 8-12 weeks

70.Which of them is a part of development deliverables ?

71.Risk and issue tracking on project should happen in ?

JIRA

72.Who is responsible for priortising the backlog ?

The product owner

73.What is the output of risk planning?

PI Planning is a vital element of SAFe. It's a ceremony that brings together representatives
from every team to help them work together, decide on top features to work on next,
identify dependencies, and make a plan for the next Program Increment.

74.Which of the following iis not apillar of SCRUM ?

-Sustainability

75. Who ensures stories are ready for sprint planning?

-Product owner

76. How should be the project backlog arranged?

-High priority items should be listed at the top followed by low priority items.

77. Which tool have you used to plot end to end project plan?
- JIRA Roadmap
78.Risk and issue tracking should happen in?
-JIRA

79. Who is responsible for prioritizing the backlog?

-Product owner

80.What is the output of PI planning?

Options-:
a.Sprint velocity
b.

81.Agenda of Sprint retrospective?

- What went well, what needs improvement along with action items with due date/owners,
what did you learn this sprint.

82.Which of them is a part of design deliverables ?

Options-:
a.

83.Story estimation should be provided at which stage ?

Options-:
a.

84.Which statement describes the flow of work in scaled agile framework?

-It is a “push” system. It is “push” at the top and “pull” at the bottom.
85. In the scaled agile framework what is the role of enablers?
- They help extend the architectural runway.

86. A project has some major scrs that the team wants to mitigate. What is the best way to
monitor how well this effort is going ?
-Risk burndown chart

87. Who all the the participants in PI planning ?

-Only involves all members of the Agile release train including product owners, scrum
masters, developers, architect and other stakeholders.

88. What is Scrum of Scrums?

-It is a technique for two or more teams working together coordinate their efforts.

89. project status reporting can be made extremely accurate iif done through
-JIRA Dashboard

90.Who facilitates daily morning meeting?

-Scrum Master

91.Story estimation should be provided at which stage ?

-while product backlog grooming is in progress

92. An application is being implemented using sdlc. during what stage can the team perform
user acceptance testing for the application?
-During the deployment phase.
93. your organization is implementing SAFe and you are Release train engineer preparing for
a program increment planning event. the product owner provides long list of feautures and
there's limited time for prioritisatisation. what approach should you recommend?
Options-:
a.

94. During a sprint review the key stake holders in the project have given lots of suggestions
and some of these might change the work planned for the next sprint . what should the
scrum team do about these suggestions?
-Should take all the feedback and work with the product owner to decide which changes to
put in the to-do list for future work.

95. You are a scrum master leading a team with members from various domains and you're
about to do sprint planning in JIRA for a single story. the story is estimated at 3 story
points.What should you do with this information when conducting sprint planning?
-create subtasks for team members based on their strengths and expertise and assign them
along with target dates.

96.The sprint planning meeting is lasting longer than planned and the team is getting tired.
What should you do to help the team and stay on track?