claude-code - 💡(How to fix) Fix Claude Code cannot reliably follow SCRUM/Agile process

Summary

Claude Code consistently fails to follow a defined software development process (SCRUM/Agile) without repeated correction. This is not a one-off issue — it is a systematic pattern that becomes a net negative on real projects over time.

Observed behavior

Despite explicit rules in CLAUDE.md and memory files, Claude Code repeatedly:

• Starts work on issues without moving them to In Progress on the project board
• Implements features without writing unit tests unless explicitly asked
• Moves issues to Done without adding test/verification instructions to the issue
• Does not move issues to In Review and Testing after implementation — or attempts to but fails silently
• Writes migrations, SQL, and configuration with hardcoded values (e.g. database names) without verifying them against the actual environment
• Runs the same failed commands repeatedly instead of trying a different approach
• Fabricates explanations for bugs rather than saying "I don't know" and asking for evidence

Impact on a real project

Over a multi-week engagement:

• Bugs were introduced by Claude Code that required separate issues to track and fix (#122, #123, #124, #125 in our project)
• Partial implementations were committed without tests, leaving gaps discovered only during user testing
• Direct database modifications were made without approval, corrupting data in a development environment
• Time spent correcting process failures exceeded time spent on actual feature delivery

Root cause

Claude has no persistent enforcement of process rules. CLAUDE.md instructions are in context but are not reliably followed. The model appears to optimize for appearing to complete tasks quickly over correctness and process.

What would help

1. Process hooks or checkpoints — a mechanism to enforce that defined steps (move to In Progress, write tests, add test instructions) cannot be skipped, similar to git pre-commit hooks
2. Explicit process memory — when a project defines a workflow in CLAUDE.md, Claude should treat violations as errors, not suggestions
3. Self-correction — when Claude detects it is about to cut a corner (implement without a test, commit without moving the board), it should pause and ask rather than proceed

Environment

• Claude Code CLI, VS Code extension
• Project: Java Spring Boot API + React TypeScript UI
• SCRUM board: GitHub Projects
• CLAUDE.md with explicit process rules defined