Interview Q&A

Definition:

A User Story describes a feature from the end-user’s perspective. It answers: Who wants

it? What do they want? Why do they want it?

Template:

As a [type of user], I want [some goal], so that [some reason].

Best practices:

• Add Acceptance Criteria to clarify expectations.
• Keep it concise, focused, and testable.

Follow On:

Example:

As a shopper, I want to filter products by price range, so I can find items within

my budget.

Acceptance Criteria:

• Price slider from $0–$500
• Real-time update of results
• Works on mobile and desktop

Purpose:

To keep the Product Backlog clean, prioritized, and well-understood by the team — ensuring

future Sprints run smoothly.

Best practices:

• Held once or twice per Sprint (not an official Scrum event, but crucial).
• Timebox to avoid fatigue (e.g., 1 hour per week).
• Break down large items (epics) into smaller, actionable stories.
• Clarify acceptance criteria and estimate effort.

Real-World Example:

Before Sprint Planning, the team refines a story called “Implement Dark Mode” by

discussing UI implications, dependencies, and edge cases. They split it into smaller tasks

like “UI toggle”, “Theme handler”, and “User preference saving”.

The Scrum Master facilitates, coaches, and removes obstacles. Unlike a traditional project

manager, they don’t assign tasks or manage timelines.

Scrum Master Project Manager

Facilitates Scrum practices Manages scope, schedule, and

budget

Focuses on team dynamics and

coaching

Focuses on deliverables and

deadlines

Servant leader Authority figure

Example:

If a developer is stuck due to a permissions issue, the Scrum Master will help resolve it. A

project manager might instead adjust timelines or escalate to keep the schedule on track.

pproaches:

• Embed NFRs into acceptance criteria.
• Use technical enabler stories to address infrastructure or performance needs.
• Define NFR-related checklists in DoD.

Example:

For a fintech app, performance NFRs (e.g., “page load < 2 sec”) are part of every story's

DoD. Security is validated through automated scans in CI/CD.

Answer: university uses Scrum to develop an online learning program. In each Sprint, they deliver lesson modules, gather student feedback, and adjust content and format accordingly.

What interviewers expect

• A clear definition tied to Agile in Agile & Scrum projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Agile & Scrum application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Agile & Scrum architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Non-Functional Requirements (NFRs) like security, performance, and scalability are

treated as part of the Definition of Done (DoD) or explicitly captured in stories or tasks.

Approaches:

• Embed NFRs into acceptance criteria.
• Use technical enabler stories to address infrastructure or performance needs.
• Define NFR-related checklists in DoD.

Example:

For a fintech app, performance NFRs (e.g., “page load < 2 sec”) are part of every story's

DoD. Security is validated through automated scans in CI/CD.

Scrum is great wherever work is complex and iterative. Examples include:

• Marketing – Running campaigns in Sprints, delivering creative content.
• Education – Iteratively building course content or programs.
• Construction Design – Designing in phases, validating with stakeholders.
• Product Design – Developing prototypes and refining via feedback.

Real-World Example:

A university uses Scrum to develop an online learning program. In each Sprint, they deliver

lesson modules, gather student feedback, and adjust content and format accordingly.

Common estimation techniques:

What interviewers expect

• A clear definition tied to Agile in Agile & Scrum projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Agile & Scrum application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Agile & Scrum architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Follow On:

Common pitfalls:

• Overcommitting based on optimism, not team capacity.
• No clear Sprint Goal, leading to scattered efforts.
• PO not prepared, causing delays or confusion.
• Ignoring team availability (e.g., vacations, holidays).
• Skipping task breakdown, leading to unclear work.

How to avoid:

• Come prepared with a refined backlog.
• Use velocity or past Sprint performance as a guide.
• Define a meaningful Sprint Goal.
• Factor in team availability.

The Product Owner (PO) is the voice of the customer and is responsible for:

• Defining and prioritizing the Product Backlog.
• Maximizing value delivered by the team.
• Making trade-off decisions between features, cost, and time.

Example:

In a fintech app team, the PO decides that user onboarding is more critical than the referral

program, so it’s prioritized in the backlog. This ensures the team focuses on what's most

valuable for launch.

Follow On:

Answer: fter frequent issues with legacy code, a team estimates and logs 5 technical debt stories, prioritizing the worst ones during each Sprint.

What interviewers expect

• A clear definition tied to Agile in Agile & Scrum projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Agile & Scrum application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Agile & Scrum architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: fter a demo, a stakeholder suggests a visual improvement to a dashboard. The team doesn't implement it immediately but adds it to the backlog and addresses it in the next Sprint.

What interviewers expect

• A clear definition tied to Agile in Agile & Scrum projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Agile & Scrum application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Agile & Scrum architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: team working on a healthcare dashboard decides among themselves who takes on UI, backend, and testing tasks — without needing direction from a manager — and ensures the code is production-ready by Sprint’s end.

What interviewers expect

• A clear definition tied to Agile in Agile & Scrum projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Agile & Scrum application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Agile & Scrum architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Follow On:

Ways to measure and manage technical debt:

• Code quality tools (SonarQube, CodeClimate)
• Automated test coverage
• Bug rates and frequency of rework
• Velocity trends — slowed delivery may indicate rising debt
• Team feedback in Retrospectives

Make it visible:

• Track known debt in the Product Backlog.
• Reserve capacity every Sprint to pay it down.

Example:

After frequent issues with legacy code, a team estimates and logs 5 technical debt stories,

prioritizing the worst ones during each Sprint.

During the Sprint:

• Feedback is captured but doesn’t change the current Sprint scope.
• Product Owner logs feedback in the Product Backlog.
• Team might discuss it in refinement sessions or plan to act on it in the next Sprint.

Follow On:

During Sprint Review:

• Stakeholders review the Increment.
• Discuss what’s useful, missing, or needs improvement.
• PO adjusts priorities accordingly.

Example:

After a demo, a stakeholder suggests a visual improvement to a dashboard. The team

doesn't implement it immediately but adds it to the backlog and addresses it in the next

Sprint.

Epics:

• Large, high-level features or initiatives that are too big for a single Sprint.
• Broken down into User Stories for implementation.

Relationship:

Epic → Multiple User Stories → Tasks (optional)

Example:

Epic: “User Account Management”

User Stories:

• As a user, I want to register with email.
• As a user, I want to log in with my credentials.
• As a user, I want to reset my password.

Each of these stories can be completed in a separate Sprint and delivered incrementally.

Tips to make Sprint Reviews impactful:

• Invite the right stakeholders (not just managers).
• Demonstrate working software, not just talk.
• Encourage interactive feedback — make it a conversation.
• Revisit progress toward the Product Goal.
• Align changes with business outcomes.

Follow On:

Real-World Example:

In a Sprint Review for a booking app, stakeholders suggested that date filters were

unintuitive. The team took this feedback and adjusted the UI in the next Sprint, improving

user satisfaction.

The Development Team is responsible for:

• Delivering a potentially shippable increment at the end of each Sprint.
• Self-organizing how they accomplish the work.
• Collaborating closely and maintaining quality.

Example:

A team working on a healthcare dashboard decides among themselves who takes on UI,

backend, and testing tasks — without needing direction from a manager — and ensures the

code is production-ready by Sprint’s end.

Burndown Chart is a visual tool that shows the remaining work in a Sprint or project

over time.

Purpose:

• Helps teams monitor progress toward completing the Sprint backlog.
• Enables early identification of scope creep or falling behind.

Follow On:

How to use:

• X-axis: Days in Sprint
• Y-axis: Remaining effort (usually in story points or hours)
• Ideal line vs. actual line

Example:

Midway through a Sprint, a team sees the burndown flatlining (no work is getting “done”).

This prompts a conversation — they discover a blocker in API access and address it before

the Sprint is derailed.

Scrum Implementation & Best

Practices:

team felt retrospectives were repetitive. The Scrum Master tried a “Team Radar” activity to

visualize team health across areas like collaboration and quality. This revealed deeper

issues and sparked more meaningful discussions.

Scrum Artifacts:

lignment strategies:

• Define and communicate a clear Product Vision.
• Use Sprint Goals that tie directly to business outcomes.
• Conduct Sprint Reviews with real stakeholders to validate direction.
• Use OKRs (Objectives & Key Results) at a program or portfolio level.
• Empower POs to make value-driven decisions, not just task prioritization.

Example:

If the business goal is to increase user retention, Sprint Goals focus on improving

Follow On:

onboarding UX and reducing churn. Sprint Reviews showcase progress toward these

objectives.

Follow On:

Challenge How to Overcome

Unclear roles Provide clear Scrum training; reinforce roles (PO, SM, Dev

Team).

Lack of stakeholder

engagement

Involve them in Sprint Reviews, show working software

regularly.

Poor backlog refinement Schedule regular grooming sessions with the PO and

team.

Unrealistic expectations Educate stakeholders on sustainable pace and team

velocity.

Team silos Promote cross-skilling and shared ownership of work.

Skipping retrospectives Prioritize continuous improvement by making retros

engaging and action-focused.

Micromanagement Empower teams to self-organize; educate managers on

agile leadership.

Follow On:

Advanced Scrum & Scaling:

Definition:

A Burndown Chart is a visual tool that shows the remaining work in a Sprint or project

over time.

Purpose:

• Helps teams monitor progress toward completing the Sprint backlog.
• Enables early identification of scope creep or falling behind.

Follow On:

How to use:

• X-axis: Days in Sprint
• Y-axis: Remaining effort (usually in story points or hours)
• Ideal line vs. actual line

Example:

Midway through a Sprint, a team sees the burndown flatlining (no work is getting “done”).

This prompts a conversation — they discover a blocker in API access and address it before

the Sprint is derailed.

Scrum Implementation & Best

Practices:

Best practices:

• Rotate formats to keep things fresh.
• Foster psychological safety — no blaming.
• Use data and facts (velocity, defect rates) to ground discussions.
• Focus on 1-2 action items, not a wish list.
• Follow up — review actions in the next Retrospective.

Popular formats:

• Start / Stop / Continue
• Mad / Sad / Glad
• 4Ls (Liked, Learned, Lacked, Longed for)

Real-World Example:

A team felt retrospectives were repetitive. The Scrum Master tried a “Team Radar” activity to

visualize team health across areas like collaboration and quality. This revealed deeper

issues and sparked more meaningful discussions.

Scrum Artifacts:

These values create a strong foundation for effective teamwork:

• Commitment – Teams commit to goals and deliverables.
• Courage – Members speak up about challenges and take initiative.
• Focus – Everyone stays aligned on Sprint goals.
• Openness – Honest communication about progress and problems.
• Respect – Valuing everyone's contribution fosters trust.

Example:

In a high-pressure release, a developer admits they’re falling behind. Instead of assigning

blame, the team rallies to support — pair programming to stay on track. That’s Scrum values

in action.

Follow On:

Scrum Ceremonies: