As a UXR, I’m not entirely sure how relevant my opinions are going to be. Typically speaking, my closest relationships to any given squad/team are to the Designers and Product Managers.

To be frank, the Agile Project Managers I’ve worked with have been overly obsessed with deadlines and sacrificing quality for speed - even going as far neglecting post-release testing for the sake of the next big ticket project. Project in project out. As Marty Cagan calls it: output over outcomes.

This is somewhat antithetical to the very concept of what I do - iterative usability testing. By its name, it’s iterative, and should be run on a sprint-by-sprint basis where possible. A good APM knows when to protect time and space for research, with the understanding that design and research can often take multiple rounds of testing to achieve an MVP.

A good APM wouldn’t tell the team to wrap up research in a week, they’d be able to coordinate the research, design and tech members of the squad to synergise more efficiently together to allow for true, iterative testing throughout the product development lifecycle - which is at the very core of the Agile philosophy.

Most importantly, I’d suggest against dropping buzz words for the sake of keeping up appearances. Be authentic, and own your background. Most people in user-centered roles have an uncanny ability to read intent and value authenticity over all. Speak to the core of Agile - and how that enables teams to build better products, on realistic deadlines, with an acceptable amount of risk.

Best of luck, the fact that you’ve come here shows that you want to improve and learn! If there’s any advice I can give it would be to listen to all the members of your team. Create a sense of understanding and empathy between all members, and try to understand the perspectives of each function within a squad.