Hacker News Reader

Comment by the_lonely_road | Hacker News Reader

Wait that actually sounds awesome. What we’re your issues with this practice? A 3 day code freeze while everyone works to solidify a “meeting of the minds” followed by 87 days of heads down progress sounds like fucking heaven to me compared to the weekly planning meetings on top of daily stands up I live with now.

View on HN

pros and cons, will depend on the type of thing a team/company is working on. I've been on the receiving end of this with some negative experiences as well.

Team1: "Hey, we've launched a new initiative a few weeks back. Important for us to be able to add one field to the response of your internal billing API. Can we discuss what that would take?"

Team2: "Hey, probably a few hours of work. But, we just had our quarterly planning last week. In 12 weeks you can submit for Q2, and _maybe_ we will plan it somewhere in May or June."

This 87/3 split sounds suspiciously like what Agile with frequent checkpoints was supposed to mitigate.

But if you prefer the 87/3 split to Agile with frequent checkpoints is it really a mitigation?

… and it mostly failed by burning out everyone with the daily routine.

SAFe (as I've seen it) has a two day planning event every 10 weeks.

Plus a planning every sprint and daily stand ups.

sigh

We had weekly planning and "triage" meetings too. This was on top of the normal stuff. It wasn't all heads down either. If you finished your tickets before the next planning meeting you could relax, edit the wiki, look for stuff to write new tickets for etc.

Reply on news.ycombinator.com