David Sabine

@davidsabine
37 Followers
29 Following
1,020 Posts
Founder Betterteams.Academy
Professional Scrum Trainer @Scrumdotorg
Professional Kanban Trainer @prokanban
Formerly @Metrist_io, @CodingDojoDotCo, @digitalocean, @OriumInc
wwwhttps://betterteams.academy
Xhttps://X.com/DaveSabine
linkedinhttps://ca.linkedin.com/in/davidsabine
Scrum teams are cross-functional, self-managing, and capable of converting Product Backlog into releasable functionality every Sprint.
Workflows, skills, and techniques are changing rapidly as new AI tools reach the market. A team that does not frequently reflect on these mutations may get stuck in a perpetual loop of forming → storming → reforming ⟳.
Retrospectives are opportunities for honest reflection and deliberate evolution of working agreements.
The Daily Scrum is a brief dialogue among developers who inspect their progress and adapt their daily plan toward the Sprint Goal.
Sprints are time-boxed experiments.

Teams can earn stakeholder’s trust and improve shared understanding by explicitly declaring how AI-generated material is used, verified, and integrated.

For example: include this info in your team's Definition of Done.

Consider adding to your Definition of Done:

* AI-generated code is clearly marked
* No AI model outputs in production code not covered by human-managed acceptance tests
* Prompt + model version + date recorded for significant AI-generated sections

Given the current trends with AI tools, it appears likely executives may finally understand my advice to keep teams small.

If my clients would listen to just one piece of advice:

* teams are the most valuable performance unit.
* small teams adapt faster than large teams.

(that's 2 pieces of advice)

AI trends indicate that, as cognitive grunt work vanishes, small teams are able to make rapid decisions and keep bureaucracy to a minimum.

Small teams (3 to 5 max) are more nimble and learn (together) faster.