The craft of helping teams actually deliver
All sorts of things decide whether a team delivers or just spins – most of them outside your control. The practice is the part you can shape, and that is what this track is about. Scrum Master and Product Owner foundations cover the roles at the centre of most teams; the SAFe roles extend them to scaled settings; and agile requirements and architecture address the parts that quietly decide whether a sprint produces value or just motion – well-formed work, and a design that can keep changing.
Good agile practice is inseparable from the engineering practice underneath it. Behaviour-driven and test-driven development are what give “done” a meaning you can trust rather than a checkbox someone ticks; they turn “the team is agile” from a ceremony schedule into demonstrable, finished work. Facilitating a team that cannot tell finished from nearly-finished is facilitating a slow-motion problem.
AI is simply the newest change you have to facilitate. When a developer can generate a feature in an afternoon, the ceremonies, estimates, definition of done and flow of work shift underneath you – and “the tool will sort it out” is not a facilitation strategy. So the track adds AI for agile practitioners for the day-to-day craft and enough tool exposure that you facilitate from understanding rather than vibes.
The real risk is not too little AI, but “done” quietly losing its meaning while everyone feels faster. Keeping flow, feedback and finished-means-finished honest is the job. For the developer journey your teams take, see the AI-Assisted Software Development path.