Hey! thank you! :)

I'm not sure if I understood the question. When you say size, do you mean Story points estimations or team size?

In the end, when we have tickets estimated with high story points, it's always good to try to see if there's a way to split the ticket into smaller ones. By doing this, you might be able to reduce the cycle time and increase deliveries.

Of course, this is deal world 😅, so there will always have situations where there will be outliners (and that's fine!). The important thing is to get them, expose to the team and let them reflect if that could have been avoided.

For example: the average cycle time of your team can be around 4 days. But one ticket stayed there for 8 days, simply because it got blocked due to translations missing. By making the team reflect on it, there was probably nothing they could've done after started the ticket to speedup this and get the translations, as it relies on people from outside of the team, but the team could come up with a team agreement that, whenever a ticket requires translations, the ticket must not be started until the translations are provided. This way, the cycle time would have been reduced.

In the end, the team can always fall into a situation that outliner tickets will appear, but we should make the team aware of the situation so, whenever it's possible, they try to improve and ship things faster. If it's not possible, well.. it happens too, but there might be ways to improve, and the important is that we all learn.