For decades, large IT Transformation projects have been planned using manual spreadsheets or hand-cranked databases. All required steps were neatly visualized in a massive MS Project Gantt Chart — of course, with buffers built in right from the start because we knew there would be delays. We also knew that the real project devil would be in the asset readiness detail, something that couldn't be managed in a Microsoft project plan. However, we would still spend an exorbitant amount of time updating our scorecards and spreadsheets even though they would inevitably fall apart entirely at some point. It was slow and inefficient.
Now, with the Windows 10 Servicing model and its fast and continuous update cadence, attempting to manage thousands of readiness activities in multiple spreadsheets is useless because managing Windows-as-a-Service is more like juggling hundreds of balls at the same time. Not only do you have to keep the current release balls up in the air, you have to keep your eye on the future balls coming at you just as quickly!