Re:Even with Agile and Scrum waterfall will sneak in
by drran on Monday December 06, 2021 @07:19AM
(#29458812)
> 1 team, 10 houses = 10 weeks, 2 teams 10 houses, = 5 weeks. Ballpark.
Concrete needs 4 weeks to cure.
Re:Even with Agile and Scrum waterfall will sneak in
by iso1631 on Monday December 06, 2021 @10:00AM
(#29460483)
https://www.hunker.com/12002648/how-to-paint-an-exterior-hou... suggests building doesn't need foundations to be 100% cured, and you can start after a week or two
Here's exactly the same article but translated for a UK perspective, it's hilarious
https://www.ehow.co.uk/about_4674117_were-concrete-blocks-fi...
> Do not pour concrete in temperatures below -6.67 degrees C.
> Temperatures of 21.1 degrees C compared to 10 degrees C, for example, reduce the 50 per cent strength curing time from 6 to 4 days
Re:Even with Agile and Scrum waterfall will sneak in
by jollybean on Monday December 06, 2021 @10:15AM
(#29460671)
The issue is not cement or how long it takes to be cured, rather the crude and easy determinism of it all.
Home builders don't generally face existential struggle with the timing of the issue.
You don't go 5x over budget and have it take 5x longer because of this.
You can reliably schedule around cement.
It's predictability.
You can plan the construction of a building, because the elements are known. If someone fails to deliver a bag of nails on time, it won't matter.
If you add labour to a project, it will very ballpark accelerate linearly.
1 team, 10 houses = 10 weeks, 2 teams 10 houses, = 5 weeks. Ballpark.
More developers do not mean the software will be finished more quickly.
There are economies of focus in software, generally not scale.
Which is why you want good developers.
The other factor is that 'Requirements Change' in Software more than they do in building, and that's the other #1 issue that causes problems.
The entire ethos of 'small releases, often' is built around that.
Software is evolved a big organically for this reason.
Waterfall is obviously counterproductive.
If there is a 'default' methodology in software it's 'Iterative Waterfall' whereby you break the project down into the smallest reasonable phases. There can be an overarching plan but it has to be nimble.