What kind of non-agile bottom-up software projects have you experienced? Bottom-up waterfall? I guess it’s possible in theory but that would be a sight to behold.
My only point is that in most situations, upper management are fools that should be left to their devices and should never get a say in development methodologies. By definition if upper management imposes Scrum, it’s a self-defeating prophecy.
Waterfall | Agile | Scrum | |
---|---|---|---|
Top-down | Can be great (esp. with rigid requirements like fintech, for safety-critical systems, or integration with traditional engineering processes with rigid schedules and feature sets) but will probably be more expensive | Bad managers trying to make-up for their own lack of foresight | Can’t exist (but some companies pretend very hard) |
Bottom-up | Probably can’t exist (but I haven’t seen anyone try) | Yes | Yes |
Your average tech company should be somewhere in the bottom-right, but bad managers are trying to pull the needle upwards to justify their existence or make up for their incompetence. But they still call that “Agile” (which can be true by some definitions of the word) or “Scrum” (which that isn’t, by definition).
Greenfield nuclear is (probably) not economically relevant.
Refurbishing existing NPPs has a LCOE on-par with renewables and gives breathing room for variability issues that will otherwise be absorbed by fossil fuels until that eventual transition to storage/smart grid.
Any discussion of nuclear’s costs/profitability that does not distinguish between greenfield and existing/refurbished is agendaposting since most of the costs of a NPP are upfront.