
Discover the mindset shift that transformed the world of software development — from rigid processes and silos to collaboration, adaptability, and continuous improvement. In this lesson, you’ll explore why Agile emerged, the challenges of the traditional Waterfall approach, and how Agile practices foster better teamwork, faster feedback, and higher-quality outcomes. Learn the key values that define Agile, including people over processes and responding to change over following a plan. This lesson sets the stage for understanding Agile as not just a process — but a powerful mindset for success.
Go back to the roots of Agile with the Agile Manifesto and its 12 guiding principles. In this lesson, you’ll explore the four core values that reshaped the way teams build software and collaborate: individuals and interactions, working software, customer collaboration, and responding to change. Understand how these values, along with the 12 principles, guide real-world decisions, teamwork, and continuous improvement. Rather than memorizing theory, you’ll see how these ideas come to life through everyday Agile practices, empowering teams to stay adaptable, focused, and user-centered.
Understand the Scrum roles that keep Agile teams running smoothly. In this lesson, you’ll meet the three key Scrum roles — Product Owner, Scrum Master, and Developers — and learn who does what within the team. See how the Product Owner prioritizes the backlog, the Scrum Master removes blockers and facilitates Scrum events, and the Developers (including coders, testers, and analysts) build the working increment. This lesson highlights how shared ownership, collaboration, and clear role definitions help Scrum teams stay focused and productive without hierarchies or micromanagement.
Understand the Scrum events that shape the rhythm of Agile teamwork. In this lesson, you’ll explore the five key Scrum events — Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective, and the Sprint itself — and how each plays a role in keeping the team aligned, focused, and continuously improving. See how this structured cycle of Plan → Build → Review → Reflect supports collaboration, feedback, and adaptability. This lesson provides a clear overview of how Scrum teams work together through each sprint.
Learn how to turn vague feature requests into clear, actionable user stories that Agile teams can estimate, plan, and deliver. In this lesson, you’ll follow the process of refining a request like “add social login” into a well-structured user story using the As a [user], I want [goal], so that [benefit] format. Discover how Business Analysts, Product Owners, and team members collaborate to ask the right questions, clarify edge cases, and define acceptance criteria — ensuring the story is clear, testable, and valuable. This lesson shows how good story writing lays the foundation for successful sprints.
A quick guide to help you succeed in this simulation by asking the right questions and shaping a clear, actionable user story.
Learn how Backlog Grooming (also called Backlog Refinement) helps Agile teams prepare stories for smooth and successful sprint planning. In this lesson, you’ll explore how the team collaborates to clarify user stories, split large items into smaller stories, add acceptance criteria, and estimate effort using techniques like Planning Poker. Understand how refinement ensures that stories are well-defined, testable, and truly Ready for Sprint, reducing blockers and surprises during sprint execution. This lesson highlights how backlog refinement keeps the team focused and the planning process efficient.
Learn how Agile teams kick off each sprint with clear focus and shared understanding through Sprint Planning. In this lesson, you’ll explore how the team collaborates with the Product Owner to define a strong Sprint Goal, select stories based on team velocity, and build a realistic, actionable Sprint Backlog. Understand how Sprint Planning ensures alignment on priorities, capacity, and expectations — setting the stage for a productive sprint. This lesson highlights the key outputs of Sprint Planning: a clear goal, committed work, and a plan to move forward together.
Discover how the Daily Standup helps Agile teams stay aligned, identify blockers, and maintain steady progress. In this lesson, you’ll explore the purpose and structure of the standup — a quick, 15-minute daily sync that promotes team collaboration without turning into a status meeting. Learn the three key questions that guide each update, understand best practices for effective standups, and see how Scrum Masters facilitate these sessions to keep the team focused. This lesson highlights why standups are a vital part of keeping Agile teams connected and proactive.
Learn how the Sprint Review connects the Scrum team, Product Owner, and stakeholders to the bigger picture through live demos, open feedback, and backlog adjustments. In this lesson, you’ll see how Sprint Reviews go beyond status reporting — focusing on collaboration, inspect and adapt, and shaping the next steps based on real-world input. Understand how the review helps assess whether the Sprint Goal was met, identify unfinished work, and prioritize new ideas. This lesson highlights how continuous feedback during Sprint Reviews ensures the team is always building the right thing.
Discover the purpose and power of the Sprint Retrospective, a key Scrum event where teams reflect on their sprint process, celebrate successes, and identify areas for improvement. In this lesson, you’ll learn how retrospectives help Agile teams inspect and adapt, fostering a culture of continuous improvement and trust. See best practices for running effective retrospectives, focusing on process, not people, and turning insights into actionable improvements for the next sprint. This lesson emphasizes how retrospectives drive growth and alignment within Agile teams.
Learn how a Scrum Master plays a critical role in identifying and removing impediments that block the team’s progress. In this lesson, you’ll see real examples of common blockers like missing access, external dependencies, and unclear requirements, and how the Scrum Master steps in to resolve them — not by managing tasks, but through servant leadership, facilitation, and coaching. Understand how proactive issue resolution helps Agile teams stay focused, productive, and aligned with sprint goals. This lesson highlights the Scrum Master’s role as a quiet enabler of success, not a micromanager.
Learn the three essential Scrum artifacts that help Agile teams stay organized, focused, and aligned: the Product Backlog, Sprint Backlog, and Increment. In this lesson, you’ll explore how the Product Owner manages the evolving Product Backlog, how the Scrum Team selects and commits to work during Sprint Planning, and how the Increment represents the sum of completed, working product features ready for feedback or release. Understand the purpose, ownership, and role of each artifact in supporting transparency, accountability, and delivery within the Scrum framework.
Understand the difference between Acceptance Criteria and the Definition of Done (DoD) — two essential quality checkpoints in Agile teams. In this lesson, you’ll learn how Acceptance Criteria define the specific conditions for a user story to be accepted by the Product Owner, while the Definition of Done ensures that every story meets the team's shared quality standards. See how these concepts work together to keep quality high, avoid misunderstandings, and ensure the work delivered is truly complete and ready for release.
Explore three common Agile estimation techniques — Story Points, T-Shirt Sizing, and Ideal Hours — and understand when and how to use each method effectively. In this lesson, you’ll learn why relative sizing helps Agile teams focus on effort, complexity, and risk, rather than exact time estimates. Compare these techniques side by side to see why Story Points are the preferred method for sprint planning, how T-Shirt Sizing helps during early backlog shaping, and why Ideal Hours are less used in Agile environments. Gain clarity on estimation approaches to improve your team’s planning and forecasting.
Get hands-on with Planning Poker, one of the most popular Agile estimation techniques used by Scrum teams. In this lesson, you’ll experience how teams collaborate to estimate user stories using story points and the Fibonacci sequence, promoting shared understanding and alignment. Watch how the team discusses complexity, compares estimates, and reaches consensus through multiple voting rounds. This interactive approach makes estimation engaging, encourages team discussion, and helps avoid guesswork — turning estimation into a team decision, not an individual opinion.
Learn how to measure and track Velocity — a key Agile metric that helps teams plan realistically and improve over time. In this lesson, you’ll understand how velocity is calculated based on the story points completed per sprint, and how it supports better forecasting and commitment in Sprint Planning. Discover why velocity should be used for internal team guidance, not for comparing across teams, and learn the best practices for tracking it effectively. This lesson highlights how steady velocity builds team confidence and drives consistent delivery of value.
Learn how Task Boards help Agile teams stay transparent, organized, and focused on the flow of work. In this lesson, you’ll explore the essentials of managing work visually through To Do, In Progress, and Done columns — whether on a physical board or a digital tool like Jira or Trello. Understand how task boards promote ownership, make standups more effective, and help teams spot bottlenecks early. You’ll also see how Work In Progress (WIP) Limits keep the team focused on finishing rather than starting too many tasks at once.
Master how to track progress effectively using Burndown and Burnup Charts — two essential Agile tools for sprint visibility. In this lesson, you’ll learn how Burndown Charts help monitor work remaining and how Burnup Charts highlight work completed along with any scope changes. Understand when to use each chart and how they keep your team aligned, informed, and proactive throughout the sprint. Whether you prefer daily sprint tracking or a big-picture view of progress, these charts help teams stay on track and respond early to issues.
Learn how popular Agile tools like Jira and Trello help teams manage backlogs, sprints, and workflows — without losing focus on what really matters: people and process. This lesson provides a tool-agnostic overview of how these platforms support Agile practices like task boards, sprint planning, story points, and collaboration. Whether you’re working with feature-rich Jira or lightweight Trello, the key takeaway is this: the right tool is the one that fits your team’s needs and reflects your actual process. Agile is about visibility, flexibility, and teamwork — not just the tools you use.
Understand what Technical Debt really means and why it’s one of the biggest hidden risks in Agile projects. In this lesson, you’ll explore how shortcuts taken to meet deadlines can accumulate into messy code, causing slower development, frequent bugs, and developer frustration over time. Learn how to identify the symptoms of technical debt, why managing it is a shared responsibility between Product Owners and Scrum Masters, and how to prioritize cleanup work alongside feature development. This lesson highlights the importance of balancing speed with sustainability for long-term Agile success.
Learn the fundamentals of Kanban, an Agile method designed for teams handling continuous, unpredictable work like support, maintenance, or operations. This lesson introduces Kanban boards, flow-based work management, and the principles that make Kanban effective — including visualizing work, limiting Work In Progress (WIP), and managing flow. Understand how Kanban helps teams reduce bottlenecks, avoid multitasking, and focus on steady progress without sprints. Whether you’re in a support environment or just need more flexibility, this lesson shows how Kanban keeps work flowing smoothly.
Learn how WIP Limits (Work In Progress Limits) and Continuous Delivery help Agile teams stay focused, reduce bottlenecks, and deliver value faster. In this lesson, you’ll explore how limiting active work encourages team collaboration, reduces context switching, and improves cycle time. See why “Stop starting. Start finishing.” is a core principle of effective Kanban teams. Understand how managing WIP unlocks continuous flow, allowing for small, frequent, reliable releases — without waiting for the end of a sprint.
Discover Scrumban, the hybrid Agile approach that combines the structure of Scrum with the flexibility of Kanban. In this lesson, you’ll learn when and why Scrumban is the right fit — especially for teams managing both planned work and urgent requests. Understand how Scrumban blends sprint ceremonies, roles, and cadence with WIP limits, flow metrics, and continuous task pulling. Whether your team is transitioning from Scrum to Kanban or needs both predictability and adaptability, Scrumban offers a balanced solution for mixed workflows.
Understand the key differences between Scrum, Kanban, and Scrumban and how each approach supports different types of Agile work. In this lesson, you’ll explore how these frameworks handle cadence, roles, work management, and commitment, and discover which method fits best based on your team’s needs. Learn why Scrum is ideal for iterative product development, Kanban suits support or continuous workflows, and Scrumban offers flexibility for hybrid or transitioning teams. This side-by-side comparison helps you choose the right Agile approach — and encourages you to adapt based on your unique context.
Explore the daily routine of a Scrum Master and understand how this role supports Agile teams beyond just managing meetings. In this lesson, you’ll follow Sam, the Scrum Master, as he facilitates standups, removes blockers, promotes transparency, and guides the team through servant leadership. Learn how a Scrum Master helps maintain focus, fosters collaboration, and drives continuous improvement through activities like coaching, unblocking, and process enhancement. This lesson highlights how the Scrum Master protects the Agile process and creates an environment where the team can succeed.
Step into the daily routine of a Product Owner and understand how they keep the Agile team aligned with business goals and customer needs. In this lesson, you’ll follow Alex, the Product Owner, through key activities like backlog refinement, stakeholder collaboration, sprint planning preparation, and reviewing product metrics. See how a Product Owner prioritizes work, ensures clear user stories, and balances both short-term sprint goals and long-term product vision. This lesson highlights the critical role of the Product Owner as the voice of the customer, focused on prioritization, clarity, communication, and alignment.
Experience a day in the life of a Developer and QA Lead working together on an Agile team. This lesson follows Ravi (Developer) and Lena (QA Lead) through their daily tasks — from daily standups and coding to unit testing, functional testing, bug fixing, and regression testing. See how Agile teamwork removes silos and fosters real-time collaboration between development and QA, ensuring faster delivery of high-quality, working software. Understand the flow of work from build → test → improve → repeat, and learn how shared ownership between developers and testers leads to smoother progress and better outcomes.
Explore the key differences between Component Teams and Cross-Functional Teams and how team structure impacts collaboration, feedback loops, and delivery speed. In this lesson, you’ll learn why Agile promotes cross-functional teams where developers, testers, analysts, and product owners work together as one unit — eliminating handoffs and delays. Understand how shared ownership and multi-skilled teamwork lead to faster feedback, better collaboration, and smoother delivery. This lesson highlights how breaking silos and working together drives Agile success.
Discover how Agile teams foster meaningful and continuous collaboration with stakeholders. In this lesson, you’ll learn how stakeholder involvement through Sprint Reviews, feedback loops, and transparent communication helps ensure that the product meets business needs and adapts to changing priorities. See how the Product Owner bridges the gap between stakeholder input and team delivery, turning ideas into actionable user stories. This lesson highlights why Agile treats stakeholders as partners, not just approvers — leading to faster alignment, fewer surprises, and better outcomes.
Step into the daily routine of a Business Analyst on an Agile team. In this lesson, you’ll follow Neha, the Business Analyst, as she collaborates with stakeholders, refines user stories, participates in standups, and helps keep the backlog clear and actionable. Learn how a BA bridges the gap between business needs and development, drafts effective user stories using the INVEST criteria, and supports the team through process flows, clarifications, and backlog refinement. This lesson offers real-world insight into the BA role and its critical contribution to Agile success.
Explore the most recognized Agile and Scrum certifications to help boost your career and validate your skills. In this lesson, you’ll learn about popular credentials like PSM I (Scrum.org), CSM (Scrum Alliance), SAFe Scrum Master (Scaled Agile), and PMI-ACP (Agile Certified Practitioner). Understand the key differences between these certifications, including exam format, training requirements, focus areas, and who each certification is best suited for. This overview helps you choose the certification path that aligns with your experience, learning style, and career goals.
Understand how the concepts covered in this course align with popular Scrum certification exams like PSM I, CSM, and SAFe Scrum Master. This lesson connects your learning on Scrum roles, events, artifacts, the Definition of Done, and empiricism directly to what certification exams test. You’ll also explore important exam-related topics such as estimation techniques, velocity, Kanban vs. Scrumban, and stakeholder collaboration. Designed to reinforce both your theoretical understanding and practical skills, this lesson helps you prepare confidently for certifications while applying Agile effectively in real-world projects.
This course contains the use of artificial intelligence.
Tired of Agile theory that feels disconnected from real work? This course brings Agile and Scrum to life with live scenarios, hands-on role plays and visual storytelling — so you don’t just learn Agile, you experience it.
Watch how a real-world Agile team collaborates sprint by sprint. Follow the journeys of a Scrum Master, Product Owner, Business Analyst, Developer, QA, and Stakeholder as they deal with common challenges, blockers, planning issues and feedback cycles.
This isn’t just another Agile course. You’ll engage in realistic role plays, explore Agile metrics and gain practical insights you can actually use on the job.
What You’ll Learn
Agile, Scrum, Kanban, and Scrumban fundamentals
Scrum roles, events, artifacts — in action
Writing clear user stories and acceptance criteria
Using Planning Poker, WIP limits, retrospectives, and dashboards
Understanding velocity, lead time, cycle time, CFDs
Managing blockers, stakeholder feedback and scope changes
**What’s New – Downloadable Excel Tool Included:**
As part of your learning experience, you’ll now get access to an Agile Maturity Self-Assessment Tool to evaluate your team across five key Agile dimensions: Planning & Estimation, Team Collaboration, Feedback Loops, Flow & Delivery and Agile Values.
Who Should Enroll
Perfect for both beginners and professionals, including:
Aspiring Scrum Masters & Product Owners
Business Analysts, Developers and QA/Testers
Anyone preparing for Agile or Scrum certification
Teams moving to Agile or improving Agile maturity
Why This Course Stands Out
Visual stories and illustrated team simulations
Interactive role plays to practice conversations and decision-making
Real-world Agile metrics and dashboards
No fluff, no boring slides — just practical, team-based learning
No prior Agile experience needed — just a willingness to explore, observe and participate.