How do you collaborate with IT teams who use different methodologies?

This is a complex question that's highly dependent on the business culture, the teams involved, visibility of the project/program at hand, org structures of the teams, project/program management and steering patterns, other 100 factors... However, strategically, Consultants should be, as much as possible, business value/goals delivery oriented. Hence, regardless the methodologies the specific teams are using, what needs to be governed is the delivery pipelines. There are different standards that consultants could use to establish such a pattern and its governance. Then follow through, avoiding exceptions, as much as possible...

Most of the time, the methodology is not the problem. Joining a new team requires open mindedness and having a learning spirit. You must be ready to unlearn and relearn. Collaboration is not methodology dependent, be it agile or waterfall, your ability to learn quickly and thrive in a challenging environment is the key.

Absolutely right. Before working with any new IT team, one should understand the respective methodology. Additionally, it's essential to grasp the core standards of these methodologies, making it easier to correlate with your methodologies and adapt quickly to new ones.

Hybrid can be suitable for projects involving the customisation of a vendor solution, where the expected output has not firmed up at the start, which can be due to conflicting user requirements coming from different departments who have not worked together before. There is some level of commitment to cover the basics in FSD to start off things while pushing for an earlier UAT open to rapid and incremental changes

This is a tricky question to know the collaboration skills of the different IT teams. We need to understand the different methodologies and ceremonies to achieve the desired output. we planned our task according to the methodologies frameworks.

Working with Hybrid methodology can mean allocating more resources and time to UAT where major changes to the original design can happen

Informal messaging have filled the gap where there are too many participants in a traditional meeting for the more quiet members to contribute their views, and we risk having valuable input not considered

We should discover which tasks took us the least effort to perform and be the first to volunteer ourselves. Perhaps we can cover each other for areas we’re still improving on

Showing appreciation ranks high as well, as well-meaning feedback without a good underlying relationship can be interpreted differently