The team I was on had largely no experience with UX. So I led workshops, opened user interviews up to the whole team, and would regularly host a UX working/learn hour where anyone on the team could help with whatever I was working on at the time. It sped the entire team up, and gave our engineers a window into exactly what they'd been missing: how users worked inside the tool.

Our tool was built really hastily. It had been designed by developers as series upon series of quick fixes to ad hoc requests. No one had considered what the user's workflow would be when they were building it. It was my job to piece together an understanding of how users were currently using the tool, and how they needed it to work.

Because the team was new to UX, and agile workflow in general, one of our teams main initiatives was bringing about more collaboration in the prioritization of efforts, and daily strategizing. I made sure to include Devs, Data Scientists, my PM, and anyone else that wanted to attend, were involved in research, synthesis, and prioritizing initiatives.

Something else that had never been a part of the team's process was a truly agile system of prioritizing initiatives. Me and a few devs and several UXers from the company got together to brainstorm how to effectively utilize team skills in prioritization, and come up with an agile approach that worked for us.