|
Mike Barthold wrote: the entire company lives "scrum". IMHO, that's the only way to do agile. The agile methodology has garnered a bad rap because many developers have been forced to follow it in isolation, under the premise that it will magically allow software to be delivered faster. If your company isn't agile, you're doing agile wrong.
/ravi
|
|
|
|
|
N_tro_P wrote: In said company though, there are going to be divisions that can use agile and use it effectively. Good point.
/ravi
|
|
|
|
|
Deadline:
(a) A hardware communication cable that resists all all varieties of handshaking, however friendly.
(b) A vague series of prophesies intended to establish a time-frame by which a certain project should not be complete.
Cheers,
Mick
------------------------------------------------
A programmer is a person who always checks both ways when crossing a one-way street.
|
|
|
|
|
/ravi
|
|
|
|
|
...because underestimating time is as bad as underestimating cost: it hurts the company financially in the long run. Think about it: does a time pressure improve quality? No - it means short cuts get taken, which means maintenance costs a whole pile more than it should, changes take longer, ...
It's not easy though - without some pressure there is a tendency to "slack off"a bit unless the developer is both well- and self-motivated.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Unfortunately many companies refuse to accept this simple truth.
Because "we have to release now because it's in this quarter's budget. Maintenance is an entirely different account and budget. That's the problem of cost center 1337 and not cost center 0815"
And THIS is, what makes software "bad" sometimes...
|
|
|
|
|
That's the problem with companies these days: they are all run by accountants, who know the cost of everything and the value of nothing.
Short term gains, long term losses - it's all they know, and then they wonder why companies go bust.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|