Content
@
1 reply
0 recast
2 reactions
↑ j4ck 🥶 icebreaker.xyz ↑
@j4ck.eth
i wana talk about Linear i know /farcaster team uses it, we use it at /icebreaker do you use it? do you use Initiatives? how do you organize your work? do engineers or product people write the tickets? considering even starting a channel for just this topic. i wish they offered an Academy tbh cc @deodad :P
10 replies
0 recast
91 reactions
Tudor 🟣🟡
@tudorizer
>do you use it? yes >do you use Initiatives? how do you organize your work? In the hierarchy the recommend. Initiatives -> projects -> issues, although we don't spend too much time bikeshedding around what goes where. The intiatives became a good replacement for Notion pages, because the Linear editor has collaboration features. >do engineers or product people write the tickets? well, both. This depends heavily on your company culture. I was fortunate to have almost 20 years of experience building software and of working with similar people, so we've had similar discussions about Jira, Basecamp, GitHub, Trello, etc. We also use Views a lot.
1 reply
0 recast
1 reaction
↑ j4ck 🥶 icebreaker.xyz ↑
@j4ck.eth
thanks for the answer!! yes, initiatives w the page editor is super nice. have started orienting that way. do you have a quick method to determine what should be an initiative vs a project? sometimes i get caught up there sounds right on who writes it - who does it at yours?
1 reply
0 recast
1 reaction
Tudor 🟣🟡
@tudorizer
Initiatives vs. projects is a matter of scope. Your unit of measure might vary, but I'll take a sprint as one example: issues < 1 sprint projects >= 1 sprint initiatives > 1 project You can slice it other ways too: KPIs, roadmap items (deliverables), weeks, months (temporal) I also make sure initiatives and projects have an end and a start. Zombie ideas are demoralising. The tickets are written at first by anyone who's closer to the product (PM or engineer who is so inclined) in a format that is high-level enough, yet clear on expectations and outcomes. A second version is agreed upon with the implementing engineers. Some teams call this backlog grooming.
1 reply
1 recast
1 reaction
