Agile & Scrum Fundamentals
Agile and Scrum foundations for new joiners and the colleagues around them: Manifesto values, the three Scrum accountabilities, sprint events, user stories and story-point estimation, with a scored sprint-sequencing exercise.
Who this is for
New joiners to agile teams, project managers transitioning from waterfall, and non-technical colleagues who work alongside Scrum teams
Learners will be able to
- Explain the four values of the Agile Manifesto and how they differ from plan-driven delivery
- Distinguish the accountabilities of the Product Owner, Scrum Master and Developers without conflating them with line management
- Sequence a full sprint correctly, from sprint planning through daily scrums to review and retrospective
- Write a user story with acceptance criteria that passes the INVEST checklist
- Apply relative estimation with story points and explain why velocity is a planning tool, not a performance metric
Template prompt
“Create an Agile and Scrum fundamentals module covering the Agile Manifesto, Scrum roles (Product Owner, Scrum Master, Dev Team), sprint ceremonies (planning, daily, review, retro), user stories, and estimation techniques. Include ordering exercises for sprint workflow.”
This prompt is fully editable. Customise it to match your audience, regulations, and learning objectives before generating.
What the 8 sections cover
- 1
Why Agile exists
Context panel on the delivery problems that plan-driven projects hit, and how the Agile Manifesto's four values and twelve principles respond to them.
- 2
The Scrum framework at a glance
A single visual diagram showing how roles, artefacts and events connect across one sprint loop, giving learners the map before the detail.
- 3
Three accountabilities, not job titles
Flashcards on Product Owner, Scrum Master and Developers, followed by a scored matching exercise pairing real responsibilities to the right accountability.
- 4
Sprint ceremonies walkthrough
Sprint planning, daily scrum, sprint review and retrospective explained with their purpose, participants and timeboxes for a typical two-week sprint.
- 5
Ordering exercise: run a sprint
A scored sequencing challenge where learners place the events and artefact updates of a complete sprint in the correct order.
- 6
User stories and acceptance criteria
The INVEST checklist applied to worked examples, contrasting a vague story with a well-sliced one that a team could actually pull into a sprint.
- 7
Estimation techniques
Story points, planning poker and velocity, with a scored scenario question asking learners to spot the estimation mistake in a mixed backlog.
- 8
Final knowledge check and key takeaways
Scored questions spanning roles, events, artefacts and common misconceptions, closing with a takeaway summary learners can revisit before their first sprint.
Structure is representative — the generator adapts sections to your edited prompt and passes every package through interactivity and visual-density quality gates.
Topics covered
Make it yours
- Name your sector in the prompt, for example a marketing or NHS operations team, so the user stories and sprint examples match real work your team does
- Upload your team's definition of done or working agreement and ask the module to reference it in the ceremonies section
- Swap the estimation section for your team's actual method, such as t-shirt sizing or right-sizing with cycle time, by stating it in the prompt
Frequently asked questions
Is this training aligned with the official Scrum Guide?
Yes. The content follows the current Scrum Guide, last revised in November 2020, which describes Scrum in terms of three accountabilities, five events and three artefacts. The 2025 Scrum Guide Expansion Pack is a supplement rather than a new version, so the 2020 Guide remains the official reference. Where common industry practices go beyond the Guide, such as story points and planning poker, the module flags them as complementary techniques rather than Scrum requirements.
Does completing this module give a Scrum certification?
No. Formal credentials such as Professional Scrum Master (Scrum.org) or Certified ScrumMaster (Scrum Alliance) require their own assessments through those bodies. This module is designed as team-level onboarding and shared vocabulary, and it works well as preparation before someone pursues a formal certification.
Who in the organisation should take Agile fundamentals training?
Anyone who works in or alongside an agile team benefits: developers and testers obviously, but also stakeholders, marketers and managers who attend sprint reviews or request work from the backlog. Teams frustrate each other most when half the room uses Scrum terms differently, so shared training across roles pays off quickly.
Can I adapt this for teams outside software development?
Yes. Scrum is used by marketing, HR, operations and research teams across the UK. Mention your sector in the prompt and the generated examples, user stories and sprint scenarios will reflect your kind of work instead of software features.
Ready to make it yours?
Customise the prompt, generate a draft, then review the content and SCORM package before delivery.
Related templates
Code Review Best Practices
Quick microlearning on writing better code reviews — checklist items, constructive framing, and security focus areas.
Delegation Skills for Team Leads
Practical delegation framework covering the delegation spectrum, task matching, and accountability without micromanagement.
Team Kick-off Icebreaker
Warm-up session for new or re-formed project teams — introductions with a twist, live working-style polls, and a closing round that surfaces how people actually want to work together.