Interview Q&A

Scrum-of-Scrums (SoS) is a coordination mechanism where representatives from multiple

Scrum teams meet regularly to discuss progress, dependencies, and blockers.

Structure:

• Each team sends a delegate (often the Scrum Master or a dev lead).
• Frequency varies (e.g., 2–3 times/week).
• Focus is on cross-team coordination, not status reporting.

Example agenda:

• What has your team completed?
• What will your team work on next?
• Are there any blockers or dependencies?

Example:

In a bank's digital transformation project, five Scrum teams are building different modules of

the same app. SoS meetings align delivery and resolve integration issues early.

The Product Owner:

• Continuously refines the Product Backlog — even during a Sprint.
• Works with stakeholders and the team to break down large items.
• Clarifies acceptance criteria.
• Re-prioritizes based on new insights.

Example:

Mid-Sprint, the PO learns from sales that customers are struggling with onboarding. They

update the backlog by splitting “User Onboarding Flow” into smaller, clearer stories for the

next Sprint.

Preferred method:

Most agile teams favor Story Points with Planning Poker to foster team discussion and

build consensus.

Example:

A login screen might be estimated as a 3-point story. A password reset flow involving emails

and error handling might be 5 points.

Follow On:

Definition:

The Sprint Backlog is a subset of Product Backlog items the team commits to deliver in a

Sprint, plus a plan for how to achieve it.

How to manage it:

• Keep it visible and up to date (via a Scrum board or tool like Jira).
• Break down items into tasks during Sprint Planning.
• Update daily during stand-ups based on progress.
• Add tasks if necessary, but don’t change Sprint scope without discussion.

Example:

A team uses a Kanban board with “To Do”, “In Progress”, and “Done” columns. Every day,

they update task statuses so progress is clear and blockers are quickly identified.

Answer: Purpose: To reflect on the Sprint and identify process improvements for the next iteration. Structure (commonly used): Follow On:

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.

spect Scrum Traditional (Waterfall)

Process Style Iterative and incremental Sequential and linear

Requirements Evolve over time Defined upfront

Follow On:

Team Involvement Cross-functional, collaborative Role-specific, hierarchical

Flexibility to Change High — welcomes changes Low — changes can be

costly

Delivery Frequent, every Sprint At the end of the project

Example:

In traditional construction, everything is planned before a brick is laid. In Scrum, like in

software development, teams build part of the system, get feedback, and adapt — like

dding a new feature based on early user testing.

Answer: fter 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.

Answer: fter 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.

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.

Spotify’s model is not a framework but a cultural model inspired by Agile/Scrum, focusing

on autonomy, alignment, and innovation.

Key concepts:

• Squads = Scrum Teams
• Tribes = Collection of related Squads
• Chapters = Discipline-focused groups (e.g., QA Chapter)
• Guilds = Interest-based communities (e.g., DevOps Guild)

Follow On:

Emphasis on:

• Autonomy with accountability
• Servant leadership
• Agile mindsets over strict roles

Example:

Each Squad at Spotify decides its own tools and ways of working but is aligned on broader

goals and architecture via Tribes and Chapters.

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:

Purpose:

The Sprint Goal provides focus and alignment for the team. It serves as a shared

objective for the Sprint, guiding decisions and trade-offs.

Defining a good Sprint Goal:

• Collaboratively set during Sprint Planning.
• Clear, concise, and focused on outcome, not just output.
• Tied to business or customer value.

Example:

Instead of “build three reports,” a better Sprint Goal would be:

✅ “Enable users to access key sales insights through interactive reports.”

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

spect Product Backlog Sprint Backlog

Follow On:

Owner Product Owner Development Team

Scope All desired features, bugs,

enhancements

Items selected for current Sprint

Timefram

Long-term, evolves continuously Short-term, Sprint-specific

Content Prioritized list of user

stories/features

Detailed tasks and plan for delivering

them

Example:

The Product Backlog includes “User Profile Page”, “Email Notifications”, “2FA Setup”. For

Sprint 4, the team selects “Email Notifications” and breaks it into tasks like “Create email

template”, “Setup backend service”, etc., forming the Sprint Backlog.

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.

Product Owner Team is a group of Product Owners (or PO + Product Managers) who

collaboratively manage a complex or large product backlog.

You need it when:

Follow On:

• The product is large or has multiple subcomponents.
• Multiple Scrum teams work on shared features or user journeys.
• Work spans multiple markets, compliance zones, or personas.

Structure:

• Chief Product Owner (overarching vision)
• POs for feature areas or team-specific backlogs
• Shared roadmap and prioritization process

Example:

For an enterprise SaaS platform with HR, Finance, and Compliance modules, each module

has a dedicated PO, coordinated by a Chief PO.

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:

s 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:

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

my budget.

cceptance Criteria:

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

Definition:

A Product Owner Team is a group of Product Owners (or PO + Product Managers) who

collaboratively manage a complex or large product backlog.

You need it when:

Follow On:

• The product is large or has multiple subcomponents.
• Multiple Scrum teams work on shared features or user journeys.
• Work spans multiple markets, compliance zones, or personas.

Structure:

• Chief Product Owner (overarching vision)
• POs for feature areas or team-specific backlogs
• Shared roadmap and prioritization process

Example:

For an enterprise SaaS platform with HR, Finance, and Compliance modules, each module

has a dedicated PO, coordinated by a Chief PO.

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.