At AMD, the Atlassian platform has become the mission-critical application for the engineering. Right from feature request and tapeout of large silicon programs to customer-blocking bugs in production, everything is managed in Jira. In addition, Confluence is used as an engineering knowledge repository and a collaboration platform. With thousands of engineers across multiple domains, AMD needed more than individual tools – they needed a connected way of working that could align teams, surface risk, and keep everyone moving in the same direction. 

In this session, AMD leaders will share how they set that up on Atlassian. They’ll walk through how programs are modeled, how planning and execution stay connected, and how work flows across hardware, firmware, and software teams without getting lost in handoffs. They’ll also show how Atlassian is integrated into AMD’s broader toolchain, and how that foundation is starting to support better developer experience and early AI-assisted workflows. AMD went thru the journey of transforming all the Atlassian footprint to 1AMD Jira and Confluence platform, improving the effeciency and productivity of engineering team.

This is not a “we solved everything” story. It’s a look at what’s working today at AMD, where we are still iterating, and a few practical patterns other large engineering organizations can borrow.

Key takeaways:

• How AMD designed a single system of work on Atlassian that spans hardware, firmware, software, and customer programs
• Concrete patterns for modeling complex engineering programs and keeping plans, issues, and documentation connected
• How Atlassian ties into AMD’s wider stack (source control, CI/CD, incident/ops tools) to give leaders a clearer view of progress and risk
• Change-management lessons from making Atlassian part of everyday engineering while still allowing teams some flexibility
• What does a Forge implementation look like with AMD’s complexity
• How the knowledge repository is harvested to bring insights and intelligence for AMD