COGNIZANT

1. What differentiates you from other SMs?

I focus on enabling high-performing teams through empathy, active coaching, and fostering
a culture of continuous improvement. My ability to balance delivery with people-centric
leadership allows teams to evolve and become self-organized.

2. How would you get to know the vibe/ pulse of the team?

By building trust through one-on-one conversations, observing team dynamics during

ceremonies, and using tools like team health checks, anonymous surveys, and retrospectives
to get honest feedback.

3. How do you manage stakeholders in a cross-functional team?

I maintain transparent communication through regular sync-ups, align stakeholder

expectations via backlog grooming, and promote shared goals using visible metrics and
status updates.

4. Suppose there is a very senior member in the team and he is openly saying that
you do not know anything about Scrum. How would you handle this situation?

I would respond calmly, invite them to a one-on-one discussion, understand their concerns,
and reinforce my role by demonstrating Scrum values. I’d focus on building mutual respect
and invite collaboration rather than confrontation.

5. How often do you do retro? What resistances you faced in the retro and tell the
flow of the retro?

Retros are held at the end of every sprint. Common resistances include lack of engagement
or fear of blame. I use techniques like Start-Stop-Continue or 4Ls to keep it engaging. Flow:
Set the stage, gather data, generate insights, decide actions, and close the retro.

6. How do you differentiate between scrum, kanban and SAFe when you have to
implement an agile framework?

Scrum is time-boxed and focused on sprints; Kanban emphasizes continuous flow and WIP
limits; SAFe scales Agile across the enterprise. I choose based on team size, workflow nature,
and organizational goals.

7. What challenges did you face during Agile transformation?

Resistance to change, lack of Agile mindset, and role clarity. I addressed them with training,
coaching, and showcasing small wins to build momentum.

8. You join a new project as a SM what is the first thing you would do in terms of
agile?
I assess team maturity, clarify roles, align with the Product Owner, understand the product
vision, and begin with establishing the Scrum framework through training or workshops.

9. PO adds a prod issue in between the sprint, how would you handle the situation?

I’d evaluate the urgency with the Product Owner. If it's critical, I’d involve the team to assess
impact and possibly replace a lower-priority item. Otherwise, it goes to the backlog.

SIGNIFY

10. What approach will you apply for tracking the project's financial health?

Use earned value management (EVM), track planned vs. actuals, and integrate burn-down
with cost tracking tools.

11. How will you reduce the cost variance?

By identifying scope creep, enhancing productivity, eliminating wasteful processes, and

ensuring cross-functional efficiency.

12. How will you apply a governance framework for your team when it is totally new to
the project?

Introduce roles, responsibilities, sprint cadences, and clear escalation protocols. Conduct
Agile training and establish ceremonies.

13. What are KPI indicators?

Key Performance Indicators (KPIs) are metrics used to evaluate team performance.
Examples: sprint velocity, lead time, defect leakage, team engagement, and customer
satisfaction.

High-Priority Scenario-Based Questions

1. Multiple stakeholders push for their features to be prioritized — how do you

handle it?

As a Scrum Master, I facilitate backlog prioritization discussions between stakeholders and

the Product Owner, emphasizing business value, alignment with the product vision, and
sprint goals. I encourage techniques like MoSCoW or WSJF, ensuring transparency and
consensus while protecting the team from undue pressure.

MoSCoW Prioritization

MoSCoW stands for:

  M – Must have
These are non-negotiable requirements. The product cannot function or be
considered complete without them.

 S – Should have
Important but not vital. These can be left out for a short time if needed, but should
be included if possible.

 C – Could have
Desirable but not necessary. These add value at little cost or risk.

 W – Won’t have (this time)

Agreed to be excluded in this release or sprint but may be considered for future
versions.

When to use:
Use MoSCoW when you want a simple and qualitative way to rank features, especially
during sprint or release planning.

WSJF – Weighted Shortest Job First

WSJF is a quantitative prioritization model used in SAFe (Scaled Agile Framework) to deliver
maximum value in the shortest time.

Formula:

WSJF=Cost of DelayJob Duration or Size\text{WSJF} = \frac{\text{Cost of Delay}}{\text{Job

Duration or Size}}WSJF=Job Duration or SizeCost of Delay

Cost of Delay is calculated by adding:

 User-business value: How much value it delivers to the customer or business.

 Time criticality: How urgent it is.

 Risk reduction and/or opportunity enablement: Will it remove risks or unlock future
value?

Job Size: Estimated effort or time to complete the task.

Example:

Feature Business Value Time Criticality Risk Reduction Job Size Cost of Delay WSJF Score

Feature A 10 8 6 4 24 6.0

Feature B 6 5 5 2 16 8.0

Feature B would be prioritized over Feature A due to a higher WSJF score.

MoSCoW vs WSJF Comparison

Criteria MoSCoW WSJF

Type Qualitative Quantitative

Best for Smaller projects, quick planning Scaled Agile, large initiatives

Decision Basis Stakeholder input, priority Value vs. Effort trade-off

Level of Complexity Simple Requires estimation and calculation

Visual Output Category list Numerical scores

2. A stakeholder requests an urgent feature mid-sprint — what do you do?

I guide the Product Owner and team to assess its urgency. If it’s critical, the Product Owner
may re-prioritize or, in extreme cases, cancel the sprint. Otherwise, it’s added to the backlog
for future planning. I ensure the team remains focused on the current Sprint Goal.

3. How do you ensure the team understands the business context of their work?

I facilitate direct communication with the Product Owner and stakeholders, encourage the
use of user stories with clear business value, and promote sprint goals tied to product vision.
Regular refinement, sprint reviews, and shared roadmaps ensure clarity.

4. Stakeholders are dissatisfied during a Sprint Review — how do you handle it?

I encourage open feedback and guide the team and PO to listen constructively. I ensure the
feedback is documented and reflected in backlog refinement. Any misalignment is discussed
in the retrospective to prevent recurrence.

5. Team identifies technical debt mid-sprint — it’s outside the sprint scope. What do
you do?

I help the team document it clearly and work with the Product Owner to add it to the
backlog. During refinement, I support prioritizing it based on long-term product health,
ensuring future sprints account for this debt.

6. A team member is resistant to Scrum practices — how do you address it?

I have a one-on-one to understand their concerns, offer coaching on Agile benefits, and
involve them in decision-making. I encourage team ownership to gradually shift their
mindset toward Agile.

7. Sprint commitments are frequently missed — how do you address it?

I analyze trends through retrospectives and metrics (e.g., velocity, capacity planning). I work
with the team to improve estimation accuracy, reduce scope pressure, and introduce
realistic planning.

8. A developer constantly overestimates tasks — what do you do?

I address this privately, review the estimation process, and introduce relative sizing methods
like Planning Poker to normalize estimates through team consensus.

9. A team member is dominating estimations — how do you handle this?

I emphasize collaborative estimation methods like Planning Poker or T-shirt sizing, where
everyone participates equally. I coach the team on psychological safety and respectful
communication.

10. A team member avoids attending Scrum ceremonies — how do you persuade
them?

I speak with them privately to understand their reasons, explain the purpose of each
ceremony, and highlight how their presence supports team success. If needed, I tailor
ceremonies to be more engaging or concise.

11. You face a conflict between team members — how do you handle it?

I act as a neutral facilitator, holding private and joint discussions. I encourage empathy, use
conflict resolution techniques (e.g., win-win negotiation), and focus on team goals over
personal differences.

12. Product Owner is unavailable during sprint planning — what do you do?

I work with the team to refine available, high-priority stories using existing backlog and
ensure sprint planning proceeds with minimal disruption. I update the PO afterward and
seek preventive alignment going forward.

13. Product Owner assigns a story at the end of sprint — do you accept it?

No. Unless it’s a critical bug, I coach the PO to avoid mid-sprint scope changes and move the
story to the next sprint backlog.

14. You discover spillover user stories in multiple sprints — what do you do?

I review causes with the team in retrospectives, adjust capacity planning, and improve
backlog refinement. I work with the PO to prioritize spillover and ensure sustainable pacing.

15. Your team has inconsistent velocity — how do you stabilize it?

I analyze causes such as changing team capacity, unclear requirements, or overcommitment.

I use consistent story point estimation, track actual capacity, and avoid last-minute scope
changes.
 16. A critical bug is found in production mid-sprint — what do you do?

I work with the PO and team to evaluate urgency. If it’s critical, we may bring it into the
sprint by replacing another story. Otherwise, it’s added to the backlog.

17. Team is not engaged in retrospectives — how do you make it effective?

I rotate formats (e.g., Start-Stop-Continue, 4Ls, Sailboat), use anonymous feedback,

celebrate wins, and focus on actionable improvements to increase participation.

18. You’re asked to act as both SM and PO — how do you manage it?

I explain the conflict of interest and recommend dividing responsibilities. If unavoidable, I

maintain transparency, involve team members in prioritization, and ensure dual roles don’t
hinder collaboration.

19. Team feels burnout due to high sprint pressure — what do you do?

I raise the concern in retrospectives and leadership meetings, adjust sprint commitments,
promote sustainable pacing, and protect the team from unrealistic deadlines.

20. Stakeholders give conflicting feedback in review — how do you handle it?

I facilitate a discussion to align on product goals, help the PO synthesize feedback into
backlog items, and prioritize based on business value.

Scrum Principles
📌Not just what to do, but why we do it.

Role Responsibilities
📌Coach, servant-leader, impediment remover… wear all the hats.

Conflict Resolution
📌 Because dysfunction doesn't fix itself.

Scrum Ceremonies
📌 Facilitate with purpose, not just check the boxes.

Team Success Measurement

📌 Burnups, velocity, happiness metrics—what really matters?

Meeting Facilitation
📌 Drive focus and outcomes, not fatigue.

Agile Adoption Support

📌 Help teams transition with empathy and clarity.
Challenging Situations
📌 Navigate tough conversations and change resistance.

And more…

Being a Scrum Master is not about running meetings.

It’s about creating impact.