> In the second case, I got the sense that leadership didn't really grasp how costly the context switching was for us due to not having much collective experien

> In the second case, I got the sense that leadership didn't really grasp how costly the context switching was for us due to not having much collective experience working in mobile (not to mention the rude awakening of having to deal with iOS dev dependencies). Interestingly I see this is a few ways: * Every small 15-30 minute call knocks me out for hours. I really need at least one full day a week with minimal meetings and that includes the daily stand-up. I honestly think the daily stand-up costs companies millions per year in productivity cost * Moving from project feature to feature is costly. So if you're working on feature X this sprint and then the PO moves to feature Y in the next sprint due to priorities it'll slow down dev. Doing this often (say every sprint) will kill velocity * Moving from project A to project B is also a big killer for productivity * Moving around tech stacks as you've said it happens occasionally in my experience but when it happens you're often flustered