This training session provides an introduction to Agile methodology, covering its core concepts, principles, and the Scrum framework.

Agile vs. Waterfall Methodology

• Waterfall: A traditional, linear project management approach. Projects move sequentially through distinct phases: planning, analysis, design, implementation, testing, and maintenance. It is highly plan-driven, making it less flexible once the design phase is set.
• Agile: An iterative, flexible approach that allows for collaboration and quick adaptation. Rather than building an entire project at once, work is divided into smaller, incremental chunks, which helps teams move efficiently and respond to changing requirements.

The Agile Manifesto and Principles

The Agile Manifesto prioritizes:

• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Collaboration over contract negotiation.
• Responding to change over following a rigid plan.

Key principles include prioritizing customer satisfaction through continuous delivery, welcoming changing requirements, maintaining a sustainable development pace, and fostering self-organizing teams.Scrum Overview

Scrum is the most common Agile framework. It uses “sprints”—time-boxed iterations typically lasting one to four weeks—to manage work.

• Values: Commitment, courage, focus, openness, and respect.
• Pillars: Transparency, inspection, and adaptation.
  • Transparency: Ensures clear communication and data-driven decision-making, utilizing tools like daily standups and task boards.
  • Inspection: Requires regular evaluation of progress, assumptions, and risks against project objectives.
  • Adaptation: Allows teams to pivot strategies and refine requirements based on insights gained during inspection.

Scrum Roles and Characteristics

• Roles: A Scrum team typically includes a Product Owner and a Scrum Master. The Scrum Master role facilitates ceremonies and removes blockers, though the title may vary (e.g., an Engineering Manager may fulfill these duties).
• Characteristics: Teams are ideally small (10 people or fewer), non-hierarchical, cohesive, cross-functional, and self-managing.
• Challenges: Common difficulties include a steep learning curve, high resource commitment, dependency management, and the need to actively protect sprint goals against scope creep.