Autocoder

SDLC and Agile Interview Questions

Last updated 2026-11-19

Service companies and campus drives often include a short software engineering round, where the questions are about process: the phases of the SDLC, why teams use Agile, who does what in Scrum and how a sprint is planned. These are easy marks for a prepared candidate and common stumbling blocks for one who only revised algorithms. This page gives precise answers and a worked velocity calculation.

The technical rounds around it are covered in how to crack a technical interview, and the design topics in OOPs questions and low-level design questions. For delivery pipelines see microservices questions.

TopicsSDLC models, Scrum, Kanban, testing, CI/CD
LevelEasy to medium
Typical roundTechnical or managerial interview

Scrum vocabulary in one place

Worked example: forecasting with velocity

A team completed 20, 24 and 22 story points in its last three sprints, so its average velocity is 22 points per sprint. The remaining backlog is 110 points, so the forecast is 110 divided by 22, which is 5 sprints. Velocity is a planning aid for one team, not a measure of productivity, and comparing velocity between teams is meaningless because story points are relative to each team.

SDLC and Agile Interview Questions: questions with worked answers

  1. 1

    What is the SDLC and what are its phases?

    easy

    The software development life cycle is the structured process for building software. The usual phases are requirement analysis, design (architecture and detailed design), implementation (coding), testing, deployment and maintenance. Each phase has outputs: a requirements specification, design documents, code, test reports and a release. Models such as waterfall, spiral and Agile differ in how they order and repeat these phases.

  2. 2

    Compare waterfall and Agile.

    medium

    Waterfall moves through phases in sequence, with each phase completed and signed off before the next, which suits stable, well-understood requirements and heavy documentation or regulation. Feedback arrives late, so a requirement mistake found in testing is expensive. Agile works in short iterations that each deliver working software, welcomes changing requirements and gets customer feedback every few weeks. Agile suits uncertain or evolving requirements; its risks are scope creep and weak documentation if it is not managed.

  3. 3

    Explain the V-model.

    medium

    The V-model extends waterfall by pairing every development phase with a testing phase. Requirements map to acceptance testing, system design to system testing, architecture design to integration testing and module design to unit testing. Test planning begins early, alongside the matching design phase, so defects are caught sooner. It is still sequential and inflexible to change, but suits safety-critical domains where verification is mandatory.

  4. 4

    What is the spiral model?

    medium

    The spiral model repeats four activities in each loop: determine objectives, identify and resolve risks (often by prototyping), develop and test, and plan the next loop. Each loop produces a more complete version. Its distinguishing feature is explicit risk analysis, so it suits large, high-risk projects. It is costly and needs risk-assessment expertise, so it is rare for small projects.

  5. 5

    What are the four values of the Agile Manifesto?

    easy

    Individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan. The manifesto says there is value in the items on the right, but the items on the left are valued more. It is supported by twelve principles, such as delivering working software frequently and welcoming changing requirements.

  6. 6

    Describe the roles, events and artifacts of Scrum.

    medium

    Roles (accountabilities): the Product Owner owns the Product Backlog and its ordering, the Scrum Master coaches the team and removes impediments, and Developers build the increment. Events: the Sprint contains Sprint Planning (what and how), the Daily Scrum (a 15-minute plan for the next 24 hours), the Sprint Review (inspect the increment with stakeholders) and the Sprint Retrospective (improve the way of working). Artifacts: the Product Backlog (ordered list of work), the Sprint Backlog (selected items plus the plan) and the Increment (usable, meeting the Definition of Done).

  7. 7

    What is a user story and what makes it good?

    medium

    A user story describes a need from the user's perspective in a format like "As a student, I want to download my hall ticket, so that I can carry it to the exam." It is a conversation starter, not a full specification. Acceptance criteria state when it is done, for example: the PDF contains the roll number; the download works for registered students only. The INVEST checklist describes a good story: Independent, Negotiable, Valuable, Estimable, Small and Testable.

  8. 8

    What are story points and velocity?

    medium

    Story points are a relative estimate of the effort, complexity and uncertainty of a backlog item, often using the Fibonacci-like scale 1, 2, 3, 5, 8, 13. Teams compare items with reference stories instead of estimating hours. Velocity is the number of points a team completes per sprint, averaged over recent sprints, and is used for forecasting, as in the worked example above. It is relative to a single team and should not be used to compare teams or to pressure people.

  9. 9

    Scrum versus Kanban?

    medium

    Scrum uses fixed-length sprints, defined roles and commitment to a sprint goal; changes mid-sprint are discouraged. Kanban is continuous flow: work items move across a board, and the key controls are visualising work and limiting work in progress (WIP) per column, which exposes bottlenecks. Kanban has no mandatory roles or time-boxes and new work can be added whenever there is capacity. Teams with unpredictable, interrupt-driven work, such as support, often prefer Kanban, while product development teams often prefer Scrum.

  10. 10

    What is the Definition of Done, and how does it differ from acceptance criteria?

    easy

    The Definition of Done is a shared, team-wide quality checklist that every item must satisfy to count as complete, such as code reviewed, unit tests passing, integrated, documented and deployed to staging. Acceptance criteria are specific to one story and describe the behaviour that makes that story acceptable to the Product Owner. A story is done only when it meets both.

  11. 11

    What is a sprint retrospective, and what makes it useful?

    medium

    It is a meeting at the end of the sprint where the team inspects how it worked, covering people, process and tools, and agrees on a few concrete improvements to try in the next sprint. A common format is: what went well, what did not, what to change. It is useful when the actions are small, assigned and revisited in the next retrospective, and when people feel safe to be honest. Without follow-through it turns into complaining.

  12. 12

    Name the levels and types of software testing.

    medium

    Levels: unit testing of individual functions or classes, integration testing of modules together, system testing of the complete application against requirements, and acceptance testing (UAT) by users or customers. Types: functional versus non-functional (performance, security, usability), black-box (no knowledge of the code) versus white-box (code-aware), smoke testing for a basic health check of a build, and regression testing to verify that new changes have not broken existing behaviour.

  13. 13

    What are CI/CD and DevOps?

    medium

    Continuous integration means developers merge small changes frequently and each merge triggers an automated build and test run, so integration problems appear quickly. Continuous delivery keeps the main branch always releasable and deploys through an automated pipeline, with a manual approval for production; continuous deployment releases every passing change automatically. DevOps is the culture and set of practices that unite development and operations, with shared ownership, automation, monitoring and fast feedback.

  14. 14

    What is technical debt?

    medium

    Technical debt is the future cost created by choosing a quick or messy solution now instead of a better one that would take longer. Like financial debt it accrues interest: each later change is slower and riskier. Some debt is deliberate and acceptable, such as shipping a prototype, if it is recorded and repaid. Manage it by refactoring continuously, reserving capacity in each sprint and tracking items in the backlog.

  15. 15

    What is an MVP?

    easy

    A minimum viable product is the smallest version of a product that delivers real value and lets the team learn from real users. It tests the riskiest assumption cheaply before heavier investment. An MVP is not a low-quality product; it has few features, but those features work. The learning, such as whether users return, drives what to build next.

Frequently asked questions

Which SDLC model is best?

None is best for all cases. Agile suits changing requirements, waterfall or the V-model suit fixed, regulated work, and spiral suits risky large projects.

How long is a Scrum sprint?

A sprint is a time-box of one month or less, and two weeks is the most common choice.

Is Scrum the same as Agile?

No. Agile is a set of values and principles. Scrum is one framework that implements them; Kanban and XP are others.

Do freshers get asked about Agile?

Often, especially in service-company interviews. Know the SDLC phases, Scrum roles and events, and be ready to describe a project you worked on in those terms.

Related guides

More in CS Fundamentals Interview Questions

See all in this section