Whenever talking about Agile, first we have to look at the Manifesto for Agile Software Development, so that we can understand how its values and principles can be embraced with Xray.
There are many ways to look at Agile, though.
Overall, Agile's purpose is to "Achieve (product) Greatness" - How?
By...
With Xray, you can see what is happening on your existent Agile (Scrum/Kanban) Boards or on your stories; no need to ask
Real time testing/coverage feedback on the issues you’re working on (e.g. Stories, Epics, Tests) providing clear insights on quality. Users can quickly analyze test results, evaluate how a Story is on different versions, besides the actual one. To have even deeper understanding on how their feature is performing on different "contexts" (e.g. browsers, mobile devices), users may analyse their test results and coverage on different Test Environments
Xray understands the "hierarchical" relation between Epic<=>Story. In fact, it's just one of the possible scenarios for handling parent and "sub-requirements." That means that Tests covering a given Story will implicitly cover the related Epic. Thus, from the Epic screen, you can track its coverage, including the latest Test results based on the coverage of related Story issues
Testers can clarify PBIs (product backlog items), assess risks and provide better estimates
Blend programming & testing together by having developers and testers working together in the same development related activities, as equals
Testers communicate directly in the issues being worked on (e.g. stories, bugs, tests)
Work together with customers and other team members using BDD and Gherkin based frameworks (e.g. Cucumber)
You can adapt Xray to the process your team finds most useful and make them more Agile. Use your team's feedback to embrace changes.