Agile development methodologies are iterative. This generally means that a partial solution gets implemented now with a more complete and more correct implementation in the next iteration(s).
No, agile doesn't mean implement a partial solution with potential errors. The book certainly doesn't state or even imply anything remotely like what you've tossed out. (Nor did my review.)
The book says "Generally, a process that encourages safety evaluations periodically throughout development will be superior to a process that depends upon a one-time safety evaluation at the beginning of a project." (p 184)
That means, as my review said, shortening cycles before implementation in order to get better feedback so that those bugs don't make it to the rollout stage.
Slashdot Mirror
No, agile doesn't mean implement a partial solution with potential errors. The book certainly doesn't state or even imply anything remotely like what you've tossed out. (Nor did my review.)
The book says "Generally, a process that encourages safety evaluations periodically throughout development will be superior to a process that depends upon a one-time safety evaluation at the beginning of a project." (p 184)
That means, as my review said, shortening cycles before implementation in order to get better feedback so that those bugs don't make it to the rollout stage.