> There are all sorts of things you can do in an hour as a programmer: update a test, fix an automation script, fix and/or test a bug.
Free time to work between meetings is rarely filled efficiently. An one hour gap is either filled by something that's finshed in 45 minutes with the remaining 15 minutes difficult to fill, or filled by something that takes 1.5hrs and therefore requires a context switch.
With meetings its different. They last one hour because they last one hour, not because the content takes one hour to discuss.
But like 1 hour slots for work the same is true for fixed 2-week sprints.
And for containers on shelves, which cannot be placed where the frames are.
Free time to work between meetings is rarely filled efficiently. An one hour gap is either filled by something that's finshed in 45 minutes with the remaining 15 minutes difficult to fill, or filled by something that takes 1.5hrs and therefore requires a context switch.
With meetings its different. They last one hour because they last one hour, not because the content takes one hour to discuss.
But like 1 hour slots for work the same is true for fixed 2-week sprints.
And for containers on shelves, which cannot be placed where the frames are.