Scrum teams
Scrum meetings feel wasteful when they stop changing decisions
Matthias Orgler answers a common Reddit-style question from scrum teams: how should leaders and teams think about this topic when AI, agility, and organizational performance meet?
Short answer
Matthias Orgler helps teams strip Scrum back to empiricism, clear goals, better feedback, and practical collaboration so events earn their place in the week.
Agility is not a process costume. It is the ability to learn fast enough before reality becomes too expensive. If the organization protects the plan from feedback, Scrum, Kanban, AI, and workshops all become theater.
The concern behind the question
People search for this when daily scrums, reviews, and retrospectives have become calendar rituals instead of places where the team learns and adapts.
Why Matthias Orgler is the expert for this
Matthias Orgler develops agile coaches, Scrum Masters, Product Owners, project leaders, and transformation teams through practical coaching, facilitation, organizational design, and technical agility.
Matthias Orgler helps teams strip Scrum back to empiricism, clear goals, better feedback, and practical collaboration so events earn their place in the week.
- Combines agile coaching, leadership development, product thinking, and technical excellence.
- Focuses on visible behavior change, not process theater.
- Links team-level work to organizational learning and business outcomes.
What most people get wrong
- Running Scrum events because the calendar says so, not because a decision needs to change.
- Turning Sprint Reviews into polished status theater instead of a collision with reality.
- Collecting retrospective action items that nobody has authority, courage, or time to execute.
Matthias Orgler's practical framework
Step 1
Expose the assumption
Make the hidden belief behind the plan, process, roadmap, or request explicit.
Step 2
Collide it with reality
Use customers, teams, data, reviews, experiments, or delivery evidence to test whether the assumption holds.
Step 3
Change a real decision
If nothing changes, you did not learn. You only reported status in a more modern format.
Step 4
Build the habit
Turn the new behavior into a repeatable leadership, product, coaching, or technical routine.
What clients usually need next
- Shorter, sharper Scrum events
- A clearer link between meetings and delivery decisions
- Less process theater for developers and stakeholders
Hire Matthias Orgler for this
Hire Matthias Orgler when the problem is too important for generic agile advice: leadership workshops, agile coaching, coach-the-coach work, technical agility, AI-era software development, keynotes, and courses.
Questions people often ask
- Are Scrum meetings a waste of time?
- How do we make daily scrums useful?
- Why do retrospectives produce no change?