(SEM VII) THEORY EXAMINATION 2019-20 AGILE SOFTWARE DEVELOPMENT

SECTION A – Explanation

Section A of the Agile Software Development paper is designed to test the student’s basic conceptual clarity and familiarity with core Agile and Scrum terminology. All questions in this section are compulsory and require brief but accurate answers. The examiner expects students to demonstrate a clear understanding of commonly used Agile concepts that are applied in real-world software development environments.

The questions in this section focus on defining roles in Scrum, understanding velocity in Agile, identifying qualities of a good Agile tester, explaining the concept of Scrum of Scrums, identifying situations where the Agile model is suitable, defining epic, user stories, and tasks, and explaining Agile metrics. These topics form the foundation of Agile practices and are essential for understanding how Agile teams plan, execute, and measure their work.

For example, the question on Scrum roles checks whether the student understands the responsibilities of Product Owner, Scrum Master, and Development Team. Velocity tests knowledge of how Agile teams estimate and track progress. The question on Agile testers evaluates awareness of collaboration, adaptability, and continuous testing. Epic, user stories, and tasks reflect how requirements are broken down in Agile. Answers in this section should be concise, conceptually correct, and written in clear Agile terminology. Lengthy explanations are not required, but incorrect definitions can easily lead to loss of marks.

SECTION B – Explanation

Section B evaluates the student’s conceptual understanding and ability to explain Agile methods in comparison with traditional software development approaches. Students are required to attempt any three questions, which allows them to choose topics based on their strengths. The questions in this section require descriptive answers supported by examples.

The questions in Section B include comparison between the traditional Waterfall model and Agile testing with examples, comparison between Extreme Programming (XP) and Scrum, discussion of Agile methodology and how it differs from modern software development, explanation of Feature Driven Development (FDD) and its activities, and discussion of impediments in Scrum with suitable examples. These questions aim to test the student’s understanding of Agile philosophies, frameworks, and practical challenges.

For instance, the Waterfall versus Agile testing question checks understanding of sequential versus iterative testing approaches. The XP versus Scrum comparison tests knowledge of Agile frameworks and their practices such as pair programming, iterations, and roles. FDD questions examine understanding of feature-centric development. The question on impediments in Scrum evaluates awareness of real-life obstacles like lack of stakeholder involvement or team dependencies. Answers in this section should be written in a clear and logical manner, beginning with an introduction and followed by explanation and examples. The expected length is about one and a half to two pages per answer.

SECTION C – Explanation

Section C is the most important and highest-weight section of the Agile Software Development paper. This section tests the student’s in-depth understanding, analytical thinking, and ability to explain Agile practices, frameworks, and tools in detail. Each question provides internal choices, and students must attempt only one part from each question.

The questions in Section C cover advanced and application-oriented topics such as Agile manifesto values and principles, Scrum framework in detail, roles and responsibilities in Scrum, planning poker and estimation techniques, Agile project management lifecycle, test-driven development (TDD), continuous integration, Agile metrics and reporting tools, scaling Agile using Scrum of Scrums, and Agile risk management. These topics require detailed explanation and practical understanding.

For example, questions on Agile manifesto require explanation of values and principles with relevance to customer satisfaction and adaptability. Scrum framework questions expect detailed explanation of sprint planning, daily scrum, sprint review, and retrospective. Estimation techniques such as planning poker require explanation of collaborative estimation. TDD and continuous integration questions test understanding of quality assurance in Agile. Answers in this section should be detailed, well structured, and written with clarity. Each answer generally extends over two to three pages and plays a major role in determining the final score.

Overall Understanding of the Paper Pattern

The Agile Software Development (RCS-077) question paper is structured to test students progressively from basic understanding to advanced application of Agile concepts. Section A focuses on fundamental definitions and terminology, Section B evaluates conceptual clarity and comparison between Agile practices, and Section C tests deep understanding of Agile frameworks, principles, and real-world implementation. Students who understand this structure can prepare effectively by revising basics for Section A, practicing explanations and comparisons for Section B, and mastering detailed Agile concepts for Section C.

A strong preparation strategy for this subject includes understanding Agile values, Scrum framework, estimation techniques, testing practices, and scaling Agile methods. Section C carries the highest weight and requires special attention to score high marks.