Agile Methodology Fundamentals

Agile Methodology

Core Values

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Agile Principles

• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
• Deliver working software frequently (weeks rather than months), with a preference to shorter timescales.
• Close, daily cooperation between business people and developers.
• Projects are built around motivated individuals, who should be trusted and supported.
• Face-to-face conversation is the most efficient and effective method of conveying information.
• Working software is the primary measure of progress.
• Continuous attention to technical excellence and good design enhances agility.
• Simplicity—the art of maximizing the amount of work not done—is essential.
• The best architectures, requirements, and designs emerge from self-organizing teams.
• At regular intervals, the team reflects on how to become more agile and adjusts accordingly.

Agile Methodologies

• Scrum:
  • Framework for managing and completing complex projects using iterative and incremental practices.
  • Emphasizes teamwork, accountability, and iterative progress.
• Kanban:
  • Visual system for managing work, emphasizing continuous flow and limiting work in progress.
  • Focuses on workflow optimization and lead time reduction.
• Lean Software Development:
  • Applies lean manufacturing principles to software development, emphasizing elimination of waste and maximization of value.
  • Focuses on continuous improvement and delivery of value to customers.
• Extreme Programming (XP):
  • Iterative and incremental software development method, emphasizing technical practices and customer satisfaction.
  • Focuses on rapid feedback, continuous testing, and refactoring.

Agile Roles

• Product Owner:
  • Responsible for defining and prioritizing product backlog.
  • Ensures that team has a clear understanding of product requirements.
• Scrum Master:
  • Facilitates Scrum framework and ensures team follows agile principles.
  • Removes impediments and fosters collaboration.
• Development Team:
  • Cross-functional team responsible for developing and delivering working software.
  • Self-organizing and motivated individuals working together to achieve project goals.