Browse Courses

Introduction to Agile Development and Scrum

Agile development is a software development methodology that emphasizes flexibility, collaboration, and customer satisfaction. It is an iterative approach that allows teams to respond quickly to changing requirements and deliver high-quality software in shorter timeframes. Scrum is one of the most popular frameworks within Agile, providing a structured way to manage and execute projects through sprints, roles, and ceremonies.

In this section

  • Module 1
    This module covers Agile principles, methodologies, and Scrum frameworks. It explores the foundations of Agile development, various methodologies including Extreme Programming (XP) and Kanban, Scrum roles, artifacts, events, and organizational impacts of Agile adoption.
    • Agile Principles
      Agile is an iterative approach to project management that emphasizes adaptive planning, evolutionary development, early delivery, and continuous improvement. This document explains the Agile philosophy, its defining characteristics, and the principles outlined in the Agile Manifesto.
    • Agile Methodologies
      This document explores various software development methodologies, contrasting the traditional Waterfall approach with Agile methodologies such as Extreme Programming (XP) and Kanban. It examines the limitations of the sequential Waterfall model and highlights how iterative, feedback-driven approaches address these challenges.
    • Working Agile
      This document explores five key practices of Agile methodology working in small batches, creating minimum viable products (MVPs), behavior-driven development (BDD), test-driven development (TDD), and pair programming. These practices enable teams to deliver value quickly, obtain fast feedback, and maintain high code quality.
    • Introduction to Scrum
      Scrum is a management framework for incremental product development that follows the Agile philosophy. It provides structure through defined roles meetings, rules, and artifacts while emphasizing small cross-functional teams working in fixed-length iterations called sprints to deliver potentially shippable product increments.
    • Scrum Roles
      This document explains the three core roles in Scrum; Product Owner, Scrum Master, and Scrum Team. Each role has specific responsibilities that ensure the effective implementation of Scrum methodology, promoting self-organization, collaboration, and continuous delivery of value.
    • Scrum Artifacts, Events and Benefits
      This document explains the key components of Scrum methodology.The three artifacts (Product Backlog, Sprint Backlog, and Done Increment), the five events (Sprint Planning, Daily Scrum, Sprint, Sprint Review, and Sprint Retrospective), and the benefits of implementing Scrum. It also highlights the differences between Scrum and Kanban approaches.
    • Organise for Success
      This document explains how organizational structure impacts the success of Agile implementations. It covers Conway's Law, team alignment strategies, the importance of team autonomy, and why organization-wide Agile adoption is essential. The document also explores the synergies between Agile and DevOps practices for achieving maximum effectiveness.
    • Organisational Impact of Agile
      This document explains how organizational structure impacts the effectiveness of Agile methodologies. It covers Conway's Law, proper team alignment strategies, the importance of team autonomy, and why the entire organization must adopt Agile principles. The alignment between Agile and DevOps approaches is also explored to highlight how they complement each other for maximum business value.
  • Module 2
    Detailed exploration of Scrum roles (Product Owner, Scrum Master, Development Team) and their responsibilities within the Agile framework.
    • Agile Roles and Need for Training
      Understanding why placing existing employees in new Agile roles without proper training leads to failure and how role transformations require specific mindset changes
    • Creating Effective User Stories
      A comprehensive guide to creating well-structured user stories with proper descriptions, acceptance criteria, and business value statements that follow the INVEST principles
    • Agile Tools: Understanding Kanban Boards
      An overview of Kanban boards, their pipelines, and workflow in Agile project management, with a focus on ZenHub integration with GitHub
    • Story Points
      An exploration of the concept, implementation, and best practices of story point estimation in agile methodologies. This article covers how teams can use abstract metrics instead of time-based estimates to more effectively plan and track work across sprints.
    • Product Backlog
      Explains the product backlog as the ranked list of all unimplemented user stories in a Scrum project. Details how to convert requirements into properly formatted user stories, organize items by priority, and ensure stories at the top are sufficiently detailed for implementation in upcoming sprints.
    • Product Backlog Refinement
      Explores the product backlog refinement process in Scrum methodology detailing how items are prioritized, broken down, and prepared for implementation. Covers key participants and their roles, techniques for effective refinement and the importance of triaging new requirements to maintain a well-organized backlog.
    • Finishing Backlog Refinement
      Details the final stages of backlog refinement, focusing on story labeling and managing technical debt. Explains how color-coded labels provide visual cues about work types, how to identify technical debt items that require attention and strategies to ensure stories are properly detailed before sprint planning.
    • Sprint Planning
      Explains the sprint planning process in Scrum methodology, including participants, sprint goals, and creating the sprint backlog. Covers how the development team selects stories, confirms story points, and ensures each story has sufficient details for implementation during the upcoming sprint.
    • Kanban Board
      The Kanban board is a visual tool that helps teams manage their workflow and visualize tasks. It consists of columns representing different stages of the workflow, with cards representing individual tasks. Teams can move cards between columns as work progresses, providing a clear overview of the project's status.
  • Module 3
    Intermediate Agile development concepts and Scrum implementation techniques for effective software development teams.
    • Daily Planning
      Learn the structured approach to daily sprint execution, story selection protocols, and Kanban board management for effective Scrum team coordination.
    • Daily Standup Meeting
      Learn the structure, purpose, and best practices for conducting effective 15-minute daily standup meetings in Scrum teams.
    • Burn down Chart
      Understanding burndown charts as visual tools for tracking sprint progress measuring story point completion, and forecasting team's ability to achieve sprint goals.
    • Sprint Review
      Understanding Sprint Review meetings in Scrum methodology, including participant roles, demonstration processes, and feedback management for iterative development success.
    • Story Points and Burndown Charts
      Learn to apply story points and burndown charts through practical scenarios and real-world examples.
    • Sprint Retrospective
      A comprehensive guide to sprint retrospectives, covering their purpose attendees, and implementation. Learn how to effectively reflect on sprints to drive continuous improvement in Scrum teams.
    • Actionable Metrics vs Vanity Metrics
      An exploration of metrics in agile development, distinguishing between actionable and vanity metrics. Learn about the top four actionable metrics and how they can drive continuous improvement in development teams.
    • Next Sprint
      A comprehensive guide to end-of-sprint activities and transition procedures. Learn how to properly close sprints, handle unfinished work, and prepare for the next iteration while maintaining accurate velocity measurements.
    • Agile Anti Patterns
      An examination of common Scrum anti-patterns to avoid and essential health check criteria for evaluating team effectiveness. This guide helps identify problematic practices and establish benchmarks for maintaining high-performing Agile teams.
  • Module 4
    Advanced topics in Agile development and Scrum methodologies building upon foundational concepts from previous modules.