This set covers modern iterative development: the Agile Manifesto, Scrum roles, events and artifacts, velocity and story-point estimation, Extreme Programming practices such as pair programming and test-driven development, Kanban, and DevOps ideas like continuous integration, continuous delivery and infrastructure as code. It is aimed at university exams, UGC NET and especially interview rounds, where Agile and DevOps questions are very common.
How to practise: read each question and tap the option you think is correct. You will see right away whether you got it, along with a short explanation, and your score is tracked at the bottom of the screen. This set has 18 questions.
Topics covered in this set
- Agile Manifesto values and principles
- Scrum roles, events and artifacts
- Velocity, story points and burn-down charts
- XP practices: pair programming, TDD, refactoring
- Kanban and WIP limits
- DevOps: CI, continuous delivery and deployment, IaC
Software Engineering MCQs with answers and explanations
Q1. According to the Agile Manifesto, which of the following is valued more than comprehensive documentation?
a) Following a plan
b) Working software
c) Processes and tools
d) Contract negotiation
Q2. In Scrum, who is accountable for ordering the Product Backlog and maximising the value of the product?
a) Scrum Master
b) Project Manager
c) Product Owner
d) Lead Developer
Q3. Which description best fits the Scrum Master?
a) The person who assigns tasks to each developer daily
b) The customer representative who accepts the increment
c) The person who writes all user stories
d) A servant-leader who coaches the team on Scrum and helps remove impediments
Q4. What is the maximum length of a Sprint according to the Scrum Guide?
a) One month
b) One week
c) Six weeks
d) Three months
Q5. A Scrum team completed 24, 30 and 27 story points in its last three sprints. If 135 points remain in the backlog, about how many more sprints are needed at the average velocity?
a) 4
b) 6
c) 5
d) 7
Q6. In Extreme Programming, two developers working together at one workstation, one writing code and the other reviewing continuously, is called
a) Collective ownership
b) Spike solution
c) Mob testing
d) Pair programming
Q7. In test-driven development, what is the very first step when adding a new behaviour?
a) Write the production code and then the test
b) Write a test for the behaviour that fails
c) Refactor the existing code
d) Run the full regression suite on the server
Q8. Which XP practice allows any developer to change any part of the code base at any time?
a) Collective code ownership
b) Sustainable pace
c) On-site customer
d) Small releases
Q9. Planning poker is mainly used for
a) Assigning bugs to testers
b) Prioritising sprints by business value only
c) Calculating the cost of cloud infrastructure
d) Relative estimation of backlog items by the whole team
Q10. What is the main purpose of the Sprint Retrospective?
a) To demonstrate the increment to stakeholders
b) To inspect how the team worked and plan improvements to its process
c) To select backlog items for the next sprint
d) To estimate the release date for management
Q11. The shared, formal description of the quality criteria an increment must meet before it is considered complete is called the
a) Definition of Done
b) Sprint Goal
c) Product Vision
d) Acceptance Burn-up
Q12. The defining mechanism of Kanban for improving flow is
a) Fixed-length sprints with commitments
b) Mandatory pair programming
c) Explicit limits on work in progress for each stage
d) A dedicated Scrum Master role
Q13. Continuous integration primarily means
a) Developers merge code into a shared mainline frequently, with each merge verified by an automated build and tests
b) Code is deployed to production once every quarter
c) Testers integrate their test plans at the end of the project
d) Each developer keeps a long-lived private branch until release
Q14. How does continuous deployment differ from continuous delivery?
a) Continuous deployment does not use automated testing
b) Every change that passes the pipeline is released to production automatically, without a manual approval step
c) Continuous deployment releases only once per sprint
d) Continuous deployment skips version control
Q15. Defining servers, networks and environments in version-controlled machine-readable files rather than configuring them by hand is known as
a) Shift-left testing
b) Blue-green deployment
c) Infrastructure as Code
d) Feature toggling
Q16. In the INVEST checklist for good user stories, the letter I stands for
a) Iterative
b) Incremental
c) Integrated
d) Independent
Q17. A sprint burn-down chart plots
a) Completed features against cost
b) Remaining work against time within the sprint
c) Defects found against modules
d) Team velocity across releases only
Q18. In Scrum, who has the authority to cancel a Sprint before its time-box ends?
a) Product Owner
b) Scrum Master
c) Any single developer
d) The external auditor
Quick revision notes
- Agile values: individuals and interactions, working software, customer collaboration, responding to change.
- Scrum roles: Product Owner (value, backlog), Scrum Master (process, impediments), Developers (increment).
- Sprint is at most one month; Daily Scrum is time-boxed to 15 minutes.
- Velocity = story points completed per sprint; sprints needed = remaining points / average velocity.
- TDD cycle: red (failing test), green (make it pass), refactor.
- INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable.
- Continuous delivery keeps code always releasable; continuous deployment releases every passing change automatically.
- Kanban limits work in progress to expose bottlenecks and improve flow.
Frequently asked questions
What is the difference between Sprint Review and Sprint Retrospective?
The Sprint Review inspects the product increment with stakeholders and adapts the product backlog. The Sprint Retrospective, held after it, inspects how the team worked and plans process improvements for the next sprint.
Is DevOps the same as Agile?
No. Agile focuses on iterative development and close collaboration with customers, while DevOps extends that collaboration to operations, automating build, test, deployment and monitoring so that software reaches production quickly and reliably. They complement each other.
Why are story points used instead of hours?
Story points measure relative size and complexity rather than time, so teams can estimate quickly by comparison. Combined with measured velocity, they give reliable forecasts without arguing over exact hours.
Comments
Post a Comment