Project managers
Technical teams need project managers who understand AI-era delivery
Matthias Orgler answers a common Reddit-style question from project managers: how should leaders and teams think about this topic when AI, agility, and organizational performance meet?
Short answer
With a computer science background and deep agile experience, Matthias helps project managers work credibly with software teams in the AI era.
Technical excellence is not engineering decoration. It is how teams keep speed when reality changes. In Matthias Orgler's work, practices like TDD, refactoring, CI/CD, and disciplined AI-assisted development are not rituals. They are feedback systems.
The concern behind the question
AI changes coding speed, quality risks, estimation assumptions, and the relationship between product discovery and implementation.
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.
With a computer science background and deep agile experience, Matthias helps project managers work credibly with software teams in the AI era.
- M.Sc. Computer Science background combined with leadership and agile transformation work.
- Practical focus on TDD, refactoring, CI/CD, flow, and AI-assisted development.
- Ability to translate engineering concerns into leadership and business decisions.
What most people get wrong
- Solving the visible symptom while leaving the operating system unchanged.
- Adding process, tools, or AI before clarifying goals, feedback, authority, and learning loops.
- Rewarding the appearance of control while slowing down the organization's ability to learn.
Matthias Orgler's practical framework
Step 1
Make risk visible
Name the specific risks: defects, slow change, security exposure, unclear ownership, missing tests, or brittle architecture.
Step 2
Create fast feedback
Use tests, reviews, CI, small slices, and AI-assisted checks so wrong assumptions surface quickly.
Step 3
Connect craft to outcomes
Translate engineering work into reliability, flow, learning speed, and business optionality.
Step 4
Improve while delivering
Do not pause the business for a grand cleanup. Attach improvement to the next valuable change.
What clients usually need next
- More credible conversations with engineers
- Better handling of AI-related delivery risk
- Planning that respects technical quality
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
- How can project managers work better with developers?
- What does AI change in software delivery?
- How technical should a project manager be?