Reconsider agile vs waterfall

[thomasholmrod]

"Projects that are better suited to the waterfall methodology are those where delivering an intermediate product is not viable. For example, a library to perform Fourier transformations is not useful unless fully implemented whereas a graphical data processing toolkit may be."

Hardcore SCRUMmers would claim that everything can be broken down to smaller stories that each provide some value. For the Fourier transformation, there may be different methods, different levels of how sophistacated the API is, documentation, etc. So I would be careful with a sentence like this. Maybe replacing "is not useful" with "may not be".

[DanNixon]

Based on feedback today we will rewrite a lot of this section.

This will include:

• better explanation of agile and waterfall, stating that there is a scale/spectrum of methodologies with these being the extremes
• give some examples where different methodologies are used (likely from WO10 projects)
• give references for more in-depth details

[AnthonyLim23]

@DanNixon could you add some references for more details? I think the stuff I wrote yesterday covers most of these points. Would you agree?

[DanNixon]

I can try, I may have to ask others for some good references though as day to day i tend to just use common sense rather than refer to publications for this.