Taro Logo
0

How and when do you break down a project into tasks?

Profile picture
Mid-Level Software Engineer at Taro Community5 hours ago

I’d love to hear your thoughts on how you approach breaking down a project into actionable tasks.

When do you typically do this?

Is it right at the beginning—where you create a P0 task and split things from there? Or do you let things evolve a bit and refine the breakdown as you go?

How do you do it?

I’ve tried vertical slicing—it worked in some cases, but in others it led to lots of PRs under a single ticket and made each ticket heavier than ideal. I’ve also tried sequencing, but curious if there are other factors you consider when structuring the breakdown.

One thing I personally struggle with is taking the time upfront to decompose the work. I sometimes hesitate—worried I’m not making visible progress, and that ends up being counterproductive in the long run. 😅

Would love to hear any approaches, patterns, or even pitfalls you’ve learned from! ty

4
0

There are no comments on this discussion yet.

Give it an upvote, and you'll be notified when the community chimes in!