I shipped my first product in 2015 with a team of three people. We used Jira to track everything—features, bugs, debt, you name it. It was messy and brilliant. Fast forward to now, and I’ve watched how teams organize their work change more in the last year than it did in the previous decade. AI isn’t just tweaking how we use tools like Jira. It’s fundamentally breaking the old model of who does what and when.
The reason this matters is simple: when your bottlenecks disappear, your entire operation has to rethink itself. And that’s exactly what’s happening right now.
The Old Bottleneck Is Gone
For years, the constraint in any engineering org was obvious: writing code took time. Lots of it. You had your architects thinking big, your seniors reviewing everything, your juniors grinding through implementation. The work was always there—boilerplate, scaffolding, test suites, connecting systems together. That glue work? It consumed half your sprint, maybe more.
Your Jira board reflected this reality. Tasks were broken down into granular chunks because humans needed to do the work in manageable pieces. You’d have an epic, break it into stories, break those into smaller tasks. Each one was a unit of work that someone would manually execute.
AI agents changed that equation overnight. The repetitive, predictable work—the stuff that made you want to bang your head on your keyboard—got automated. Suddenly, scaffolding appears. Tests get written. Boilerplate vanishes. The stuff that used to be half your sprint is now handled in minutes.
That’s not a marginal improvement. That’s a restructuring event.
How Teams Actually Work Now
What I’m seeing in teams that have gone all-in on AI is a complete shift in thinking. Engineers aren’t reasoning in terms of individual files and functions anymore. They’re thinking in systems. Architecture. Constraints. Execution plans.
On a practical level, here’s what changes in Jira and how you organize work:
- Bigger units of work. You don’t need a task for “write database migration tests.” You need a story for “ship the new payment system.” The agent fills in the middle.
- Different skill mix required. Your senior engineers spend less time code-reviewing boilerplate and more time thinking about system design. You need people who understand constraints and trade-offs, not people who can type fast.
- Faster feedback loops. Cycle times went from weeks to days for us, sometimes to hours. Your backlog priority suddenly matters way more because you can actually execute.
- Less busy work. The stuff that kept junior engineers busy while they “learned the codebase”? A lot of that goes away. You need junior engineers who can think, not people who can follow a detailed instruction manual.
I’ve watched teams struggle with this transition because the old Jira structure doesn’t fit anymore. You have to actually think about what you’re shipping instead of hiding behind task granularity. It sounds great—and it is—but it also means you can’t paper over unclear product thinking with more tasks and more process.
The Real Change Is Organizational
Here’s the thing nobody talks about: the tool didn’t change. Jira is still Jira. What changed is what happens inside the tool.
The org chart is breaking because speed changes everything. When you can ship something in a day instead of a week, the entire question of “who is responsible for what” gets messy. Your product managers need to be able to think through implementation now. Your engineers need to understand the business problem, not just the technical spec. Your QA folks need to think about test strategy instead of running through checklists.
That’s genuinely harder than it sounds. Most teams aren’t used to working that way. We had to completely rethink our standup. We had to change who talks to whom. We had to accept that some of the hierarchy we’d built—based on the assumption that writing code was the bottleneck—just didn’t make sense anymore.
The teams winning right now are the ones that recognized this early. They stopped trying to fit the new reality into old boxes. They’re using Jira differently because they’re thinking about their work differently. They’re hiring differently. They’re organizing differently.
If you’re still breaking everything into tiny tasks and running sprints the same way you did in 2020, you’re leaving a massive amount of potential on the table. This isn’t about adopting the latest feature in Jira or switching to some new tool. It’s about actually understanding that the game has changed and building your team to play the new one.
Source: When product managers ship code: AI just broke the software org chart
Tom Harrington
Emma Clarke