3 ms·

>8hr "planning" sessions One place I was at had quarterly 3 day planning sessions. That was something else.

by usrn 4y ago

the_lonely_road 4y ago
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.
- saimiam 4y ago
  This 87/3 split sounds suspiciously like what Agile with frequent checkpoints was supposed to mitigate.
  - HWR_14 4y ago
    But if you prefer the 87/3 split to Agile with frequent checkpoints is it really a mitigation?
  - notimetorelax 4y ago
    … and it mostly failed by burning out everyone with the daily routine.
- hectormalot 4y ago
  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."
- verve_rat 4y ago
  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
- usrn 4y ago
  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.
namdnay 4y ago
SAFe?
- noisem4ker 4y ago
  Scaled Agile Framework.
withinboredom 4y ago
I worked on one team that had a one week planning period every two weeks. The planning week, for us regular devs, was “do whatever you want” and it was epic. There were basically no bugs because a few of us liked tackling bugs for fun. Other people worked on optimization problems and code hygiene. For the people doing planning, they were always busy playing ticket shuffle, asking random devs random questions all the time. But those two weeks was cray and anything not done by the end of the sprint had to be done by the end of the planning period, and you better have a good reason.

>8hr "planning" sessions One place I was at had quarterly 3 day planning sessions. That was something else.

by usrn 4y ago

>8hr "planning" sessions One place I was at had quarterly 3 day planning sessions. That was something else.

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.

saimiam 4y ago
This 87/3 split sounds suspiciously like what Agile with frequent checkpoints was supposed to mitigate.
- HWR_14 4y ago
  But if you prefer the 87/3 split to Agile with frequent checkpoints is it really a mitigation?
- notimetorelax 4y ago
  … and it mostly failed by burning out everyone with the daily routine.
hectormalot 4y ago
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."
verve_rat 4y ago
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
usrn 4y ago
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.

namdnay 4y ago

SAFe?

noisem4ker 4y ago
Scaled Agile Framework.

withinboredom 4y ago

I worked on one team that had a one week planning period every two weeks. The planning week, for us regular devs, was “do whatever you want” and it was epic. There were basically no bugs because a few of us liked tackling bugs for fun. Other people worked on optimization problems and code hygiene. For the people doing planning, they were always busy playing ticket shuffle, asking random devs random questions all the time. But those two weeks was cray and anything not done by the end of the sprint had to be done by the end of the planning period, and you better have a good reason.