It pains me to read this because the scrum meetings at my last companies were fluid enough that you could say anything. So if I worked on a problem which turne

It pains me to read this because the scrum meetings at my last companies were fluid enough that you could say anything. So if I worked on a problem which turned out to be more complicated than originally estimated, I would just list out all these sub-problems and so people would realize that I did a lot. The company I work for now does scrum very differently. During the scrum planning meetings, we must break down all tasks so that they are less than 8 hours. So this means that every day, you MUST be able to point to at least one completed task every day. If new complexity was uncovered (which of course is always the case due to technical bloat which occurs when developers are always pressured like this), then you need to take it upon yourself to cut all the corners necessary to get your minimum of one daily task done. That is unpleasant and unproductive. Though I guess it helps existing devs build a moat of complexity around themselves so that, over time, the work becomes predictable for you but not for others who are less familiar with existing code/constraints.