Re:Why don’t software development methodologies work? (2014)
by Drdrdrq on Saturday December 09, 2017 @09:34AM
(#15885939)
True. Also, there is a fourth variable where you can cut corners (even if it's almost never a good idea): quality.
Great teams can produce much more than mediocre ones, but they too have a limit. When deadline is set too close, one of these 4 things has to give, and it is good to know in advance which one that is, so team can set the priorities accordingly.
Re:Why don’t software development methodologies work? (2014)
by Clubber on Saturday December 09, 2017 @10:20AM
(#15886140)
I would say that is part of the scope. The scope being a well tested, functional and relatively bug free software that does x, y and z.
Re:Why don’t software development methodologies work? (2014)
by Terr_ on Saturday December 09, 2017 @01:35PM
(#15887228)
Unfortunately most business people don't make things like "doesn't corrupt the database when an exception is thrown" into a feature bullet.
So while you can argue it's part of the scope, it's not part of the scope that anybody else seems to think about.
Re:Why don’t software development methodologies work? (2014)
by Jtsummers on Saturday December 09, 2017 @09:38AM
(#15885956)
Isn't this:
> Massive differences in productivity are possible depending on how individuals work together on a team.
Addressed by this:
>> Exceptions I've seen are with mature and well-bonded teams working on familiar scope they understand clearly, with a timeline they themselves defined.
?
This can be true but can also be completely false. Massive differences in productivity are possible depending on how individuals work together on a team.