4 ms·
Why is that funny? I think it is normal that a hobby team working in a silo on an alternative client with a low amount of users move faster than a full engineer
by zorr 4y ago
Why is that funny? I think it is normal that a hobby team working in a silo on an alternative client with a low amount of users move faster than a full engineering organization working on a mass rolled out product used in corporate environment all over the world.
For a new feature the hobby team can just hack away for a few nights, push the release and they are done.
The engineering org needs to plan and coordinate the feature across multiple teams (web app, desktop app, mobile app, Graph, teams admin panel, o365 admin panel,...) and then make sure it fits well into the rest of the MS infrastructure (policies, permission scopes, IT admin controls, licensing, auditing,...). Legal might need to be involved.
And then after aligning all those teams and waiting for each team to prioritize and do the work it needs to get into the MS roadmap as well going through the usual stages (private preview, public preview, General Availability). And once it hits GA it needs to be supported for many years.