There is a difference between leaving a conference inspired and leaving it changed. I have been to my fair share, and I love the networking. But inspired fades somewhere over the flight home, depending on how long the flight is. Changed shows up in your next planning session.
Right now the biggest Agile gathering of the year is underway at National Harbor. PMI Agile 2026 runs July 26 through 28 at the Gaylord National, just outside Washington, DC. I wish I could be walking that floor this week. I am not, so I am there in spirit. Most people who are there will go home inspired. I want to talk about how you go home changed instead.
I would never have guessed that the largest Agile event in the world would end up being a PMI event. But the world changes. Regardless of who holds the conference, today is about how you show up to it.
Three Scrum Masters, One Full Notebook, Zero Changes
A few years back a client sent three of their Scrum Masters to a big industry conference. Full week, real money, great intentions. I happened to be going anyway, so I met up with them there.
They came back glowing. Notebooks full. New vocabulary. One of them had a photo with the keynote speaker and was completely starstruck.
Ninety days later I asked what had actually changed in their delivery. Cycle time, the same. Planning, the same. Working agreements, not one word different from what they had before they left.
The conference did not fail them. Their mode of attention did. They went as fans.
Fans Collect Moments. Analysts Collect Evidence.
Conference inspiration is designed to feel like progress. The energy in a keynote room is real, and it is also completely free. It costs the speaker nothing to give and it costs you nothing to receive. It is a bit like catalyzing an Agile transformation for one week and then watching it die on the following Monday.
What costs something is a decision. A decision has a name attached to it, a date attached to it, and a way to be wrong.
This industry has quietly optimized for the inspired version of you. Inspired attendees come back next year. Changed attendees might not need to. That is a dangerous proposition when you are the one holding the conference.
Why This Particular Conference Is Framed Differently
I have watched Agile conferences for twenty years. I am that old. This one is framed differently than any I can remember, and it is worth looking at before you decide how to walk the floor.
The program says the quiet part out loud
The theme this year is MORE, Together: Shaping the Future with Agility. And the organizers put an unusual frame right in the program. They say the event is where practitioners and leaders examine what is working, what is breaking down, and how agility has to keep evolving.
That second half matters. Conferences do not usually advertise the breakdown. They advertise the breakthroughs, because breakthroughs sell tickets.
PMI's own promotional copy goes further. Their words, not mine: the Agile community does not need another conference, it needs a reckoning. Sit with that one for a second. The field's flagship event is marketing itself as a reckoning. When an institution like PMI says that about its own community, take it seriously. Read it as a diagnosis rather than a death notice.
The track list tells you where the arguments moved
Look at the six tracks and you can see where the real arguments live this year:
- Agility at Scale
- Agility in Regulated & Complex Environments
- Future of Work & Careers
- Emerging Technology, DevOps & Engineering
- People, Teams & Sustainable Agility
- Hands-On Agile
Now notice what is missing. There is no track called "which framework is best." The arguments have moved on from which framework wins to where agility breaks under real conditions. The data backs that shift up.
The Field's Own Scoreboard Quit Keeping Score
Digital.ai has run the State of Agile Report for eighteen editions. It is the longest-running study of Agile adoption we have, and for most of its history it worked like a scoreboard. Which frameworks. How much adoption. Which scaling approach is winning.
The 18th edition, released last October, is subtitled The Adaptation Era, and the center of gravity moved. It is about outcomes, value measurement, governance, and AI. The framework horse race is no longer the story the report is telling.
That is not a small editorial choice. That is the survey finally catching up to reality. The interesting question stopped being about frameworks years ago. The report is just now admitting it in the mainstream.
Now put the practitioner view next to that
The AI4Agile Practitioners Report 2026, published on Scrum.org earlier this year, surveyed 289 practitioners: Scrum Masters, coaches, product people, across more than twenty countries.
The headline number looks impressive. 83% of practitioners use AI tools. Then you look closer. 55% spend 10% or less of their working time with AI. Only 15% have had any formal training on using it in an Agile context.
The report's own read on that is blunt: most practitioners experiment with AI the way most organizations "do Agile." They go through the motions without changing how they think or work.
That sentence should sting a little. It is the same shallow adoption pattern this community spent two decades pointing out in everybody else.
Connect the three signals. The flagship event is calling for a reckoning. The longest-running survey stopped keeping framework score. The practitioner data shows broad, shallow adoption of the technology reshaping the work. That is the real context for National Harbor this week. The question is not whether the community survives. It is whether the people in it can tell signal from slogan while the ground moves underneath them.
Three Questions to Carry Into Every Session
So what does attending like an analyst actually look like? I am a data guy. I like metrics and I like taking things apart. I also get starstruck, so I am not condemning anybody here. But I carry three questions into every session, keynote, and vendor booth, and I would recommend the same this week. They work on the floor, and they work on every recap post that floods your feed the week after.
1. Who benefits if I believe this?
Everyone on an Agile conference stage is selling something. A tool, a certification, a book, a consulting practice, a reputation. That includes me. I sell training and coaching for a living, and if I can say follow the incentives, so can the person at the podium.
An incentive does not make a claim false. Plenty of true things get said by people who profit from them. The incentive tells you how hard to test the claim before you act on it, the same way you would with a health study. When a vendor keynote says their platform doubled a client's delivery speed, do not argue with it. Quietly ask who measured that, and who paid for the measurement.
2. What is the evidence, and would it survive contact with my organization?
This is where most conference ideas go to die. On reentry. It is nobody's fault. A case study from a 40-person startup with no compliance burden is a real result. It is just not your result if you run 4,000 people in a regulated environment.
For every claim, ask about the sample. How many teams. What kind of organization. Over what time frame. Measured how. A surprising amount falls apart the moment you dig into the measurement. If the speaker cannot answer those questions, you have not learned a fact. You have learned a story. Stories are fine. File them as stories.
Take the AI numbers I just gave you. I told you the sample: 289 practitioners, twenty-plus countries, self-reported. That is a useful signal about practitioner sentiment. It is not a census of the industry. Holding both of those at once is the thing analysts do well.
3. What decision of mine does this change?
This is the sharpest filter of the three. You are facing real decisions right now. Whether to keep the scaled planning event that eats two days a quarter and that everyone quietly complains about. Whether to pilot AI in backlog refinement, which you probably should. Whether to reshape a coaching role before someone else reshapes it for you.
If a session speaks to one of those decisions, take notes like your job depends on it. If it does not, enjoy it as a talk and move on. Entertainment is allowed. Just do not file entertainment as learning and expect it to catalyze anything with your team.
The Hallway Tells You What the Stage Will Not
A quick word on hallway conversations, because honestly that is where the best signals live. The stage tells you what the industry wants to project. The hallway tells you what everybody is quietly worried about. Pay attention to those.
What to Do This Week, Whether You Are There or Not
There is a version of this you can run either way.
If you are at National Harbor: tonight, before tomorrow's sessions, write down the decision you are actually facing back home. One sentence, at the top of your notes. Filter every session through that lens. By the time you leave, write two things under that sentence: the decision you are making, and the smallest test that would tell you whether it is right. That sounds a lot like product thinking, and it should.
Done well, it looks like this. One decision. One test. One calendar invite already sent to your team for the week you are back. A decision review, not a trip report.
On the smallest test, because people ask me what that actually means: it is the cheapest thing you can run that would change your mind. Not a pilot program. Not a working group. If the decision is whether to kill the two-day quarterly planning event, the smallest test is skipping it once and writing down beforehand what you expect to break. If the decision is whether to pilot AI in backlog refinement, the smallest test is one refinement session with one team where you compare the output against what the team would have produced on its own. One team, one iteration, a result you can read in two weeks. If it takes a quarter and a budget line, it is not a test yet.
If you are not attending: pick one of the debates. Scale, governance, delivery, or the future of the roles. Write your own position in five sentences before the recap content starts flooding your feed next week. Then, when the takes roll in, compare them against your starting position instead of absorbing them. You will notice immediately which recaps carry evidence and which ones just carry the vibe of the room.
Either way the standard is the same. Bring back one decision. Not one buzzword. One decision.
A Conference Cannot Change Your Organization
Conferences are worth attending. They build your repertoire and your network, and I will keep going to them. But the change never comes from the room. It comes from the one decision you were willing to name, date, and be wrong about.
If you want help turning that decision into something your teams can actually run, that is what our training and coaching work is built for. Have a look at our upcoming classes and find the one that matches the decision you just wrote down.
If you are at National Harbor this week, drop me a note or a comment. I would love to hear what you are seeing on the ground.