The curriculum is either an agile tool or an obstacle. A teacher can be an excellent agile practitioner in their own classroom, but if the curriculum they're delivering is structured as a rigid day-by-day delivery schedule with no slack, no modular flexibility, and assessments that only report outcomes rather than inform next steps — agile teaching becomes impossible to sustain.
Something has to give, and usually it's the teacher. This cluster is for the people who design and build curriculum — whether that's a school's head of department building a scheme of work, or a curriculum creator building a course for the marketplace.
The question is the same: how do you design curriculum that supports iteration rather than resisting it? 📚 This cluster is relevant to both schools and creators. School curriculum teams design schemes of work.
Marketplace creators design courses. Both benefit from building agile-compatible structure into the curriculum from the start, rather than retrofitting it later.