Interview Q&A

Short answer: Aspect Scrum Kanban Extreme Programming (XP) Framework Type Prescriptive, timeboxed (Sprints) Flow-based, continuous delivery Engineering-focused Agile methodology Roles PO, Scrum Master, Dev Team No defined roles Coach, Developer, Customer (on-site) Work Planning Sprint Backlog (2–4 weeks) Continuous pull from board Iterations, similar to Sprints Change Policy No changes during a Sprint Changes allowed anytime…

Explain a bit more

Change-resistant within iteration Focus Delivery + team process Visualizing flow and limiting WIP Code quality and engineering discipline Practices Daily Scrum, Sprint Planning, Review, Retro Visual board, WIP limits, Cycle Time Pair programming, TDD, CI/CD, Refactoring Example: A support team may prefer Kanban for flexibility, while a product dev team building new features might favor Scrum or XP for structure and code quality practices.

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: Follow On: Definition: The Product Backlog is an ordered list of everything that might be needed in the product, serving as the single source of work for the Scrum Team.

Explain a bit more

How to maintain it: Continuously refine items for clarity, detail, and priority. Regularly update it based on feedback, market changes, and stakeholder input. Collaborate with the team to ensure shared understanding. Real-World Example: For a streaming platform, the backlog might start with high-level features like “Watchlist” and “User Reviews”. As sprints progress, these are broken down into more detailed items like “Add to Watchlist Button” or “Review Moderation Rules”.

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: Sprint Planning sets the direction for the upcoming Sprint.

Explain a bit more

The team collaboratively decides what can be delivered and how the work will be accomplished. Key outcomes: A clear Sprint Goal. A selected set of Product Backlog Items (PBIs) for the Sprint. A high-level plan for delivering those items. Real-World Example: In a team building a customer support chatbot, the Product Owner presents the most valuable backlog items. The team discusses capacity and agrees to focus on implementing “Chatbot FAQ logic” and “User intent recognition.” These become the Sprint backlog.

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: travel app team uses Value vs. Effort to prioritize. “In-app booking” has high value and moderate effort, while “Flight status tracking” has high effort and low impact — so the former gets scheduled first.

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

Explain a bit more

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.

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

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: User Story describes a feature from the end-user’s perspective. It answers: Who wants it?

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: Definition: A Product Owner Team is a group of Product Owners (or PO + Product Managers) who collaboratively manage a complex or large product backlog.

Explain a bit more

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.

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: A User Story describes a feature from the end-user’s perspective.

Explain a bit more

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

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: The Scrum Master facilitates, coaches, and removes obstacles.

Explain a bit more

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.

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: The Product Owner (PO) is the voice of the customer and is responsible for: Defining and prioritizing the Product Backlog.

Explain a bit more

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:

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

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: The Development Team is responsible for: Delivering a potentially shippable increment at the end of each Sprint.

Explain a bit more

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.

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

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: Contains all endpoints, request/response formats, parameters, headers, and security details. Acts as a contract between client and server. Used for auto-generating documentation, client SDKs, and mock servers.

Real-world example (ShopNest)

ShopNest exposes REST APIs for cart and checkout. Controllers stay thin; business rules live in application services.

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: RAML (RESTful API Modeling Language) → YAML-based specification for APIs. Focuses on design-first API approach. Differences with OpenAPI/Swagger: RAML is more design-oriented; Swagger is implementation-oriented. OpenAPI has better tooling support and community adoption.

Real-world example (ShopNest)

ShopNest exposes REST APIs for cart and checkout. Controllers stay thin; business rules live in application services.

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: Postman is a GUI tool for testing REST APIs. Features: Send HTTP requests (GET, POST, PUT, DELETE). Automate tests using Postman Collections. Generate documentation and mock servers. Supports environment variables and CI/CD integration.

Real-world example (ShopNest)

Creating an order is POST /api/orders → 201 with Location header. Fetching is GET /api/orders/{id} → 200 or 404.

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: PIs? Return a structured JSON response with: status → HTTP status code error → Short message details → Optional for debugging { "status": 400, "error": "Bad Request", "details": "Email is required" }

Real-world example (ShopNest)

Creating an order is POST /api/orders → 201 with Location header. Fetching is GET /api/orders/{id} → 200 or 404.

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: Return a structured JSON response with: status → HTTP status code error → Short message details → Optional details for debugging

Example code

{ "status": 400, "error": "Bad Request", "details": "Email field is required" }

Real-world example (ShopNest)

Creating an order is POST /api/orders → 201 with Location header. Fetching is GET /api/orders/{id} → 200 or 404.

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.