sideways deployed PMM @Atlassian | former @newrelic @IOpipes @Merkle | committed partner, dad, surfer, skateboarder, DevEx, cloud infra enthusiast | he/him
Seattle - Coast Salish lands
Joined March 2014
- Tweets2K
- Following857
- Followers989
- Likes8.9K
John Kinmonth retweeted
Today we're releasing our AI SDLC transformation playbook, where we share best practices to deploy AI at enterprise scale
Engineering leaders frequently ask how Atlassian thinks about our AI-native SDLC. This playbook is our answer, informed by our own transformation and learnings from top engineering organizations we work with
Come find us at the AI SDLC booth at Team '26 EU this week for a physical copy (and merch) atlassian.com/blog/ai-at-wor…
John Kinmonth retweeted
I am so lucky to get to chat with Elena from Lovable and learn how the PM team there works. I love the speed at which she operates, while still doing the core PM job of building products people love.
Register and tune in on Sept 22nd.
AI is rapidly changing how software gets built. But the bottleneck isn't code—it's context.
On Sept 22, we’re trading notes with leaders from @Vercel, @Lovable, @1Password, and more on what’s actually working in the SDLC.
Link below to save your spot. ⬇️
John Kinmonth retweeted
Turn conversations into work with Atlassian Rovo + @Microsoft365. 🤝
Rovo now connects Microsoft 365 to the Teamwork Graph, unifying your work across Jira, Confluence, and GitHub.
🔹 Use Rovo as an agent in @Copilot and Teams to get the full picture for every decision.
🔹 Trigger @ Jira workflows in Teams to delegate work to AI agents using natural language.
The power of Atlassian, right where you already collaborate. atlassian.com/blog/rovo/rovo…
John Kinmonth retweeted
People are moving to spec-driven development. The new Jira planner makes this easy and enables you to seamlessly connect to all of your enterprise context via the Teamwork Graph.
John Kinmonth retweeted
AI coding agents rarely fail at writing code. They fail at understanding context.
Jira Planner is the bridge—a structured way to translate human collaboration into agent-readable specs before the IDE even opens.
Now in early access. See it in action. ⬇️
John Kinmonth retweeted
🤔 Without the right context, every day is day one for your coding agent.
✖️ They don’t know why certain tradeoffs were made
😱 They don’t know which services depend on what
🧐 They don’t know what’s going to break downstream
🚀 So today, we’re introducing Code Context into the Atlassian Teamwork Graph.
💥 Code Context taps into knowledge from the Teamwork Graph to connect to Jira work items, Confluence decisions, Rovo and more.
💡 It gives agents a more complete understanding of the work, so they can produce better outcomes, and can catch cross-repo dependencies before they become shipped errors.
🫶 Any agent (Cursor, OpenAI's Codex or Anthropic's Claude Code) can use it through the Teamwork Graph CLI, and accountability and governance stays with developers through its permission-aware design.
➕ One context layer to reason over. That’s the difference between an agent that ships and one that creates work.
John Kinmonth retweeted
Most coding agents are blind to the complexity of your system.
Code Context fixes this. By bringing codebase understanding into the Teamwork Graph, agents can now reason across every repository with the context needed to produce more precise output—all while respecting your existing access controls.
Watch @Claude Code with vs. without Code Context to see the difference. 👇
John Kinmonth retweeted
Codex agents run in clean, disposable sessions. By design.
But while code lands in your repo, the context needs a permanent home.
@OpenAI Symphony now integrates with Jira as your system of record. Every plan, review, and follow-up pinned to the work item, long after the session’s gone.
Manage the work, not the session.
John Kinmonth retweeted
Scaling agents isn't a prompt engineering problem. It’s an orchestration problem.
Jira automation is now an open control plane for your coding agents. Trigger @GitHub Copilot, @cursor_ai, or @claudeai Code the moment engineering conditions are met.
Stop prompting. Start orchestrating.
John Kinmonth retweeted
A video is worth a thousand prompts. 🎥
Loom video prompts turn your screen recordings into structured action plans for AI agents like Rovo, @ClaudeAI and @cursor_ai. ↓
John Kinmonth retweeted
Coordination is the new bottleneck in AI-native development.
See how we’re evolving Jira to be the system for the AI SDLC—and why teams like @Reddit are using it to ground their agentic workflows: go.atlss.in/ej073c
John Kinmonth retweeted
Writing software is about solving a customer problem. Code is one part, and it's the part AI has gotten great at.
But the rest - context, coordination, judgment - is still on humans.
Today we launched new capabilities in Jira let teams plan work with AI, turn intent into agent-ready specs, assign work to @AnthropicAI Claude Code, @cursor_ai, or @GitHub Copilot (with Codex coming soon), monitor every session, and measure AI cost against output.
The Teamwork Graph supplies the context. Jira turns it into workflow.
Already, @Atlassian engineers report:
→ 44% higher quality results
→ 48% lower token consumption
The SDLC is becoming legible to agents without becoming less accountable to humans. See it at jira.dev.
Life isn't all enterprise software. Got to speak to 2K sellers a few years back in Copenhagen about AI + DevEx for @Atlassian.
Spent an extra day exploring the architecture. 🛹🇩🇰
John Kinmonth retweeted
With 1M+ monthly users executing 5M+ tool calls per day, the Atlassian Rovo MCP (Jira, Confluence, etc) is one of the most widely used MCP servers around. Today we’re sharing the kinds of traffic we’re seeing which offers interesting insights into how teams are adopting AI...
John Kinmonth retweeted
🥇 Jira Slack Agent now has new features that uplift your workflow.
🫶 Jira slack agent has existed for more than a year now - and we have millions of monthly active users of that agent in slack.
💥 Based on working with our customers, we have learnt a bunch of new ways in which we can improve this and now we are officially launching it to you all.
🏹 With the new Atlassian Jira for Slack app, you can now turn any conversation into a tracked work item the moment it happens. Just mention @Jira to:
✅ Create & update: Turn threads into structured Jira tasks.
✅ Capture context: Automatically pull in decisions, links, and team knowledge from the thread or channel.
✅ Orchestrate work: Assign tasks to teammates or AI agents directly from chat.