>Can you guys genuinely work 2 weeks on a feature without doing anything else? Sometimes, but you need a progressive team that, e.g. that doesn't do stand ups

>Can you guys genuinely work 2 weeks on a feature without doing anything else? Sometimes, but you need a progressive team that, e.g. that doesn't do stand ups every day when almost all the work is multi-day efforts. You also need people who are technically skilled to not bug a developer about something they can find out themselves. More skill = more autonomy = less bother. That holds true for their work too. A regular occurrence is people around developers leaning on them to figure out technical details because they are not technical enough - that should be their job, so that gap contributes to a higher number of meetings. >Who the hell are these people that can reliably say feature X will take me 8 weeks? They're probably overestimating then time the delivery to be around 8 weeks (they are more skilled than their estimate would lead you to believe). A feature like that should get broken up, then you estimate the individual ones. It doesn't matter that the fragments aren't testable/deployable on their own, it helps with the complexity. Decomposing that feature also helps you estimate better.