Earlier quoted context omitted.
It immediately irks me that I'm defending agile here, but part of the point of agile is that the developer doesn't really know what the end user needs, so it's, in theory, better to get a minimum viable product out that meets the user's need, then refine on subsequent releases, rather than spend years working on releasing something perfect that it turns out doesn't fill the user's need. From a similar perspective for…
> From a similar perspective for journalism, I think there's an argument that can be made that it's better to get most of the information out right away, even if some of it is inaccurate, and then correct the inaccuracies later, rather than wait until every piece is confirmed and edited perfectly to release the information. Argument to extremes, think of a hurricane or volcano explosion. Following the argument to the…
"There is a hurricane, and we're hearing initial, unconfirmed reports that it's to the south. We want to stress these are unconfirmed at this time, etc etc"
Which is something that would traditionally be broadcast in an emergency.
Obviously, we're really talking about an extreme hypothetical, but as long as it's clear the information may not be complete or accurate at the time of reading, I see no problem (as long as it is eventually accurate).