Yes, but what if that appearance of stability is unwarranted? After all, the underlying process is just Dorothy moving things around, and when Dorothy's on vaca

Yes, but what if that appearance of stability is unwarranted? After all, the underlying process is just Dorothy moving things around, and when Dorothy's on vacation things might not be working the way they should. This brings up an interesting aside: they right way to build software for "agile" processes might look very different from the right way to build software for "frozen" (non-agile) processes (big corp, stable processes, few surprises if any, etc.). Ideas such as abstraction/encapsulation that work well for the latter situation might be totally out of place in the former.