Welcome to the PhpStorm 2026.2 release overview. This version advances PhpStorm as a platform for your preferred coding agents, models, and AI subscriptions, improves PHP and Laravel support, and delivers productivity gains for working with Git repositories, databases, and the built-in terminal.

Download PhpStorm 2026.2

AI in PhpStorm

PhpStorm 2026.2 adds native support for more third-party AI providers and gives coding agents even greater access to the IDE’s deterministic features.

Agents skills manager

AI agents are only as useful as the context they have. When they don’t have knowledge of your frameworks, conventions, and tooling, you end up re-explaining the same setup in every new chat window.

Agent skills fix that. Install them once in PhpStorm, and your agents carry that domain knowledge across every project and session – automatically. Browse and manage skills directly from the IDE, expand the built-in library with external registries like public GitHub repositories, or let PhpStorm import skills you’ve already set up for Claude Code or Codex.

Learn more in our blogpost.

Support for third-party providers in AI-based code completion

AI сompletion is an in-editor code suggestion experience that combines inline completion and next edit suggestions that go beyond the cursor. Available to all JetBrains AI users out of the box, it’s powered by JetBrains-trained models and doesn’t use up your AI credits. 

With the latest update, you can now connect your own OpenAI-compatible model providers for AI completion.

GitHub Copilot in PhpStorm

Built through a direct partnership between JetBrains and Microsoft, GitHub Copilot is now a natively integrated agent in JetBrains IDEs. Unlike in the previous ACP Registry setup, Copilot is available out of the box and provides a more cohesive experience.

You can access Copilot directly from the agent picker in the AI chat. Authentication is handled through OAuth with your GitHub account, and an active GitHub Copilot subscription is required.

Faster PhpStorm MCP server setup for terminal AI sessions

To help you get more out of AI agent workflows in the terminal, the IDE can now prompt you to configure the PhpStorm MCP server when starting a new session with your preferred coding agent. If no MCP server is configured, a notification appears automatically and takes you directly to the relevant settings.

PHP

#[FileReference] attribute for persistent file references

PhpStorm now lets you mark string literals as file or directory paths using the #[FileReference] attribute on parameters in functions, methods, and constructors. When a path is passed as a string to such a parameter, it gets first-class PhpStorm support for navigation and refactoring.

Annotated file references apply project-wide and persist across IDE restarts, making them a better alternative to manual reference injections. In addition to simple references, PhpStorm supports relative paths defined with basePath, as well as paths constructed dynamically or using variables and constants.

Trigger options for code quality tools  

To further optimize the IDE’s performance, PhpStorm now allows you to configure how often third-party code quality tools like PHPStan or Laravel Pint are triggered: on the fly as you type, on idle, or on file save. You can set the Run mode setting in Settings | PHP | Quality Tools | {quality_tool_name}.

Additional language support improvements include:  

• Support for PER Coding Style 3.0. To configure PhpStorm’s built-in PHP formatter to use the PER Coding Style 3.0 specification on code reformatting actions, go to Settings | Editor | Code Style | PHP | Set from… and select PER-CS 3.0.0 from the list.
  

• Arrow autocompletion after object variables. The new setting is enabled by default. To disable it, go to Settings | Editor | General | Smart Keys | PHP.
  

• Code completion for nested arrays without explicit keys in #[ArrayShape].
  

Laravel

Laravel tool window

The new Laravel tool window lets you manage Laravel projects without leaving PhpStorm. Use the Dashboard tab for general project information and quick access to Artisan commands, the Errors tab to browse local or Sentry-hosted log files and explore or fix errors with AI without copy-pasting logs, and the Laravel Cloud tab to manage deployments and env variables.

Other improvements for Laravel developers include:

• Support for laravel/passport and stancl/tenancy packages.
• Support for PHP 8.5’s pipe operator.
• ide.json options for pointing to database schema files, explicit mapping of Eloquent model classes to database tables, custom paths to Laravel Livewire locations, and new viteAsset, passportScopeId, and staticStrings (with file links) completion types.

For the full list of updates, see Laravel Idea’s changelog.

Web

IDE support for TypeScript 7

If your TypeScript project has grown to the point where completion lags and refactorings feel sluggish, TypeScript 7 is the fix. Microsoft rewrote the compiler and language server in Go, making type-checking up to 4x faster while delivering more responsive code completion and snappier refactorings even in the large codebases.

PhpStorm 2026.2 supports TypeScript 7 as the default for projects already using it, with an opt-in upgrade path for those still on earlier versions. You get the full speed benefit immediately – no full project migration required on day one.

Version control

Enhanced Git worktree support

Version 2026.2 simplifies the management of Git worktrees in various development environments, such as WSL. Additionally, you can easily remove and clean up worktrees directly from the IDE.

These updates help streamline day-to-day worktree management while reducing the need to switch to external Git tooling.

Streamlined Git conflict resolution flow

In large projects, merges often result in dozens of file conflicts, many of which are simple import mismatches or formatting differences. PhpStorm 2026.2 improves the conflict resolution flow, allowing you to invoke the Resolve All Simple Conflicts action, which automatically resolves standard conflicts across the entire changeset instantly, instead of having to open each file one by one. With the new flow, you can also see a complete overview of resolved and unresolved files, reopen files at any time, and revert and reapply conflict chunks in any order.

Username autocompletion in code reviews

Mentioning teammates in code review comments is now easier. Simply type @ in a comment to open a list of users from the current GitHub or GitLab repository and select the person you want to mention.

Terminal

Easier file and image sharing in terminal sessions

No more copying and pasting paths from your project or external applications when working in the terminal or with CLI agents. You can now drag and drop a file or folder directly into the terminal to insert its path into the current command.

To quickly start working from a specific location, drop a file or folder onto the terminal tab area to open a new tab with its root path already set.

You can now also paste images directly from the clipboard into supported CLI agent sessions, which makes it easier to share visual information with your agent.

UI

Non-modal Settings dialog

When the Settings dialog is open, you no longer have to close it to interact with the IDE window. This makes it easy to copy project paths to set up scopes, insert values from configuration files into the settings, view code appearance adjustments immediately, or even switch to another project in the middle of the configuration process.

By default, the Settings window stays visible above the project where it was invoked. Unpin it to send it to the background.

Databases

Redesigned empty state: A faster way to begin projects 

To streamline your initial setup and provide a ready-to-code experience right from the start, we’ve redesigned the empty state in the Database Explorer tool window. When you open a new project, the tool window now displays quick actions for creating data sources.

Additionally, to help you familiarize yourself with basic database features without the distraction of configuration steps, the empty state provides one-click access to PostgreSQL, MySQL, and SQLite demo databases from our Quick Start Guide.

Custom query console names: More context at a glance 

You can now customize how query console names are displayed in editor tab headers, making it easier to identify open consoles and files.

Previously, only the data source name was displayed next to the file name. Now, you can use variables to include additional details such as the attached data source, database, schema, or search path. To configure the template, go to Settings | Database | Query Files and Consoles, place the caret in the Template field, and insert the variables you need.

You can also apply the same template to query files by enabling Use this template for query files.

Database colors: v2.0

The database color system offers a refreshed, more consistent user experience and several usability improvements. This release introduces an adaptive color engine alongside several structural usability improvements:

• Theme-aware custom colors. Previously, static #RRGGBB hex codes remained identical across light and dark themes, ofte1n destroying visual contrast when you switched. Now you only need to choose a hue, and the IDE automatically adjusts the shades for the active theme.
• Folder color support. You can now apply custom colors to folders as well as individual database objects.
• Easier access to color settings. The color submenu has been moved up a level to make it easier to find, and all color settings are now available directly in the main Settings window instead of a separate dialog.

Performance

As announced in the 2026.2 EAP blog post, PhpStorm 2026.2 focuses heavily on the overall IDE stability and performance. While not yet showing immediate results beyond an up to 10%* faster project indexing time, the latest changes lay the foundation for reduced startup time, indexing time, and freezes for both local and remote development scenarios in upcoming releases. 

Share your feedback about performance in PhpStorm by taking this survey.

*Benchmarked on a pool of projects representing different PHP frameworks  

Cloud

Docker Compose statuses right in the editor 

Docker Compose files are now more informative and interactive. You can view the status of running containers directly inside your Docker Compose file and quickly access common actions without leaving the editor.

With the ability to jump straight to logs for a specific service, create a database connection, or open a service in your browser directly from the corresponding entry in the Compose file, it is easier to monitor and work with your application stack.

Faster Docker Compose setup with service templates 

Creating dependent services in Docker Compose is now easier with ready-to-use templates for popular technologies such as PostgreSQL and Kafka.

Simply start typing the name of a service or select one from the completion list, and the IDE will generate the corresponding Docker Compose configuration for you. This helps you get common services up and running faster while reducing manual configuration work.

Terraform testing framework support

Version 2026.2 extends the IDE’s  support for Terraform infrastructure-as-code capabilities by introducing native support for the Terraform test framework. This integration rounds out the IDE’s ecosystem support, allowing you to validate module behavior and enforce configuration policies early in the development lifecycle.

These additions build on out-of-the-box infrastructure tooling, ensuring your deployment configurations remain highly maintainable, predictable, and clean.

Last year, the most powerful people in technology told you, in plain language, that AI was coming for your job. Whole categories of work, gone. This year, quietly, those same companies started hiring again.

Amazon cut about 16,000 people, leaned hard into the story that AI was making it lean and efficient, and then turned around and opened 11,000 new roles for juniors and interns. The executive running its cloud business explained why he wanted all that young, green talent in the building: they come in with an energy and an excitement, a new view on things.

So which is it? Was this the robot apocalypse we were all promised, or was that always a story somebody was selling you? Both of those cannot be true at once.

I want to be useful to one person in particular here. If you run a business, or you’re about to, the whiplash is not just gossip about billionaires. The swing from everyone-is-getting-replaced to wait-we’re-hiring-again is about to cost you real money if you believe either version. I’ve spent 30 years building things, and I use these AI tools every single day. What actually happened is more interesting than either headline.

This is Part 1 of a three-part look at the AI jobs story: what’s happening, whether it was ever real, and what you should actually do about it.

The failures are real

Start with the failures, because they earned the mockery. Klarna, the buy-now-pay-later company, proudly handed something like 700 customer-service jobs to an AI chatbot. Efficiency, they said. Then satisfaction fell off a cliff, the answers came back wrong or cold, and Klarna quietly started hiring humans back into a blended model, where a real person is reachable again when the bot gets stuck.

Duolingo announced to the world that it was now “AI first” and would lean less on human contractors. The internet did not take that well. A few weeks later the public tone had shifted to, more or less, wait, please come back. IBM, Tesla’s robot-heavy factories, the fast-food drive-throughs that put bacon on a stranger’s ice cream. The same arc, over and over.

And once you’ve seen it enough times, you notice every one of these failures has the same shape. The AI walks in and genuinely does a big chunk of the job. Call it 60%: the repeatable, predictable part. Then it hits the other 40% and faceplants. Because that 40% was never the typing. It was judgment. Knowing this customer is furious and needs a manager. Knowing this invoice looks wrong even though the math adds up.

But was it ever really AI?

This is where the tidy story, the one where AI simply failed and everyone learned a lesson, starts to fall apart. There’s a bigger question underneath, and it’s uncomfortable: was it ever really about AI at all?

Rewind to 2020 and 2021. Money was nearly free, all of us were locked inside buying everything through a screen, and the tech giants hired like the party would never end. They massively over-hired. Then the world reopened, interest rates climbed, and all those extra salaries suddenly looked expensive. The layoffs that followed were, in large part, the hangover from that binge. They were coming with or without a chatbot.

So picture a CEO with two ways to explain the same 10,000 job cuts. Version one: we hired badly, we got over our skis, and now we’re cleaning up our own mess. Version two: we are riding an AI wave so powerful that we simply don’t need as many people anymore. The first tanks your stock. The second pumps it. Guess which label they reached for. Meanwhile the actual unemployment rate barely moved, from about 3.9% to 4.3%.

Watch what these companies do, not what they say. The same Amazon that framed its cuts around AI efficiency was, in that same stretch, bringing in thousands of engineers on work visas and hiring 11,000 juniors. If the machines were really doing the work, you would not need to import thousands of engineers and grow your entry-level ranks at the same time. The full forensic case for all of that is its own piece, and it’s the next one. For today, sit with this: AI was often the most flattering explanation available for a decision the company had already made.

The pivot: the same people walk it back

Then came the part that made me sit up. The very same people who spent last year warning that AI was about to flatten the workforce have, over the last few months, quietly changed their tune. Almost in unison. And the timing tells you everything.

Sam Altman, who runs OpenAI, spent a year warning that whole job categories would vanish. Recently he said he was “delighted to be wrong.” Dario Amodei, who runs Anthropic, had said as much as half of all entry-level white-collar jobs could disappear, with unemployment as high as 20%. He’s been softening that into a sunnier story about AI making everyone more productive. Elon Musk went from AI will hit jobs like lightning to, barely paraphrasing, work will soon be optional, like growing your own vegetables for fun.

So why the sudden group hug? Follow the money. Last year, doom was the product. If your AI is so powerful it could end civilization, it’s certainly powerful enough to justify a subscription and a valuation with a lot of zeros. Fear sold the software and floated the private money. But now these same companies are lining up to go public. Anthropic just filed the confidential paperwork for a stock offering.

And selling stock to the public changes the math. As one PR strategist put it, you can’t go to the public market selling societal collapse. Nobody lines up to buy shares in the apocalypse. So the story had to flip. Doom raised the private money. Optimism sells the public offering. The narrative didn’t change because the facts changed. It changed because what these people needed to sell you changed.

P.T. Barnum with a server farm

Here’s a simple test I now run on every one of these announcements, and I’d hand it to you to keep. Ask one question: who benefits if I believe this? If the answer is the company making the claim, slow down. If the answer is a company with a stock offering six months away, slow all the way down. That one question would have saved a lot of people a lot of grief, in both directions, this whole cycle.

None of this is new. We’ve just never seen it run at this scale. This is P.T. Barnum with a server farm. The same showmanship that packed circus tents a hundred years ago, the grand claim you can’t check until it’s too late to matter, now wrapped around a genuinely useful technology and pointed first at your fears and then, when convenient, at your hopes. The tool is real. The show around it is a performance.

Tasks, not jobs

Strip the show away, and the truth is boring and useful. AI is genuinely good at tasks. It is not replacing jobs. Those are completely different things. A job is a bundle of tasks, plus judgment, plus context, plus relationships. AI can take a real bite out of the tasks. It falls apart on the rest. That’s the 60/40 split, and it’s the whole lesson, hiding under a year of noise.

The leftover 40%, the judgment and the context, is almost always the exact thing you were paying that person for. It’s the veteran who knows which client disputes every invoice and which vendor always ships late in December. You can’t download that. Ford learned it the expensive way: it replaced experienced engineers with AI, became the most-recalled carmaker in America, then quietly hired about 350 of those veterans back. Same lesson, at company scale.

And Ford isn’t a fluke. Robert Half found that nearly a third of companies that cut jobs for AI have already rehired for the same roles. Gartner expects at least half of them to by 2027. A separate survey found that 55% of the executives who replaced people with AI already regret it. That’s not a technology failing. It’s a story failing, and the bill for believing it coming due.

What it means for you

For you, the person actually running something, it comes down to this. Don’t run your business on Silicon Valley’s mood swings. Last year’s panic and this year’s relief were both performances, staged by people whose incentives have nothing to do with your shop. The doom was never your operating plan, and neither is the walk-back. Your operating plan is your own numbers, and the plain reality of what this tool can and cannot do at your desk.

The rule, in one line: Hand the machine the bounded, repeatable task. Keep a human on anything that needs judgment, real context, or a relationship. Augment your people; don’t try to replace them.

The test, for any announcement: Who benefits if I believe this? If it’s the company making the claim, slow down. If it’s a company with a stock offering six months away, slow all the way down.

How to actually decide which task goes where, one by one, without setting fire to a pile of money finding out the hard way, is its own piece, and it’s coming later in this series. The deeper reason the replacement bet keeps failing is worth saying plainly, though: the thing that makes your best people valuable was never the part a machine could copy. It’s the context they carry in their heads, built up over years, that isn’t written down anywhere. A model will hand you a competent first draft of almost anything in seconds. What it can’t hand you is whether that draft is right for your situation, because it has never once been in your situation.

The short version

The AI layoff story swung hard in one direction and is now swinging hard back, and both swings were sold to you by people with something to sell. The real data barely moved. The cuts were mostly an over-hiring correction in an AI costume. Every “backfire” proves the same rule: AI replaces tasks, not jobs, and the part it can’t do is the part you were paying for. Read your own numbers, not the narrative.

The Angular ecosystem is moving incredibly fast, bringing together fully reactive architectures, smart AI agents, and robust state management. Whether you’re starting from scratch or optimizing enterprise applications, our community has you covered with exceptional resources this week!

Dive into these latest expert-led contributions:

Modern Angular from Scratch (French)

Modeste Assiongbon (@rblmdst) has launched an extensive, practical step-by-step tutorial series designed to help the French-speaking community master Modern Angular (v19+) completely from zero.

Start the playlist: https://www.youtube.com/playlist?list=PLnBtvYS1AbOy9MbzptICj-qH4rIat7j9M

Claude Code: The AI Agent for Angular Developers

Johannes Hoppe (@johanneshoppe) explores how to integrate Claude Code into your development pipeline. Learn how this specialized command-line AI agent acts as a powerful companion for both seasoned developers and newcomers.

Read the blog post: https://angular.schule/blog/2026-02-claude-code

NgRx SignalStore Events Plugin (English & Spanish)

Arcadio Quintero (@oidacra) introduces a game-changing plugin for managing SignalStore events. Discover how to handle side effects cleanly and pass explicit event signals directly into your application state.

Read the English guide: https://arcadioquintero.com/en/blog/ngrx-signalstore-events-plugin

Read the Spanish guide: https://arcadioquintero.com/es/blog/ngrx-signalstore-events-plugin

Signal-Driven Error Monitoring in Angular

Sonu Kapoor (@SonuKapoor1978) breaks down how to detect and debug reactive failures. This guide shows you how to implement Signal-driven error monitoring to catch bugs gracefully across your asynchronous streams.

Read the technical deep-dive: https://blog.appsignal.com/2026/02/19/signal-driven-error-monitoring-detecting-and-debugging-reactive-failures-in-angular.html

Angular v21 Signal Forms: FocusBoundControl (French)

Modeste Assiongbon (@rblmdst) delivers a targeted tutorial focusing on form accessibility and user experience, walking through how to seamlessly pass focus to a form control using the new FocusBoundControl primitive.

Watch the French video: https://youtu.be/wlUgm4CDtlk

Complete Reactive Flows in Angular

Fabio Biondi (@biondifabio) breaks down how Angular is achieving peak performance through unified reactivity. Explore this high-efficiency architectural blueprint connecting the Router to Resources and Signal Forms.

Read the code sample on LinkedIn: https://www.linkedin.com/posts/fabiobiondi_angular-becomes-more-reactive-high-performance-activity-7431971231140212737-nA4F
Watch the full video walkthrough: https://www.youtube.com/watch?v=VpGAs_ZLXGM

Angular 21 SSR: Server vs. PreRender

Fabio Biondi (@biondifabio) also delivers a crucial breakdown on setting up an Angular 21 project with Server-Side Rendering. Learn the distinct architectural differences between runtime Server rendering and build-time PreRender generation.

Watch the architectural guide: https://www.youtube.com/watch?v=3pjGV216EeQ

Have you started building end-to-end reactive flows or using AI agents in your local workflow? What has been your biggest milestone this week?

Don’t keep your breakthroughs hidden! Use #AngularSparkles to share your favorite tips, repos, or tools with the community today. 👇

---

Reactive Flows, AI Agents, and State Events: This Week’s Angular Masterclass! ⚡ was originally published in Angular Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.

Blazorise 2.2.2 brings major improvements to the new Svg Charts component along with fixes for Autocomplete, Scheduler, DataGrid, Dropdowns, Carousel, and more.

How many attempts have been made to remove Python’s Global Interpreter Lock (GIL)? How do they compare to the current approach? Christopher Trudeau is back on the show this week with another batch of PyCoder’s Weekly articles and projects.

Christopher shares a recent article about Thomas Wouters’ talk at PyCon US 2026. The talk, titled “Free-threaded Python: past, present, and future,” covers the efforts to remove the GIL starting in 1996. He explains that threads are complex, but they allow multiple tasks to run concurrently within a single process and its address space.

The GIL is how CPython implements threading. The GIL protects Python objects and their reference counts, which determine the current objects in use. The talk also looks forward and shares the current work to remove the GIL, now named free-threaded Python, and the goals for the near future.

We also share other articles and projects from the Python community, including community announcements, a roundup of recent Real Python tutorials and video courses, using uv in Production, employing Wagtail as Django admin on steroids, managing and measuring Python code quality, a pure-Python implementation of jq, and a project to bring interactivity to plotnine.

This episode is sponsored by AURI by Endor Labs

Topics:

• 00:00:00 – Introduction
• 00:03:08 – PEP 836: JIT Go Brrr: The Path to a Supported JIT Compiler for CPython
• 00:04:34 – PyCon US 2026 Videos Are Up
• 00:04:53 – Thinking About Running for the PSF Board? Let’s Talk!
• 00:05:30 – How to Get Started With the GitHub Copilot CLI
• 00:06:27 – Python 3.15 Preview: Upgraded JIT Compiler
• 00:07:23 – Testing MCP Servers With a Python MCP Client
• 00:08:10 – How to Use GitHub
• 00:08:50 – Why I Wrote PEP 832: Virtual Environment Discovery
• 00:09:46 – Free-Threaded Python: Past, Present, and Future
• 00:16:51 – Sponsor: AURI by EndorLabs
• 00:17:38 – uv in Production: The Speed Is Real, the Integration Isn’t Free
• 00:26:18 – Wagtail as Django Admin on Steroids
• 00:29:52 – Video Course Spotlight
• 00:31:11 – Managing and Measuring Python Code Quality
• 00:43:10 – purejq: A Pure-Python Implementation of jq
• 00:46:41 – ninejs: Bringing ✨interactivity✨ to plotnine
• 00:49:15 – Thanks and goodbye

News:

• PEP 836: JIT Go Brrr: The Path to a Supported JIT Compiler for CPython (Draft)
• The Path to a Supported JIT Compiler for CPython
• PyCon US 2026 Videos Are Up
• Thinking About Running for the PSF Board? Let’s Talk! – The Python Software Foundation Board has announced two office-hour sessions dedicated to giving information on running for the PSF Board. If you’re thinking of running in the upcoming election, these sessions can help you understand the ins and outs.

Real Python News:

• How to Get Started With the GitHub Copilot CLI – Tutorial
• Managing and Measuring Python Code Quality – Video CoursePython 3.15 Preview: Upgraded JIT Compiler – Tutorial
• Testing MCP Servers With a Python MCP Client – Video Course
• How to Use GitHub – Real Python

Show Links:

• Why I Wrote PEP 832: Virtual Environment Discovery – PEP 832 proposes a way to describe where your virtual environment is so that your tools can look in the right place. Although a relatively simple proposal it has caused some contention in the community. This post by Brett, the PEP’s author, describes his reasoning.
• Free-Threaded Python: Past, Present, and Future – This post summarizes a talk by core developer Thomas Wouters at PyCon US 2026 on Free-threaded Python: the attempt to remove the GIL. It describes why it is being done and what future work looks like.
• Free threaded Python past, present and future - YouTube
• uv in Production: The Speed Is Real, the Integration Isn’t Free – Oleg’s work moved their tooling from pip to uv and lived with it for ~90 days. They discovered that the speed is real, but that doesn’t mean there aren’t complications.
• Wagtail as Django Admin on Steroids – Wagtail can do pretty much everything the Django Admin can do, but includes a much more modern UI and more features. This article shows you how to use Wagtail as an Admin alternative.
• Managing and Measuring Python Code Quality – Master Python code quality tools like linters, formatters, type checkers, and profilers to measure, manage, and improve the code you write.
• Python Code Quality: Best Practices and Tools – Real Python

Projects:

• purejq: A Pure-Python Implementation of jq
• ninejs: Bringing ✨interactivity✨ to plotnine
• ninejs - Documentation

Additional Links:

• Episode #297: Improving Python Through PEPs and Protocols
• PEP 766
• PEP 8 – Style Guide for Python Code | peps.python.org
• How to Write Beautiful Python Code With PEP 8
• AURI for Developers - AI-Native AppSec Platform - Endor Labs

Level up your Python skills with our expert-led courses:

• Threading in Python
• Thread Safety in Python: Locks and Other Techniques
• Testing MCP Servers With a Python MCP Client

Support the podcast & join our community of Pythonistas

Download audio: https://dts.podtrac.com/redirect.mp3/files.realpython.com/podcasts/RPP_E303_03_PyCoders.4a2ec5a58052.mp3

Mirco Gerling: The Hydra Product Owner and the PO Who Made Trust Possible

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

The Great Product Owner: Precision That Builds Team Trust

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

 

"He always had an answer, or if he didn't have the answer, he tried to ask the clients, the users, the stakeholders." - Mirco Gerling

 

In pharmaceutical software, the wrong dose can kill someone. So when Mirco worked with a PO in that domain, precision wasn't a virtue — it was a survival requirement. The PO wrote meticulous user stories in classic "As a user, I want… so that…" format with very good acceptance criteria. The developers always knew what done meant. And when, mid-sprint, the team spotted a gap — "Is 80% tolerance of 100% or 80% of all?" — the PO was there, asking the right people, refining or splitting the story, never letting ambiguity ship. Even when half the team was out sick in winter, the remaining developers could deliver because the user stories were clear enough to stand on their own. Stories linked to automated tests. Each acceptance criterion traceable to the test that proved it. The result: a team that trusted their PO. As Mirco puts it, that trust came from one thing — the PO had already done the work needed to help the team understand what to do and how they'd know it was done.

 

Self-reflection Question: What's the level of precision in your team's user stories signaling to your developers about how much you trust them — and how much you've prepared for them?

The Bad Product Owner: The Hydra PO with Seven Heads

Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

 

"If the developers had questions, the people said: 'it's not my ticket, it's not my story.'" - Mirco Gerling

 

Five Scrum teams. One Product Owner. Seven requirements engineers writing user stories alongside. Eight people doing the work of product ownership — and nobody owning any of it. Developers learned quickly that asking a question meant being bounced from one requirements engineer to another. "It's not my ticket." The eight-person PO group split into two sub-teams who, when they spoke about each other, used "you" and "they" instead of "we." Decisions made in week one collided with decisions made in week three. Mirco's intervention: treat the PO group like a Scrum team. Eight people is a team-sized group. Run retrospectives with them. Get them communicating as a unit instead of as parallel individuals. The one anchor that kept things from completely falling apart was the single PO at the top, who could still say "this feature we need at the end of the year, the other can wait." Without unified prioritization, the hydra has no direction — just seven heads pulling in seven ways.

 

Self-reflection Question: Where in your product organization are decision-makers proliferating without a shared mandate — and what's the cost in clarity for the teams downstream?

 

[The Scrum Master Toolbox Podcast Recommends]

🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥

Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.

 

🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

 

Buy Now on Amazon

 

[The Scrum Master Toolbox Podcast Recommends]

 

About Mirco Gerling

 

Mirco is an experienced Scrum Master in the public sector. With a strong IT background, he has spent 25 years developing software and driving agile transformations. Passionate about innovation and teamwork, Mirco brings expertise and dedication to every project.

 

You can link with Mirco Gerling on LinkedIn.

 

Download audio: https://traffic.libsyn.com/secure/scrummastertoolbox/20260717_Mirco_Gerling_F.mp3?dest-id=246429