It's very similar to Scrum, with some nuanced differences. He mentions "do not work on incremental changes" and "do not focus on user stories", and instead "do construct small goals that achieve more general yet still concrete outcomes", and "do prioritize those goals".
I think his advice suffers from the same problem Scrum does, which is that it's simultaneously too generic and too constricting for anyone to perform it correctly and get good value out of it unless they just happen to be really excellent at their jobs or have a great team leader.
Seems like this field is very preoccupied with attempts to distill excellence into a formula. But the skill you need to do this approach well is "identifying doable tasks that make meaningful progress towards the overall goal", which basically just the entire skill of project management.
Comments
It's very similar to Scrum, with some nuanced differences. He mentions "do not work on incremental changes" and "do not focus on user stories", and instead "do construct small goals that achieve more general yet still concrete outcomes", and "do prioritize those goals".
I think his advice suffers from the same problem Scrum does, which is that it's simultaneously too generic and too constricting for anyone to perform it correctly and get good value out of it unless they just happen to be really excellent at their jobs or have a great team leader.
Seems like this field is very preoccupied with attempts to distill excellence into a formula. But the skill you need to do this approach well is "identifying doable tasks that make meaningful progress towards the overall goal", which basically just the entire skill of project management.