Maybe we do. I don't know what you think a Senior Engineer does. I think a senior should be able to take responsibility and ownership over his work and the work of his team. I don't think they're able to predict business needs without any feedback about those business needs. I certainly think a senior should be able to divide big chunks of work into smaller parts, because even a junior should be able to do that; that's pretty much the core of programming.
I also think a senior should be able to understand how a development process works without resorting to silly strawmen.
There are a multitude of processes for getting feedback; Agile is a contender but by far not the best. Please don't be disingenuous - Agile processes are often strict and brittle - anything that doesn't fit into the Agile round hold can't be done, and the 'sprint' is the worst of the awkwardness.
Strawmen are different from examples; its lazy to call any explanation a strawman.
In what way is Agile strict and brittle? It's entire point is to adapt quickly, on short iterations. To be flexible. In probably the most strict form of Agile, Scrum, constant improvement of the process is an intrinsic part of the process.
I'd like to see a process that handles this better while clearly being not Agile.
I also think a senior should be able to understand how a development process works without resorting to silly strawmen.
reply