Scrum Developer I — AI

The reasoning beneath a Developer's work: Agile values and principles from a builder's perspective, the three pillars of empiricism applied to engineering, the Scrum values as Developers live them, lean and flow thinking, and why inspection matters more when output becomes cheap to generate.

The Scrum framework as Developers own it: their accountabilities, the how of Sprint Planning, the Sprint Backlog as a living forecast, the Daily Scrum as the Developers' event, their part in Review and Retrospective, and using AI as an input to estimation rather than a substitute for the team.

The technical craft that makes Done real: the Definition of Done as a quality commitment, the difference between done and looks-done, test-first development, continuous integration and delivery, technical debt and refactoring, version-control discipline, code review, and pairing.

Implementing a specification that carries acceptance criteria with AI as a teammate, while the Developer stays accountable for verification, security, licensing and the Definition of Done: implementation prompting, critical review of generated output, the generate-then-verify loop, AI-written tests, agentic workflows, provenance, and when not to use AI at all.

A Developer's work is team work: cross-functionality and T-shaped skill, collaborating with the Product Owner and Scrum Master, professional responsibility for security, privacy, accessibility and ethics including in AI-assisted output, sustaining skill as tools change, and agreeing team-wide AI practice.