|
|
|
|
|
by eropple
922 days ago
|
|
> if you are solving it, you get to choose how to do it, in what order and with what priority In times of plenty, this works, and I think it can have high velocity. Especially with very small teams that all have high levels of direct investment in the result. There are also times of famine, however, and the work that keeps the lights on is often not work that even invested software developers want to prioritize. When making money is on the line, there's always somebody who's there to make you eat your vegetables. Who, in your conception of the problem, is that? |
|
What kind of work is that? And why are the developers willingly not wanting to prioritize it, if the alternative of not doing it is becoming jobless? Do we need some kind of PM figure to say things like: "If we don't make this feature for the client, we are doomed, so start coding. Chop chop!". And do we need to keep that guy on the payroll for simply relaying a message?