Re:Software effort estimation is mostly fake research
by virgilp on Monday January 18, 2021 @03:07PM
(#25825986)
Adobe executes (executed) massive releases on a well-defined cadence (1.5 yr per "creative suite"). Sure, I won't say they don't have collaboration, or top-tier engineers etc. But in the end, the success of this well defined cadence boiled down to the simple strategy of "we release what is ready". Everybody knew the deadlines well in advance, and everybody strives to 'make it' - but, (not so) occasionally, some teams didn't and you could see entire features get ruthlessly cut out. Simply no other way of synchronizing across the entire company... you cut scope to make it in time, and if you can't make it, that's it, your feature gets cut. With enough teams working, you still get features to showcase at each release.
[ Parent
| on HN ]
Re:Software effort estimation is mostly fake research
by vinay_ys on Monday January 18, 2021 @03:19PM
(#25826127)
That's pretty much how Linux kernel releases work. Just having a regularly scheduled release train that always runs on time – that you can catch (or not) is great.
Re:Software effort estimation is mostly fake research
by andrekandre on Monday January 18, 2021 @06:17PM
(#25827934)
> "we release what is ready"
this really is key, if you can do it
alot of companies though, are "business driven" which means releases and schedules are set beforehand, which makes this hard... (but if you can do it, its great!)
Re:Software effort estimation is mostly fake research
by throw14082020 on Tuesday January 19, 2021 @07:35AM
(#25832871)
What happens when you can release whenever. This question is probably quite relevant to most developers, because CD (continuous delivery) is popular.