Agile Methodologies Quiz

Definition: Agile methodologies are iterative and incremental approaches to software development focusing on collaboration, customer feedback, and small, rapid releases.
Core Principles (Agile Manifesto):
1. Individuals and interactions over processes and tools.
2. Working software over comprehensive documentation.
3. Customer collaboration over contract negotiation.
4. Responding to change over following a plan.
Common Agile Frameworks:
- Scrum:
  - Involves roles (Scrum Master, Product Owner, Development Team).
  - Utilizes time-boxed iterations called Sprints (typically 2-4 weeks).
  - Focuses on regular ceremonies: Sprint Planning, Daily Stand-ups, Sprint Review, and Retrospective.
- Kanban:
  - Emphasizes continuous delivery and work-in-progress limits.
  - Visualizes work using a Kanban board.
  - Adapts to changes flexibly without fixed iterations.
- Extreme Programming (XP):
  - Focuses on technical excellence and frequent releases.
  - Practices include pair programming, test-driven development (TDD), and continuous integration.
Benefits:
- Improved flexibility and adaptability to change.
- Enhanced customer satisfaction through frequent delivery and feedback.
- Increased team collaboration and ownership.

Definition: A Version Control System is a tool that helps manage changes to source code over time, allowing multiple people to work on a project simultaneously.
Types of Version Control Systems:
- Local Version Control Systems:
  - Keep track of changes in local files (e.g., RCS).
- Centralized Version Control Systems (CVCS):
  - Single central repository (e.g., SVN, CVS).
  - Allows multiple users to collaborate but depends on a central server.
- Distributed Version Control Systems (DVCS):
  - Each user has a full copy of the repository (e.g., Git, Mercurial).
  - Allows for offline work and more robust collaboration.
Key Concepts:
- Repository: Storage location for project files and version history.
- Commit: A snapshot of changes with a message describing the update.
- Branching: Creating a separate line of development to work on features without affecting the main codebase.
- Merging: Combining changes from different branches into a single branch.
- Conflict Resolution: Managing conflicts that arise when merging changes made to the same part of the code.
Benefits:
- Enables collaboration among multiple developers.
- Provides a history of changes for tracking progress and reverting to earlier versions if needed.
- Supports branching and merging for feature development and bug fixes.

Agile methodologies utilize iterative and incremental approaches for software development, emphasizing collaboration, customer feedback, and rapid releases.
The Agile Manifesto outlines four core principles:
- Prioritizes individuals and interactions over rigid processes and tools.
- Values working software more than extensive documentation.
- Encourages customer collaboration rather than strict contract negotiation.
- Emphasizes responsiveness to change instead of adherence to a strict plan.

Scrum:
- Defines specific roles: Scrum Master, Product Owner, and Development Team.
- Operates in time-boxed iterations known as Sprints, usually lasting 2-4 weeks.
- Incorporates regular ceremonies including Sprint Planning, Daily Stand-ups, Sprint Review, and Retrospective for continuous improvement.
Kanban:
- Focuses on continuous delivery and incorporates work-in-progress limits to enhance efficiency.
- Uses a visual Kanban board to track workflow.
- Offers flexibility to adapt to changes without being constrained by fixed iterations.
Extreme Programming (XP):
- Aims for technical excellence with frequent software releases.
- Implements practices like pair programming, test-driven development (TDD), and continuous integration for high-quality code.

Facilitates improved flexibility and adaptability in response to changing requirements.
Enhances customer satisfaction through consistent delivery of valuable software and regular feedback loops.
Fosters greater team collaboration and encourages ownership of the development process.

Version Control Systems are essential tools that help manage and track changes to source code over time, allowing collaborative project work among multiple developers.

Local Version Control Systems:
- Maintain changes within local files, exemplified by tools like RCS.
Centralized Version Control Systems (CVCS):
- Feature a single central repository (like SVN or CVS), allowing collaboration through a shared server.
Distributed Version Control Systems (DVCS):
- Each developer has a complete copy of the repository (e.g., Git, Mercurial), enabling offline work and robust collaboration.

Repository: The central storage location for project files and their version history.
Commit: A specific snapshot of changes made, accompanied by a description for context.
Branching: Creates independent lines of development that allow work on features or fixes without disrupting the main codebase.
Merging: Combines changes from different branches into a unified branch.
Conflict Resolution: The process of addressing and resolving conflicts when simultaneous changes affect the same code section.

Promotes collaboration among developers by allowing simultaneous work on projects.
Maintains a historical record of changes, which supports progress tracking and rollback if necessary.
Allows branching and merging, facilitating efficient feature development and bug fixes.