Of the five Scrum values — Commitment, Focus, Openness, Respect, and Courage — most teams practice four reasonably well. Courage is the one they avoid. Yet Courage is what makes the other four values meaningful. Without it, Openness becomes performative, Commitment turns into silent pressure, and Respect becomes an excuse not to speak up. Courage shows up in small, practical moments: telling the Product Owner the backlog isn't ready, admitting uncertainty during estimation, or raising a real problem in the Daily Scrum. After 20 years working with Scrum teams, the clearest differentiator between teams that improve and teams that stagnate is willingness to say what's true — even when it's uncomfortable. Courage doesn't require a dramatic stand. It just requires speaking up one moment sooner than feels safe.

Over a 50-year career spanning lumber yards, retail software, Scrum and AI-assisted development, one principle has remained constant: the best professionals think clearly about the problem before reaching for a tool. Whether it was a pencil and clipboard in 1972 or AI in 2026, the tool itself was never the differentiator — the quality of thinking behind it was. The same holds true today: great developers define the problem before opening an IDE, write tests before writing code, and ask AI a good question before accepting its answer. Tools will keep changing. Clear thinking never goes out of style.

Completing every user story in a Sprint doesn't equal success if the Sprint Goal isn't met. Many teams fall into the trap of optimizing for task completion — closing tickets and hitting velocity targets — while losing sight of the actual business outcome they committed to. The Sprint Goal isn't a label for a group of stories; it's a real deliverable of value. When the goal is vague or ignored, teams execute work without asking whether it adds up to something meaningful. The fix is simple but disciplined: write the Sprint Goal in one clear sentence before the Sprint begins, then use it as the filter for every planning decision.

AI Agents are autonomous AI tools that can plan, act, and complete tasks independently — and when integrated into a Scrum team, they supercharge every ceremony without replacing human roles.

What Changed in Software Development This Week Because of AI — May 12, 2026

This issue covers five verified announcements from May 5–11, 2026, all tied to changes in how software gets built.

Anthropic gave AI agents the ability to learn from their mistakes. A new feature called "dreaming" lets Claude Managed Agents review their own past sessions between tasks, clean up memory, and improve over time without human intervention at every step. Legal AI company Harvey saw task completion rates jump six times after using it. Two related features — outcomes (a built-in grading loop) and multiagent orchestration (parallel specialist agents) — also moved to public beta the same week.

Microsoft published the largest study of human-AI work patterns to date. Surveying 20,000 workers across 10 countries and analyzing trillions of productivity signals, the 2026 Work Trend Index found that software teams have already moved through four stages of AI collaboration — Author, Editor, Director, and Orchestrator — and that every other business function is now following the same path. The biggest barrier to AI value is not the technology. It is how organizations structure work around it.

OpenAI told the world how it keeps its own coding agent safe. A May 8 post detailed the sandbox modes, auto-review policies, network restrictions, and audit logging Codex runs under inside OpenAI's own engineering teams. It is the first time a major AI lab has published its full internal governance playbook for a coding agent.

OpenAI launched a company dedicated to enterprise AI deployment. The new OpenAI Deployment Company and its Codex Labs hands-on service, backed by seven global systems integrators including Accenture, Capgemini, and Infosys, signals that the industry now treats enterprise AI adoption as a change management problem, not a technology problem. Four million developers are using Codex every week.

Anthropic brought full Claude Platform feature parity to AWS. As of May 11, AWS customers get every new Claude feature the same day it ships — including Managed Agents, code execution, the Advisor strategy, and the new Agent view in Claude Code.

For Scrum teams, the common thread across all five stories is the same: AI agents are moving from individual productivity tools to team-level infrastructure. The teams that benefit most will be the ones that treat agent governance, clear acceptance criteria, and workflow redesign as Agile work — not as IT afterthoughts.