3 ms·
Why does this guy's blog always make it to the top of HN? Is he like famous or something? Just seems like another "bad idea" post that's just going to be (right
by dvt 6y ago
Why does this guy's blog always make it to the top of HN? Is he like famous or something? Just seems like another "bad idea" post that's just going to be (rightfully) trashed here. Overall, it's a bad idea for a few reasons:
- Someone made a mistake a long time ago, and now you're tasked with fixing it. That's not fun nor interesting.
- This type of work "gamification" infantilizes your employees. My guess is this would only work if everyone's like 22-25.
- John Cutler's "one day sprints" are a terrible idea, but this one is somehow even worse.
> Why the team did not ask the Product Owner about the proof of concept?
Because the product owner wasn't even around for most of the day ("I happen to be in Amsterdam that day, so I will jump in and out, and generally not available"). Yeesh. How could anyone possibly work under this guy? I would've resigned yesterday.
- alasdair_ 6y ago>"I happen to be in Amsterdam that day, so I will jump in and out, and generally not available" This was especially egregious given that the CTO insisted that everyone else make certain that there should be no interruptions the entire day and that they are 100% available for the team. This strikes me as a terrible way to lead people - demand everyone else give it their all, while phoning it in yourself.
- ebiester 6y agoI only can judge from the article - I don't know the dynamics of the team. Some people and teams thrive on meeting a challenge and it would be exhilarating. Others would see this as draining. For the right team, I would do this. That isn't many teams.