undefined | Better HN

0 pointsHeyLaughingBoy6y ago0 comments

It can usually be done. The problem is that people assume that now that you have that list of subtasks, you can iterate through them one at a time until you've built the feature. That's the major disconnect.

What I do with my guys is I make them decompose the feature, but with the understanding that they'll probably be jumping from one subtask to the other, back and forth, as they understand what it is they'll be building. AND they'll probably come across new subtasks as they work through the feature.

It makes Jira look crappy, but it Reflects Reality (tm) which to me is far more important than keeping Jira clean.

0 comments

1 comments · 1 top-level

Ididntdothis6y ago

That's how it works. Touch something here, touch something there, learn from it and slowly build up the whole thing. I think Scrum and Kanban may work if you have a somewhat mature system where you add incremental features but if you do something relatively new and big the backlog can not reflect reality. Or it forces a workflow that doesn't make sense. I have seen it multiple times where people refused to make changes to something because their story was done already. Never mind that the design turned out to be unsuitable.

1 more reply

j / k navigate · click thread line to collapse