Personnel System
You're replacing your personnel system with a new one. Obviously you need an integrated database and can't release the system until it does everything the old one does, plus all the new things you've thought of. There's just no way you can release this incrementally.
This could turn into one of those horrible tail-chasing exercises where there's always just one more feature that you have to put into the new system before it's ready. Just don't go there.
Instead, what if we made our database compatible with the old one, but with new relational tables for new features that are needed, and delivered some of those new features. We could produce new reports that summarized the use of the new features, and we could produce new versions ...
Get Extreme Programming Installed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
