[al2o3cr]

Not a fan of this - the core assumption seems to be that engineers aren't productive because they're just not paying attention to their schedule, so setting a fixed schedule like they're in elementary school again will "make them more productive".

It also seems to require some sort of Agile gnomes to do the grunt work of planning, because the 55-minuute weekly planning meeting handwaves "prepared work items" into existence.

[waterlink]

For the prepared items, there is actually another meeting on Friday, called Pre-Iteration Planning meeting where only Product Manager, Engineering Manager, and other necessary roles join (can be designer or QA if you have or need these). This is where work items are refined, so they are ready for estimation on Monday.

[waterlink]

Regarding the productivity of engineers and schedule, the focus isn't on the individual, however, on the team and its ability to collaborate and co-create. So the optimised schedule is to increase the productivity of the team as a whole, and also use the same fixed rigid schedule to build momentum over time.

[nullindividual]

MBAs demand rigidity in the creative process while they roll a 5d20 to come up with the percentage.