The Coders Guild offered clear and practical insights into generative AI, which we’ve started applying in our business. The course was well-structured and relevant to our needs, making the learning process straightforward and effective.
The Coders Guild led the research and development that produced the UK’s first Level 4 AI and Automation apprenticeship standard — built with Skills England and the Alan Turing Institute after a year of research into what SMEs actually need from AI training. We’re not reselling someone else’s framework. We designed it, and we’re running the first cohorts now.
Our trainers work in the field. Every programme is delivered by industry practitioners — people using these tools in real businesses, not academics teaching from a curriculum. That means what gets taught reflects how AI and automation work in practice, not how they looked two years ago.
Built for smaller businesses. Most AI training is designed with enterprise budgets and infrastructure in mind. Ours isn’t. Everything we do is built around the constraints and opportunities of SMEs — businesses where one capable person can genuinely change how the whole organisation works.
Pick the one that matches where you are. If it’s not obvious, tell us what you’re working with and we’ll point you right.
Spend, policy, risk, who on the team needs what. AI for Leaders is six weeks that take you from using the tools to leading the doing.
Grow your own AI capability with fully funded, hands-on training. Your people learn on real work in your business, on the UK’s Level 4 AI and Automation apprenticeship, the standard we created with Skills England.
Closed cohorts on your dates, up to twelve people, built around how your business actually works. One conversation tells you what fits.
Want to go deep yourself? Our courses run from Foundations through Intermediate to Advanced. See them all below.
“Businesses need outputs, not certifications. That’s why our training returns value fast: people do the work on your business, instead of watching videos and hoping some of it sticks.”
Crispin Read – who led the R&D on the UK’s new Level 4 AI and Automation standard with Skills England
Every business is different. If you’re unsure which option works best, or you need something more tailored to your specific challenges, fill in the form and we’ll send you some options and arrange a call.
"*" indicates required fields
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Agile project management is how modern teams plan, organise and deliver work iteratively and collaboratively. It’s less about rigid plans and more about adapting to change, delivering value incrementally, and continuously improving how work gets done. AI is changing how Agile teams work — from accelerating backlog refinement and sprint planning to generating retrospective insights and automating reporting. Teams that understand how to work alongside AI tools are delivering faster and with less friction. Our training covers modern Agile practice, including how these tools fit into the workflow.
The Coders Guild led the research and development that created the UK’s first Level 4 AI and Automation apprenticeship standard with Skills England and the Alan Turing Institute. That thinking runs through our Agile training too — including our Skills Bootcamp in Agile Project Management with AI and Digital Tools.
Every business is different. If you’re unsure which option works best, or you need something more tailored to your specific challenges, fill in the form and we’ll send you some options and arrange a call.
"*" indicates required fields
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
No. While project management experience can help, it’s not required and sometimes creates habits you need to unlearn.
Traditional project management focuses on detailed planning, tracking against plans, and controlling work. Scrum Masters focus on facilitating self-organising teams, enabling empirical process, and continuous improvement. These require different mindsets.
Successful Scrum Masters come from diverse backgrounds – teaching, coaching, software development, business analysis, customer service. What matters is facilitation skills, understanding team dynamics, and embracing Agile principles.
Project management experience helps with stakeholder management and understanding organisational context. But pure project managers sometimes struggle with reduced control and servant leadership aspects of Scrum Master role.
These are distinct roles with different responsibilities:
Scrum Master focuses on how the team works – facilitating ceremonies, removing impediments, coaching Agile practices, helping team self-organise and improve. The Scrum Master serves the team and protects them from distractions.
Product Owner focuses on what the team builds – managing backlog, prioritising work, defining requirements, accepting completed work, maximising value delivered. The Product Owner serves stakeholders and customers.
In analogy: Product Owner decides what should be built. Scrum Master helps team build it effectively.
Product Owners need deep product and domain knowledge, stakeholder management skills, and commercial understanding. Scrum Masters need facilitation skills, understanding of team dynamics, and Agile expertise.
The roles collaborate closely but should not be combined – they represent different concerns and can create conflicts of interest when combined.
Certification isn’t legally required but is often expected by employers:
Benefits of certification:
Limitations of certification:
Recommended certifications:
Get certified to open doors and demonstrate baseline knowledge. But focus equally on developing practical skills through experience, reading, and community engagement.
Our Agile Planning with Lego Workshop and Impact Mapping and MVP Workshop are both half-day sessions — quick, high-impact, and easy to fit around work. The Agile Project Management Essentials Short Course is a multi-session programme covering tools and practice in more depth. Get in touch and we’ll send you the current schedule and details.
Scrum and Kanban are both Agile frameworks but take different approaches:
Scrum:
Kanban:
When to use which:
Scrum works well for teams building products with clear release cycles, needing regular planning and review, or starting Agile journey (structure helps learning).
Kanban suits operational teams with continuous work flow, teams with frequent priority changes, or teams wanting flexibility without prescribed ceremonies.
Many teams combine elements (“Scrumban”) – using Kanban boards within Scrum framework, or adding Scrum ceremonies to Kanban flow.
This is core challenge of Agile roles – you have responsibility without authority. Here’s how successful Agile practitioners handle it:
Build trust: Teams follow people they trust. Demonstrate you’re there to help, not control. Protect them from distractions. Remove impediments effectively. Show consistent support.
Ask good questions: Rather than telling teams what to do, ask questions that help them discover solutions. “What’s blocking progress?” “What would need to happen for this to work?” “What did we learn from last sprint?”
Focus on enabling, not controlling: Your success comes from team’s success. Make it easy for them to work effectively. Remove obstacles. Create clarity. Facilitate collaboration.
Use data: Metrics and visualisation make problems visible without you having to point them out. Burndown charts show if work is on track. Retrospectives surface issues teams identify themselves.
Work the system: When teams need things outside your control, work organisational channels to get results. Build relationships with people who can help. Escalate effectively.
Let go: Resist urge to solve problems for team. Self-organising teams solve their own problems. Your job is creating conditions for them to do so.
Significantly. Agile teams are already using AI to write and refine user stories, generate sprint retrospective summaries, analyse velocity data and flag delivery risks, and automate the reporting that used to eat half a sprint review. AI also changes how teams work during discovery — generating hypotheses faster, analysing user feedback at scale, and running competitive analysis that used to take days. Our Skills Bootcamp specifically covers Agile with AI and digital tools, and our other courses reflect modern delivery practice rather than a version of Agile frozen in 2015.
It depends on what you need. The Agile Planning with Lego Workshop is our most popular option for teams who want to understand Agile principles quickly through doing rather than theory — a half-day that changes how people think about delivery. The Impact Mapping and MVP Workshop suits teams building products who need to cut scope and focus on what matters. The Agile Project Management Essentials Short Course is for individuals wanting a practical grounding in tools and techniques. The Skills Bootcamp is the most in-depth and is fully funded for eligible learners in West Yorkshire. If you’re not sure, get in touch and we’ll point you in the right direction.
Yes — and this is more common than people expect. Agile methods were developed in software but the principles apply across marketing, operations, HR, finance, and any team that deals with changing priorities, iterative work, and stakeholder management. We regularly work with non-tech teams who want to work more effectively and deliver more predictably. The workshops in particular are designed to be accessible regardless of industry or technical background.
Agile is a set of principles and practices for managing work in environments where requirements change, priorities shift, and the best solutions emerge through collaboration and iteration. Rather than planning everything upfront and executing a fixed plan, Agile teams work in short cycles, deliver working outputs frequently, and adapt based on feedback.
The approach originated in software development but now extends across many fields – marketing, product development, operations, even HR and finance. Any work involving uncertainty, complexity, or changing requirements benefits from Agile thinking.
Agile isn’t a single methodology – it’s an umbrella term covering several frameworks. Scrum is most common, involving sprints (time-boxed work periods), daily standups, sprint planning, and retrospectives. Kanban focuses on visualising work, limiting work in progress, and continuous flow. Other approaches include Extreme Programming (XP), SAFe (Scaled Agile Framework), and hybrid models.
What makes work “Agile” isn’t following specific rituals – it’s embodying certain principles. Delivering working solutions frequently. Collaborating closely with stakeholders. Responding to change over following plans. Prioritising individuals and interactions over processes and tools. Continuously reflecting and improving.
Agile project management roles exist across most tech organisations and increasingly beyond tech. Scrum Masters facilitate Agile teams and remove impediments. Product Owners manage backlogs and prioritise work. Delivery Managers coordinate across teams. Agile Coaches help organisations adopt and improve Agile practices. Project Managers in Agile environments focus on outcomes and flow rather than detailed upfront planning.
The work is collaborative and communication-heavy. You’re facilitating conversations, resolving blockers, helping teams self-organise, and creating visibility around work. If you enjoy helping teams work better together and shipping valuable work consistently, Agile project management might suit you.
Agile roles exist across every sector now. Technology companies pioneered Agile, but financial services, healthcare, retail, government, and manufacturing all use Agile approaches. The principles transfer – helping teams collaborate, prioritise effectively, and deliver iteratively works regardless of industry.
Agile project management requires understanding frameworks, facilitating teams, and helping organisations deliver work effectively:
Agile principles and values: Understanding the Agile Manifesto, the principles behind Agile approaches, and why Agile emerged as alternative to traditional project management.
Framework knowledge: Deep understanding of at least one Agile framework – typically Scrum or Kanban. Understanding ceremonies, artifacts, roles, and the theory behind practices.
Iterative delivery: Understanding how to break work into valuable increments, deliver frequently, gather feedback, and adapt based on learning.
User stories: Writing effective user stories that describe value from user perspective. Understanding acceptance criteria, story splitting, and prioritisation.
Estimation and planning: Techniques for estimating work in uncertain environments. Story points, t-shirt sizing, relative estimation. Understanding velocity and capacity.
Sprint planning: Facilitating effective sprint planning sessions. Helping teams understand goals, select work, create sprint plans, and commit to achievable goals.
Daily standups: Running focused daily standups that promote transparency, identify blockers, and enable collaboration without becoming status meetings.
Sprint reviews: Facilitating sprint reviews that demonstrate working solutions, gather feedback, and inform next steps.
Retrospectives: Leading retrospectives that help teams reflect honestly, identify improvements, and commit to changes. Creating psychological safety for honest discussion.
Backlog management: Helping Product Owners maintain healthy backlogs – prioritised, refined, with clear acceptance criteria. Understanding backlog grooming and refinement.
Visualising workflow: Creating Kanban boards that accurately represent how work flows through the team. Making work visible and transparent.
Work in progress (WIP) limits: Setting and maintaining WIP limits to prevent overload, identify bottlenecks, and improve flow.
Flow metrics: Understanding cycle time, lead time, throughput. Using flow metrics to identify improvement opportunities.
Continuous improvement: Making incremental improvements to workflow based on metrics and team observations.
Facilitation skills: Running effective meetings and workshops. Keeping discussions focused, ensuring everyone contributes, reaching decisions efficiently.
Conflict resolution: Addressing team conflicts constructively. Helping people with different perspectives find solutions.
Stakeholder management: Communicating with stakeholders outside the team. Managing expectations, providing visibility, gathering input.
Coaching: Helping team members develop Agile mindset and skills. Asking questions rather than providing answers. Supporting self-organisation.
Active listening: Really hearing what people say, understanding underlying concerns, noticing what’s unsaid. Essential for effective facilitation.
Removing impediments: Identifying and removing blockers that prevent teams from making progress. Sometimes this means solving problems, sometimes it means escalating to people who can.
Creating psychological safety: Building environments where people feel safe to speak up, admit mistakes, ask questions, and challenge ideas.
Enabling team autonomy: Helping teams make their own decisions rather than directing them. Creating conditions for self-organisation.
Protecting the team: Shielding teams from unnecessary distractions and interruptions. Saying no to requests that would compromise team focus or commitments.
Agile metrics: Understanding which metrics provide useful insights – velocity, burndown, cycle time, lead time. Knowing which metrics create harmful behaviours.
Value metrics: Moving beyond output metrics (story points completed) to outcome metrics (value delivered, problems solved, user satisfaction).
Team health indicators: Recognising signs of healthy and unhealthy team dynamics. Using qualitative and quantitative signals.
Project management tools: Jira is most common, but also Azure DevOps, Monday.com, Asana, Trello, ClickUp. Understanding how to configure tools to support Agile workflows without creating admin overhead.
Collaboration tools: Miro or Mural for virtual collaboration and workshops. Confluence for documentation. Slack or Teams for communication.
Visualisation tools: Creating burndown charts, cumulative flow diagrams, dependency maps. Making information radiators that provide at-a-glance project status.
Scaled Agile frameworks: Understanding how Agile works when multiple teams coordinate – SAFe, LeSS, Scrum@Scale. Knowing when scaling frameworks help versus create overhead.
Organisational change: Understanding how organisations adopt Agile. Recognising cultural barriers and navigating organisational politics.
Agile beyond software: Adapting Agile principles to non-software contexts. Understanding what’s essential versus what’s software-specific.
Emotional intelligence: Reading room dynamics, understanding motivations, recognising when people are frustrated or disengaged. Essential for facilitation and coaching.
Patience and persistence: Agile adoption is gradual. Cultural change takes time. Helping teams improve requires patience and consistent reinforcement.
Flexibility and pragmatism: Knowing when to follow frameworks strictly versus when to adapt. Balancing Agile purity with organisational reality.
Systems thinking: Understanding how changes in one area affect others. Seeing beyond individual teams to organisational flow.
Agile project management offers several distinct career paths with different focuses:
Junior Scrum Master / Agile Coordinator: Supporting Agile teams, facilitating basic ceremonies, helping with backlog management, learning Agile practices. Often working under experienced Scrum Master or Agile Coach. Salary: £25,000 – £35,000.
Entry roles focus on learning Agile frameworks, understanding team dynamics, and developing facilitation skills. You’ll observe experienced practitioners, assist with ceremonies, and gradually take on more responsibility.
Project Coordinator / Delivery Coordinator (Agile): Supporting delivery managers or project managers in Agile environments. Tracking progress, coordinating meetings, maintaining documentation. Salary: £24,000 – £32,000.
Scrum Master: Facilitating one or more Agile teams. Running all Scrum ceremonies, coaching team members, removing impediments, helping teams self-organise and improve. Salary: £35,000 – £55,000.
At this level you’re independently facilitating teams, making judgment calls about how to apply Agile practices, and helping teams navigate challenges. You understand when to follow frameworks and when to adapt.
Product Owner: Managing product backlogs, prioritising work, defining requirements, accepting completed work, maximising value delivered. Balance between stakeholder and team. Salary: £40,000 – £60,000.
Product Owners need deep product knowledge and stakeholder management skills. You’re constantly making prioritisation decisions and trade-offs between competing needs.
Agile Delivery Manager: Coordinating delivery across multiple teams or complex initiatives. Ensuring teams have what they need, managing dependencies, communicating progress to stakeholders. Salary: £40,000 – £60,000.
Delivery Managers focus on flow and outcomes across multiple teams. You’re less involved in individual team ceremonies, more focused on coordination and removing organisational impediments.
Senior Scrum Master: Facilitating complex teams or multiple teams. Mentoring junior Scrum Masters. Influencing organisational Agile adoption. Leading community of practice. Salary: £50,000 – £70,000.
Senior Scrum Masters often work with teams facing particular challenges – distributed teams, complex technical work, organisational change. You’re expected to handle difficult situations and coach others.
Agile Coach: Coaching teams, leaders, and organisations on Agile adoption and improvement. Working at multiple levels – team, management, organisation. Helping organisations transform ways of working. Salary: £55,000 – £80,000+.
Agile Coaches work beyond individual teams, helping organisations understand and adopt Agile principles. You’re influencing culture, working with leadership, and enabling organisational change.
Senior Product Owner / Product Manager: Managing complex products or multiple related products. Strategic product direction. Leading other product owners. Salary: £55,000 – £80,000+.
Head of Delivery / Delivery Director: Leading delivery function across organisation. Defining delivery standards, managing delivery managers, reporting to executives. Salary: £65,000 – £95,000+.
Agile Transformation Lead: Leading organisation-wide Agile transformation. Strategic planning, executive coaching, change management. Designing and implementing Agile operating models. Salary: £70,000 – £100,000+.
Head of Agile Practice: Building and leading Agile coaching practice. Hiring coaches and Scrum Masters, defining standards, measuring Agile maturity. Salary: £75,000 – £110,000+.
Technical Agile Coach: Agile coaching with deep technical expertise. Helping engineering teams adopt technical practices like TDD, continuous integration, pair programming alongside Agile frameworks.
Agile Portfolio Manager: Managing portfolio of initiatives in Agile organisation. Prioritising across teams, managing budgets, aligning delivery to strategy.
Release Train Engineer (SAFe): Facilitating Agile Release Train in scaled environments. Coordinating multiple teams, managing programme-level ceremonies, ensuring alignment.
Agile skills open doors to product management (combining product ownership with strategy), programme management (coordinating complex initiatives), organisational development (helping organisations change), or management consulting (advising organisations on Agile adoption).
Agile roles suit people who enjoy facilitating collaboration, solving organisational problems, and helping teams work more effectively.
Enjoy enabling others: Agile roles are servant leadership – your success is measured by how well teams perform, not personal achievement. If you get satisfaction from helping others succeed, you’ll find this rewarding.
Comfortable with ambiguity: Agile embraces change and uncertainty. Plans evolve. Priorities shift. You need to be comfortable working without perfect information and helping others navigate ambiguity.
Strong communication skills: Much of Agile work involves communication – facilitating discussions, resolving conflicts, explaining concepts, managing stakeholders. Clear communication is essential.
Systems thinking: Understanding how different parts of organisations interact, how changes ripple through systems, how to improve overall flow rather than just local optimisation.
Patience and persistence: Organisational change is slow. Teams don’t transform overnight. You need patience to help teams gradually improve and persistence to maintain focus on improvement.
Emotionally intelligent: Reading team dynamics, understanding motivations, recognising when people are struggling. Agile facilitation requires emotional awareness and empathy.
Project managers: Traditional project managers moving to Agile environments. You bring project management skills and learn different approaches to planning and control.
Business analysts: BAs moving into Product Owner roles. You understand requirements and stakeholder management – adding backlog management and Agile prioritisation.
Developers and testers: Technical people moving into Scrum Master roles. You understand the work teams do and add facilitation and coaching skills.
Complete career changers: People from teaching, coaching, facilitation, or other fields who enjoy helping teams work better. You bring people skills and learn Agile practices.
People who genuinely care about teams and organisational effectiveness. Those who ask good questions rather than providing all answers. Individuals comfortable with servant leadership rather than command and control. People who can balance framework adherence with pragmatic adaptation.
Age and background don’t matter. Agile roles value maturity, life experience, and emotional intelligence – often developed through varied careers. Many successful Agile practitioners came to the field mid-career.
You don’t need to be extroverted. Good facilitation comes from listening, asking questions, and creating space for others – not from being loudest voice in room.
Organisational resistance: Agile changes how organisations work. You’ll face resistance from people comfortable with traditional approaches or protective of territory.
Lack of authority: Scrum Masters and Agile Coaches have responsibility without direct authority. You influence without control, which can be frustrating.
Competing interpretations: Agile frameworks can be interpreted differently. People disagree about “proper” Agile. Navigating these discussions requires diplomacy.
Measuring impact: Your impact is indirect – teams deliver work, you help them work better. Quantifying your contribution is difficult.
Constant context switching: Facilitating multiple teams or working across organisation means constant context switching between different team dynamics and challenges.
Visible impact: When teams improve – shipping faster, communicating better, feeling more engaged – you see tangible results from your facilitation.
Variety: No two teams are the same. Every day brings different challenges, conversations, and problems to solve.
Continuous learning: Understanding team dynamics, organisational change, facilitation techniques. Agile roles provide endless learning opportunities.
Helping people: Genuinely helping teams work better, be happier, and deliver more value. If you care about people, this work is satisfying.
Intellectual challenge: Navigating organisational complexity, understanding systems, finding elegant solutions to messy problems. Agile work is intellectually engaging.
Agile project management is easier to enter than many tech careers – you don’t need coding skills or deep technical background:
Learn Agile fundamentals:
Free resources are plentiful. The Scrum Guide is free and authoritative. Mountain Goat Software offers free Agile resources. YouTube has countless Agile tutorials and ceremony examples.
Get certified: While not required, certifications provide structured learning and credibility:
Certifications help you learn frameworks systematically and demonstrate commitment, but they don’t replace practical experience. Many organisations hire certified Scrum Masters, so certification can open doors early in your career.
Agile roles require practical experience, which creates catch-22 for beginners. Here’s how to build experience:
Practice Agile in your current role: Even if your organisation isn’t Agile, you can apply Agile principles to your own work:
Volunteer to support Agile teams: If your organisation uses Agile, volunteer to help:
Run Agile experiments: Introduce Agile practices to non-Agile teams:
Document these experiences. When interviewing for Agile roles, you can discuss how you applied Agile thinking, what worked, what you learned.
Agile roles are heavily focused on facilitation. Build these skills:
Practice facilitating meetings: Volunteer to run team meetings, workshops, or planning sessions. Focus on keeping discussions focused, ensuring everyone contributes, and reaching clear outcomes.
Learn facilitation techniques: Study facilitation approaches – how to ask good questions, handle difficult participants, manage time, reach decisions.
Develop active listening: Practice really hearing what people say, understanding underlying concerns, reflecting back what you’ve heard.
Study conflict resolution: Learn how to address disagreements constructively, help people find common ground, and move forward.
Learn about team development: Understand Tuckman’s stages (forming, storming, norming, performing), team health indicators, psychological safety.
Study organisational change: Read about how organisations adopt new practices, why people resist change, how to influence without authority.
Understand technical work: Even if you’re not technical, understanding basics of software development, testing, and deployment helps you facilitate technical teams effectively.
Apprenticeships: Agile project management apprenticeships provide structured learning while working in real Agile roles. Duration: 15-18 months. Government-funded for qualifying employers.
Apprenticeships suit people transitioning from other roles or entering the field. You’ll work with experienced Agile practitioners while building skills systematically.
Certification courses: CSM (Certified ScrumMaster) courses combine training with certification. Two-day intensive courses teach Scrum and prepare you for certification.
Self-taught route: Many Agile practitioners are self-taught through reading, online resources, and practice. Combine self-study with volunteering to help Agile teams in your organisation.
Entry-level Agile roles are competitive but attainable:
Target junior roles: Look for Junior Scrum Master, Agile Coordinator, or Delivery Coordinator positions. These expect less experience and provide learning opportunities.
Consider project coordinator roles in Agile organisations: Project support or coordination roles in Agile environments expose you to Agile practices. Once inside, you can transition to Scrum Master roles.
Leverage existing experience: If you have project management, business analysis, or team coordination experience, emphasise transferable skills – stakeholder management, planning, facilitation.
Highlight certifications and learning: Show you’ve invested in learning Agile – certifications, courses, books read, communities engaged with.
Demonstrate Agile mindset: In interviews, show you understand Agile principles, not just practices. Talk about iteration, collaboration, continuous improvement, responding to change.
Network: Join Agile communities, attend Agile meetups (local or virtual), engage on LinkedIn. Many Agile roles are filled through referrals.
The Coders Guild offers Agile project management apprenticeships covering Scrum, Kanban, delivery management, and Agile coaching. Training is practical, includes facilitating real teams, and is taught by experienced Agile practitioners.
Government funding is available for apprenticeships and qualifying programmes. Browse our Agile project management courses below or get in touch to discuss which route might work for you.
Junior Scrum Master / Agile Coordinator: £25,000 – £35,000 for entry-level roles supporting Agile teams.
Scrum Master: £35,000 – £55,000 for experienced Scrum Masters facilitating one or more teams independently.
Senior Scrum Master: £50,000 – £70,000 for senior practitioners facilitating complex teams or mentoring other Scrum Masters.
Product Owner: £40,000 – £60,000 for mid-level Product Owners. Senior Product Owners earn £55,000 – £80,000+.
Agile Delivery Manager: £40,000 – £60,000 for mid-level roles. Senior Delivery Managers earn £55,000 – £75,000.
Agile Coach: £55,000 – £80,000+ for experienced coaches working across teams and with leadership.
Head of Delivery / Agile Practice Lead: £65,000 – £95,000+ for leadership roles.
Salaries vary by location, sector, and organisation size. London pays 20-30% more than other regions. Financial services and technology typically pay more than other sectors. Larger organisations often pay more than SMEs.
Demand for Agile practitioners remains strong, though it has matured from the growth phase a decade ago:
Continued demand drivers:
Market realities:
Agile roles transitioned to remote work during COVID and many remain remote or hybrid:
Remote-friendly aspects: Many ceremonies and facilitation work well remotely with good tools (Zoom, Miro, digital boards). Some practitioners argue remote removes office distractions.
Challenges of remote: Building team cohesion, reading body language, having informal conversations, and facilitating collaborative workshops are harder remotely.
Hybrid common: Many organisations now offer hybrid – remote most days with occasional in-person collaboration for workshops, planning, or team building.
Junior roles sometimes benefit from in-person mentoring. Experienced practitioners work effectively remotely.
Agile contracting and consulting is common:
Contract Scrum Masters: £350-£550 per day depending on experience and location.
Contract Agile Coaches: £500-£800+ per day for experienced coaches, particularly those with SAFe or transformation experience.
Interim Delivery Managers: £400-£650 per day for managing delivery across teams.
Contracting typically requires several years of permanent experience first. Clients want proven capability and often specific certifications (SAFe, professional coaching credentials).
Agile careers offer good progression for people who develop both depth and breadth:
Depth in frameworks: Deep expertise in Scrum, SAFe, or organisational coaching commands premium rates.
Breadth of experience: Working across industries, team types, and organisational contexts makes you more valuable.
Leadership progression: Moving into management – leading Agile practices, managing coaches and Scrum Masters – increases compensation.
Consulting: Experienced Agile coaches can build successful consulting practices, either independently or with firms.
If you’ve got an event, collaboration or success story we should know about – get in touch.
FREE AI WEBINARS
Two short, practical AI sessions a month. Free. Drop your email and we’ll send you the link, plus the recordings of the ones you’ve missed.
"*" indicates required fields
