> It ultimately boils down to "I don't want to report on what I am doing or how I plan on doing it." That's not a good take on it, let alone all boiling down t

> It ultimately boils down to "I don't want to report on what I am doing or how I plan on doing it." That's not a good take on it, let alone all boiling down to it by any measure. The constant status reporting of scrum is a distraction. That doesn't of course mean the engineering team shouldn't communicate both plans and results in a timeline that makes sense. If the work is so incredibly trivial that status needs to be reported every.single.day, then it's not work I'm interested in even doing. Progress on anything creative and challenging takes a longer timeline and daily reports are a very annoying distraction.