News for hackers. Stuff that matters.
Re:Incident Response Documentation by donavanm on Monday January 14, 2019 @09:02PM (#18908311)
Have you tried that before? Theres the obvious, that “night” is longer than business hours. Then theres the squishy people problems of things like sick time, meal breaks, using the WC, holiday, or PTO. And ignoring all that what do you do when there are two discrete problems at the same time? Varying shift times is terrible for humans.

In short, no 1 headcount does not 24/7 coverage make. I dont even believe the grandparents 2 per rota is enough to be sustainable. I have seen as small as 4 work acceptably.

Re:Incident Response Documentation by AceyMan on Tuesday January 15, 2019 @11:15AM (#18912201)
It requires four heads to cover even "20/365" (half the night "closed") and four is, in fact, short for true 24/7/365 = 8760 hrs, while a person works 2,000 hr/yr x 4 = 8,000.

If you try it with less, you're lying to yourself and everyone else.

(me: worked rotating shifts in a 24/7 operation for years)

Re:Incident Response Documentation by donavanm on Tuesday January 15, 2019 @12:31PM (#18912962)
Oh I was thinking of 4 minimum for the off business hours coverage. Actual 24/7/365 id put at 7-8 heads.

(Me: a guy whos been on oncall rotas for 15 years, worked swing shift for 4, and whos current org runs “follow the sun” support)

Re:Incident Response Documentation by quicksilver03 on Tuesday January 15, 2019 @04:12AM (#18909820)
A million times this. I'm about to tackle this issue at my current gig, and I won't have any on-call rotation with less than 4 people.