Post

I know the feeling. We used six-week cycles (5 + 1 cooldown/planning) at Maze, and it worked really well for us. I think it's perfect for platform work.

i’d take 5+1 over 2 weeks

Haroen Viaene

@haroen.me

do you pick individual tickets in sprint planning? we started not assigning the tickets when the sprint starts (only when you actually start to work on a ticket) and that removes the individual component of the deadline IMO.

11 Dec 2025

we do, without defining scope up front, isn’t it just an arbitrary line where you say okay today is not sprint 5, its sprint 6?

Haroen Viaene

@haroen.me

11 Dec 2025

I mean, are the tickets assigned to people in advance? if it gets pooled for the entire team, I think there's less individual deadline effect

12 Dec 2025

yes, people in the team assign themselves tickets on the first day, enough to last the sprint

Joel

@handle.invalid

linear.appLinear Method – Practices for buildingThe quality of a product is driven by both the talent of its creators and how they feel while they’re crafting it. To bring back the right focus, these are the foundational and evolving ideas Linear i...

I recently joined a new startup and we’ve mostly gotten rid of agile in favor of the linear project method linear.app/method Each swe on the team is a project owner, who is responsible for writing and refining stories for their project as they go. No need for sprint planning, retro, refinement

Joel

@handle.invalid

Only meeting we have is daily standup. Project owners interface with stakeholders directly and so own the process of setting meetings as needed

11 Dec 2025

thats what my team usually does, i really like it. however, it is hard for someone to look at what the team is doing and when is it shipping, i give you that