Plenty of teams can run a single Scrum sprint successfully; far fewer organisations manage to keep Agile working once it spreads across multiple teams, departments and stakeholders. This masterclass from the Arab British Fellowship Training Academy is aimed at that harder problem - it goes beyond the basics of Agile and Scrum into scaling practices, backlog discipline and the change-management skills needed to lead a real transformation.

The course walks through Scrum roles, events and artifacts as one connected system, then builds up estimation, monitoring and reporting skills that keep delivery visible without micromanaging teams. The final stretch tackles scaling frameworks such as SAFe, resistance to change, and the practical steps of running an organisation-wide Agile transformation.

• Compare Agile frameworks - Scrum, Kanban, XP and SAFe - and decide when each one fits.
• Apply Scrum roles, events and artifacts as one connected operating system, not separate checklist items.
• Write and refine user stories and backlogs that hold up as projects grow in complexity.
• Estimate work and monitor delivery using story points, velocity, burndown and cumulative flow.
• Scale Scrum across multiple teams using frameworks such as SAFe.
• Manage resistance to change and team dynamics during Agile adoption.
• Lead an organisation-wide Agile transformation, from roadmap to measured results.

Target Audience

• Project managers and Scrum Masters
• Product Owners and IT managers
• Software developers and business analysts
• Team leaders moving their teams into Agile
• Professionals leading or supporting an Agile transformation

Module 1: Why Organisations Move to Agile - and Where Adoption Breaks Down

• Agile vs traditional delivery: the real trade-offs
• Common reasons Agile adoption stalls
• What a masterclass-level practitioner needs beyond the basics

Module 2: Choosing and Comparing Agile Frameworks

• Scrum, Kanban, XP and SAFe compared
• Why Scrum remains the most common starting point

Module 3: Scrum Roles, Events and Artifacts in One Picture

• Roles: Product Owner, Scrum Master, Development Team
• Events: Sprint Planning through Sprint Retrospective
• Artifacts: Backlog, Sprint Backlog and Increment, kept in sync

Module 4: Backlogs, User Stories and Estimation

• Writing user stories that hold up under scrutiny
• Backlog grooming and refinement
• Story points, T-shirt sizing and Planning Poker

Module 5: Monitoring Delivery Without Micromanaging

• Burndown, burnup and cumulative flow diagrams
• Definition of Done versus Definition of Ready
• Keeping progress visible to stakeholders

Module 6: Scaling Scrum Beyond a Single Team

• Introduction to the Scaled Agile Framework (SAFe)
• Coordinating multiple Agile teams
• Strategies for large-organisation rollouts

Module 7: Managing the Human Side of Change

• Handling resistance to change
• Team dynamics and conflict resolution
• Building an Agile mindset and culture

Module 8: Leading an Agile Transformation

• Steps to initiate and lead a transformation
• Building an organisational Agile roadmap
• Measuring the success of Agile implementation