Product Backlog Ordering

Shouldn't the evaluation of any dependencies also involve the teams which are expected to do the work?

Yes, absolutely! Thanks for the good point, Ian! However, I am not interested in who should be involved. 

I am concerned about one particular point. Should I also consider the dependencies to other products during product backlog ordering? I know that there are different ordering criteria such as value (overall value), dependencies between product backlog items, risk or costs.

But also the dependencies to other products? I think, this can be tricky and it may be to complicate to handle.

I'd like to address a specific point to you. I am aware of the criteria according to which a product backlog can be ordered. It's about whether I should also consider the dependencies on other products.

I don't mean to offend but in my opinion the fact that you had to ask if dependencies are a criteria for ordering the backlog indicates that you are not aware of the criteria for ordering a product backlog.  To me any outside dependency is a criteria for ordering.  However I also believe that the Scrum Team should do everything in their power to rectify outside dependencies because I view them as a impediment.  

Consider it this way.  Is it possible for your Scrum Team to deliver value to the stakeholders if there is an outside dependency that must be delivered before the work that your team has done can be used?  If not, then your team is not delivering value. 

I am assuming by your question that you are the PO.  Based on that assumption, as a Scrum Master I would coach you to be working hand-in-hand with the PO of the product on which you are dependent to order the items in both backlogs so that each team can deliver the appropriate value to the stakeholders/organization at the optimum time.  I would be working with the entire Scrum Team to find ways of dealing with the impediment.  For example, if both of the products are developed in house, would it be possible for your team to make the necessary changes in the other product's code base using the other team as consultants and code reviewers?  That would help your team to deliver their value and not have any outside dependencies.  And in fact it is something that my current organization does on a regular basis. 

Many thanks Daniel for your input! Your point of view sounds good to me. 

Thanks for your help!

I guess it's up to the product owner to prioritize in whatever way he/she sees fit.

Perhaps food-for-thought; an item high on the backlog usually means something really valuable to your company, so does it become less valuable if you can't start working on it because of an dependency? If you alter it's position, is your backlog still a correct representation of the things you 'should' (but perhaps can't) be working on?

That being sad, perhaps to consider when your team relies heavily on another team to finish things, then perhaps your 'cross-functional' team is missing certain skills so that they wouldn't be so much dependent on another team?