2 ms·
> Agile gives the programmer a voice in the process, and once they update the tasks and time estimates, the feature's priority can be re-evaluated. You couldn'
by pdimitar 9y ago
> Agile gives the programmer a voice in the process, and once they update the tasks and time estimates, the feature's priority can be re-evaluated.
You couldn't be more wrong on this one. Managers love their power and they don't give it away to programmers no matter what.
In 15 years of career I've never seen a manager treat a programmer as a decision maker, not even once. And I suspect that's a biiiiiit more than "anecdotal evidence".
What usually happens is:
- "Why did this estimate change from 2 days to 3 weeks?"
- "Are you sure you're doing this right?" (coming from a non-technical manager)
- "Let me stop you right there. We heard your concerns but you overplay their importance." (that I can agree with sometimes)
- "This feature is important. Reduce your estimate, it doesn't look good to the people above us."
...etc. to infinity.
Agile is not, and never was, a magic bullet. It's kind of like some economical systems that only existed on paper -- sounds perfect in theory, is never implemented well (or fully) in practice.