Amazing stuff. It was a real pleasure to read. Despite its length I couldn't get myself to skip ahead or skim. We're now in the process of switching to a struc

Amazing stuff. It was a real pleasure to read. Despite its length I couldn't get myself to skip ahead or skim. We're now in the process of switching to a structure similar to Basecamp's 6-week cycles[0]. And those cycles obviously do have a deadline. However, I would still say this kind of deadline is better than your typical one for a couple of reasons: 1. The team is self-managing. Typically the team was involved in the pitch process for the project, so they have vested interest in getting this done. I think this is key to avoiding the Student problem. It's no longer an assignment dropped from above, but something you are keen to push forward. 2. The cycle is 6 weeks rather than a sprint of 2... So this feels more like a slower-pace mini-marathon. And the team has autonomy to drop features or make adjustments. I admit that's a weaker argument for it than the one above. I wonder what's your take on this? [0] https://m.signalvnoise.com/how-we-set-up-our-work-cbce3d3d9cae https://m.signalvnoise.com/how-we-set-up-our-work-cbce3d3d9c...