Interview Q&A

For small teams (3–5):

• Communication is simpler.
• Roles may overlap more (e.g., devs test their own work).

For larger teams (8+):

• Consider splitting into multiple Scrum Teams working on the same product, aligned

by a Scaled Scrum approach (e.g., Nexus, LeSS).

• Use communities of practice for specialized skill-sharing.

Follow On:

For varied skillsets:

• Promote cross-training to reduce silos.
• Use pair programming, knowledge sharing sessions, and code walkthroughs.

Example:

In a team with only one QA, developers start writing automated tests and review each

other’s code to balance the workload.

Product Increment is the sum of all work completed in the Sprint that meets the

Definition of Done.

Ways to measure:

• Functionality delivered (e.g. completed features)
• Business value delivered (e.g. increase in conversions)
• Quality metrics (e.g. defect rates, test coverage)
• Velocity (amount of work delivered compared to previous Sprints)

Example:

In a SaaS platform, the Sprint delivered “Export to CSV” and “Custom Reports”. These

features are measured by tracking how many users adopt them post-release and how much

support ticket volume drops.

Follow On:

Answer: Real-World Example: After noticing last-minute testing rushes, the team agrees to integrate testing into the daily workflow. Next Sprint, they try pairing QA early with devs, reducing defects by 30%.

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.

Scrum fosters continuous improvement through:

• Sprint Retrospective – A dedicated meeting at the end of each Sprint to reflect on

what went well and what can be improved.

• Empowered Teams – Teams are encouraged to experiment and adapt their process.
• Transparency and Inspection – Constant review of progress and adaptation as

needed.

Example:

After noticing delays in code reviews, a team agrees in the Retrospective to set aside daily

time for peer reviews. In the next Sprint, turnaround time improves noticeably.

Answer: team’s velocity drops — but it’s because they started writing more automated tests. The focus remains on sustainable delivery, not chasing numbers.

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: product team building a CRM system receives new legal requirements for data handling. Instead of derailing the project, the Product Owner updates the backlog, and the team includes those changes 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.

Best practices:

• Identify and visualize dependencies during PI Planning or Sprint Planning.
• Use Dependency Boards or digital tools (e.g., Jira Advanced Roadmaps).
• Cross-team backlog refinement to surface risks early.
• Encourage cross-functional teams to reduce external dependencies.
• Establish Integration Sprints or teams, if needed.

Example:

In a large retail company, multiple teams need the same API updates. A shared backlog,

joint planning sessions, and dedicated integration owners reduce surprises.

Meaningful metrics:

• Velocity (story points per Sprint): Trend, not target.
• Sprint Goal success: Did the team meet their goal?
• Lead Time / Cycle Time: Time from idea to delivery.
• Quality metrics: Bugs found, escaped defects.
• Team health: Engagement, collaboration, and satisfaction.

Caution: Avoid weaponizing metrics. They’re for continuous improvement, not judgment.

Example:

A team’s velocity drops — but it’s because they started writing more automated tests. The

focus remains on sustainable delivery, not chasing numbers.

well-formed backlog item (often a User Story) should be:

✅ INVEST:

• Independent – Can be developed separately
• Negotiable – Not a fixed contract
• Valuable – Delivers user or business value
• Estimable – Team can estimate its size
• Small – Can be completed within a Sprint
• Testable – Has clear acceptance criteria

Example:

Poor: “Fix bugs”

Better: “As a user, I want error messages when login fails, so I know why I can’t access my

ccount.”

Scrum embraces change by:

• Allowing the Product Backlog to be continuously refined and reprioritized.
• Keeping Sprints short, so changes can be incorporated in the next cycle.
• Fostering close communication between stakeholders and the team.

Follow On:

Example:

A product team building a CRM system receives new legal requirements for data handling.

Instead of derailing the project, the Product Owner updates the backlog, and the team

includes those changes in the next Sprint.

Best practices:

• Daily Scrum encourages daily alignment.

Follow On:

• Task ownership is flexible — any team member can pick tasks.
• Use shared goals (Sprint Goal) instead of individual targets.
• Foster a safe environment for asking questions and learning.
• Encourage pairing between devs, designers, testers, etc.

Example:

In a team building a healthcare dashboard, developers work closely with UX designers to

ensure usability and compliance, reviewing designs together before coding begins.

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”.

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.

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.

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.

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: