Interview Q&A

Short answer: S, M, L, XL — useful for high-level estimation.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Definition: The Definition of Done is a shared understanding of what “done” means for a backlog item or Increment.

Explain a bit more

It ensures transparency and consistent quality. Impact on quality: Prevents incomplete work from being marked as finished. Reduces rework by setting clear expectations. Ensures the Increment is potentially shippable. Example DoD: Code is committed and peer-reviewed Unit tests are written and passed Integrated into CI/CD pipeline User story accepted by Product Owner No major bugs in QA Real-World Example: Without a DoD, a team may claim a feature is “done” even though it hasn’t been tested. With a proper DoD, it won’t be considered complete until it’s fully tested, reviewed, and accepted. Follow On:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Purpose: To inspect the Increment and adapt the Product Backlog based on feedback.

Explain a bit more

It’s a collaborative working session, not a demo-only meeting. Key components: Presentation of what was "Done" in the Sprint. Discussion on what went well and challenges faced. Stakeholder feedback on the Increment. Review of the market or business context. Real-World Example: The team presents a new analytics dashboard to stakeholders. Marketing suggests a change in how data is grouped. The Product Owner logs this feedback into the Product Backlog for future refinement.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A Sprint is a fixed-length (usually 1–4 weeks) timebox where a usable and potentially shippable product increment is developed.

Explain a bit more

The Sprint fosters focus, regular delivery, and continuous improvement. Example: A digital agency might run 2-week Sprints to deliver iterative updates to a client’s website. After each Sprint, the client gets a working piece — such as a new landing page — and provides feedback that shapes the next Sprint.

Real-world example (ShopNest)

ShopNest team runs 2-week sprints. Daily standup is blockers-only, not a status novel.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: login screen might be estimated as a 3-point story. A password reset flow involving emails nd error handling might be 5 points. Follow On:

Real-world example (ShopNest)

“Add UPI” is a story with acceptance criteria. Points reflect effort/risk, not days on a calendar.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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.

Real-world example (ShopNest)

ShopNest team runs 2-week sprints. Daily standup is blockers-only, not a status novel.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Scrum-of-Scrums (SoS) is a coordination mechanism where representatives from multiple Scrum teams meet regularly to discuss progress, dependencies, and blockers.

Explain a bit more

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.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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.

Real-world example (ShopNest)

ShopNest team runs 2-week sprints. Daily standup is blockers-only, not a status novel.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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:

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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.

Explain a bit more

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.

Real-world example (ShopNest)

ShopNest team runs 2-week sprints. Daily standup is blockers-only, not a status novel.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

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

Real-world example (ShopNest)

ShopNest team runs 2-week sprints. Daily standup is blockers-only, not a status novel.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Aspect 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…

Explain a bit more

planned before a brick is laid. In Scrum, like in software development, teams build part of the system, get feedback, and adapt — like adding a new feature based on early user testing.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short 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%.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

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

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Spotify’s model is not a framework but a cultural model inspired by Agile/Scrum, focusing on autonomy, alignment, and innovation.

Explain a bit more

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.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: For small teams (3–5): Communication is simpler.

Explain a bit more

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.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A Product Increment is the sum of all work completed in the Sprint that meets the Definition of Done.

Explain a bit more

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:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Purpose: The Sprint Goal provides focus and alignment for the team.

Explain a bit more

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

Real-world example (ShopNest)

ShopNest team runs 2-week sprints. Daily standup is blockers-only, not a status novel.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short 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%.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: 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.

Explain a bit more

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.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

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

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

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

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Best practices: Identify and visualize dependencies during PI Planning or Sprint Planning.

Explain a bit more

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.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Meaningful metrics: Velocity (story points per Sprint): Trend, not target.

Explain a bit more

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.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A 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…

Real-world example (ShopNest)

“Add UPI” is a story with acceptance criteria. Points reflect effort/risk, not days on a calendar.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.