Agile Development Practices Quiz

A method of software development where requirements are broken down into small, manageable stories and prioritized based on value and time available. Developers then further decompose these stories into tasks for implementation.

Frequent releases of software that progressively add functionality to the initial version. Each release focuses on delivering a minimal useful set of features that provide value to the user.

The design should be sufficient to meet the current requirements and avoid unnecessary complexity. Focusing on simplicity and avoiding over-engineering.

A practice where automated unit tests are written for a new piece of functionality before the functionality itself is implemented. This ensures that the code meets expectations and avoids introducing errors.

A continuous process of improving the codebase by cleaning it up, simplifying it, and eliminating redundancies. This helps maintain code readability and maintainability.

Two developers work together on the same task, checking each other's code and providing support. This promotes knowledge sharing, reduces errors, and improves overall code quality.

Encourages all developers to take ownership of the entire codebase, eliminating silos and promoting collaboration. Anyone can contribute to any part of the system.

Integrating new code changes into the main system as soon as they are completed. After integration, all unit tests are run to ensure that new code doesn't break existing functionality.

A software development approach that emphasizes iterative cycles, rapid prototyping, and customer feedback to deliver working software quickly and adapt to changing requirements.

A software development process that involves breaking down a large project into smaller, manageable parts, developing each part in parallel, and then integrating the finished parts into a complete system.

A software development model that follows a structured, sequential approach, starting with requirements gathering and ending with deployment and maintenance.

A software development model that iteratively builds upon previous iterations while prioritizing addressing the highest risks associated with the project.

The first phase of the Spiral Model focuses on identifying and addressing the key risks and potential challenges that are most likely to hinder the project.

A foundational principle of Agile Methods that emphasizes the importance of individuals and their collaboration over rigid processes and tools.

A core value of Agile Methods; it prioritizes working software that delivers value to customers over extensive documentation.

A crucial principle of Agile Methods; it emphasizes the continuous collaboration with customers throughout the software development process.

A key value of Agile Methods; it advocates for adaptability and flexibility to accommodate changing requirements and market dynamics.

A set of principles and practices that guide Agile software development, emphasizing collaboration, customer focus, and iterative development.

A practice in XP where the code is constantly improved (refactored) to make future changes easier, even if there's no immediate need for them.

A type of refactoring involving changes to the overall architecture of the software, often more expensive to implement compared to smaller code improvements.

Refactoring example: Changing the class hierarchy to eliminate redundant code.

Refactoring example: Improving code clarity by making attributes and methods easier to understand.

Refactoring example: Replacing inline code with calls to pre-written functions in a library.

A specific type of test-first development where tests are written as automated code. These tests are run automatically every time new code is added, ensuring no errors are introduced.

A core principle in XP where customers actively participate in testing and validation of software features.

Acceptance tests designed and implemented by customers in the team to verify whether new features meet their needs.

The process of writing executable tests before writing the actual code. These tests aim to simulate user input and verify that the code produces the expected output.

A team of developers (usually no more than 7) responsible for developing software and related documents.

A fully functional increment of the software, ready for release.

A series of sprints that focus on developing and delivering increments of the software.

The first phase of Scrum, where the overall project goals and software architecture are established.

The final phase of Scrum, where documentation is completed, lessons are learned, and the project is officially concluded.

An approach to project management that emphasizes iterative development and flexible adjustments to plans.

A plan-driven approach to project management where specific tasks are scheduled in advance.

The core responsibility of a software project manager is to deliver the software on time and within budget.

Pair programming is a collaborative approach to coding that can be more efficient than individual work, leading to better code quality and knowledge sharing.