Yes, but the hands-on work is case-based rather than lab-based. Most of the practice is guided through quizzes and applied exercises, and the course also includes peer-reviewed work where you argue for Agile in a project case and create a story map for a fictional mobile app. That gives you a chance to use the ideas in realistic team situations instead of only reading about them.

You'll cover the Agile mindset, when Agile fits a project, and how it differs from predictive approaches. The course then moves into requirements and planning work, and into the team practices behind Scrum and XP. By the end, you'll have a practical picture of how Agile teams gather needs, plan releases, track work, and improve over time.

After finishing, you should be able to participate more effectively on an Agile software team and explain why common Agile practices are used. You'll be able to write and critique user stories, take part in planning and tracking work, and spot common problems teams run into when adopting Agile. For example, you should be able to look at a project situation, argue whether Agile fits, and outline work through a story map or release plan.

It's more concept-first, with guided practice to reinforce the ideas. Most of the course focuses on understanding Agile practices and team workflows, then applying them through quizzes, case studies, and peer-reviewed assignments rather than technical build work.