4 ms·
Author here. Sorry you think that. I see the article title has been changed, although I wrote this about 3 weeks ago so I'm not sure why it's been labelled as
by bobm_kite9 7y ago
Author here. Sorry you think that. I see the article title has been changed, although I wrote this about 3 weeks ago so I'm not sure why it's been labelled as (2019).
This article focuses on the Timebox issue. I'll be posting the follow up in a couple of weeks, will post on HN... although there's plenty of other content on this site that covers where I'll be going with that solution.
Apologies if it didn't cover everything you wanted - but I find that long articles tend to lose the readers too easily, and I'm trying to keep to a single main point-per-article in my writing as a matter of discipline.
I'll look forward to your thoughts on the next one.
- FZ1 7y agoJust letting you know the link to the 10X article gives a 404. I tried to read it, but "page does not exist". ---- Edit for clarification: First link in first paragraph after "10X" section header. About "visited the terrain before".
- bobm_kite9 7y agoThanks for letting me know - some Jekyll weirdness going on there, will look into it when there's less traffic.
- loopz 7y agoThe ending is your actual point, which is excellent. With scrum being so oversold in companies, it's a hard sell though. So an article starting out with this premise would perhaps gain better traction: "But actually, we’re now three degrees away from the original problem of trying to build the right thing. The team is focused on figuring out how much they can get done in a Sprint, not whether they are building the right thing. Scrum purists might argue that this is the purpose of the Sprint Goal, which should be agreed in advance.. but actually this is usually just a bunch of items from the backlog, shoe-horned into a sprint-sized chunk of time."
- bobm_kite9 7y agoAuthor here. Yes, the overall feeling I'm getting from the responses is a disappointment that I didn't get to this. Initially that had been my intent, but as I wrote it I realised I was trying to crowbar too much into a single article. However, I am pleased that people seem to agree with this article's diagnosis of the problem. The next article will build upon this one (and others in the series). Hopefully it will be equally well considered on HN, I am interested to see how it goes down.