NEOCODE

Agile Development Methodology MCQs

1. Agile Development Methodology

Q1. What is the primary focus of Agile methodology?

Correct Answer: C) Customer collaboration and iterative development

Explanation:
Agile methodology emphasizes customer collaboration, responding to change, and delivering working software in short iterations rather than focusing on extensive documentation or rigid planning.

Q2. Which of these is NOT an Agile principle?

Correct Answer: B) Contract negotiation over customer collaboration (Agile prefers collaboration over contract negotiation)

Explanation:
The Agile Manifesto values "Customer collaboration over contract negotiation." Contract negotiation is associated with traditional waterfall methods, while Agile emphasizes ongoing collaboration with customers.

Q3. Agile projects are divided into short iterations called:

Correct Answer: B) Sprints

Explanation:
In Agile (particularly Scrum), work is organized into fixed-length iterations called sprints, typically 1-4 weeks long, at the end of which a potentially shippable product increment is delivered.

2. Scrum Framework

Q4. Who is responsible for removing obstacles in Scrum?

Correct Answer: B) Scrum Master

Explanation:
The Scrum Master serves as a facilitator and coach, removing impediments that hinder the team's progress. This is distinct from the Product Owner who manages what gets built, and the Development Team who builds it.

Q5. The Product Backlog is maintained by:

Correct Answer: C) Product Owner

Explanation:
The Product Owner is solely responsible for managing the Product Backlog, including prioritizing items and ensuring it's visible and transparent to all stakeholders.

Q6. Daily Stand-up meetings in Scrum should ideally last:

Correct Answer: B) 15 minutes

Explanation:
Daily Scrums are time-boxed to 15 minutes to keep them focused. Team members answer: What did I do yesterday? What will I do today? Are there any impediments?

Q7. Which Scrum artifact represents work to be done in a Sprint?

Correct Answer: B) Sprint Backlog

Explanation:
The Sprint Backlog contains items selected from the Product Backlog plus the plan for delivering them. It's created during Sprint Planning and owned by the Development Team.

3. Aspect-Oriented Programming (AOP)

Q8. AOP is used primarily for:

Correct Answer: A) Improving code modularity by separating cross-cutting concerns

Explanation:
AOP addresses cross-cutting concerns (like logging, security) that traditionally cut across multiple modules, resulting in code scattering and tangling. It improves modularity by encapsulating these concerns in aspects.

Q9. In AOP, logging and security are examples of:

Correct Answer: B) Cross-cutting concerns

Explanation:
Cross-cutting concerns affect multiple parts of a system but don't align with the system's primary decomposition. AOP separates these from the main business logic for better maintainability.

Q10. Which term refers to the point where an aspect is applied in AOP?

Correct Answer: A) Join Point

Explanation:
A join point is a point in the execution of a program where an aspect can be plugged in, such as method invocation or exception handling. Advice (aspect code) is executed at these points.

4. Extreme Programming (XP)

Q11. Which practice in XP involves two programmers working together on the same code?

Correct Answer: B) Pair Programming

Explanation:
In pair programming, two developers work together at one workstation - one "drives" (writes code) while the other "navigates" (reviews each line). They switch roles frequently for better code quality and knowledge sharing.

Q12. XP emphasizes:

Correct Answer: D) All of the above

Explanation:
XP values working software over documentation, recommends short release cycles (1-3 weeks), and requires an on-site customer for continuous feedback - making all these options correct.

Q13. The XP practice of writing tests before code is called:

Correct Answer: B) Test-Driven Development (TDD)

Explanation:
TDD follows a red-green-refactor cycle: write a failing test (red), write minimal code to pass (green), then refactor. This ensures test coverage and drives design from requirements.