3 ms·
Week patterns have a long history, and humans have to rest some point, so I respect the "Nothing ships on Friday [and implicitly Saturday or Sunday]" plan outsi
by tialaramex 7y ago
Week patterns have a long history, and humans have to rest some point, so I respect the "Nothing ships on Friday [and implicitly Saturday or Sunday]" plan outside of very young (often self-funded) startups where basically all that the half a dozen people doing it are thinking about 24/7 is that one project so there aren't really "weekends" anyway at first.
However, bigger organisations can get really out of hand with this. They start out with small carve outs, oh, nobody really works from the start of Christmas week until the first full week of the New Year. Soon it's from Black Friday although good luck scheduling anything the week before that, and so before you know it they're declaring that nothing can even be planned for the months of November, December and January each year.
Now, if you really must have this habit, which I don't recommend, what you need to understand, just as much as the "No shipping on Friday" folks is what this does to your perception of time. If you have "Don't ship Friday" then the question in the Tuesday meeting "Will it be live on Monday?" must be re-phrased "Is it ready to ship by Thursday?" and not every manager seems to understand that. But when you have "Nothing can be scheduled for our 90 day Winter Risk period" as policy then the question in that meeting "Will we be ready for the January 31st legal deadline?" is actually "Are we 100% sure we'll have fixed this by the end of October this year?" and I have yet to see anyone who recognises that despite having a policy which makes it so.
- ineedasername 7y agoIn the early 00's I had to work with a company that setup payment portals. My workplace already used them for existing portals. We needed another for a separate service. It took a few days to get the paperwork signed for the banking end of things, and then we were told by the portal people "sorry, yesterday was Tuesday. We only go live with changes on the first Tuesday of every month."
- tim58 7y agoI'd like to provide a counter-argument. Every software release includes risk. There's risk that there are bugs. There's risk that it will introduce regressions. There's risk it will cause a major crash. We can do things that reduce the risk. We can have recovery plans for negative outcomes. We cannot eliminate all risk. The reason businesses have black-out deploy dates is so that they can control the risk. Deploying code 24 hours before a critical business day, like black friday is for some businesses, is an entirely different risk/reward ratio and should be treated different. Even 90 day risk periods can be valid for some businesses, for example seasonal businesses during peak season.
- tialaramex 7y ago> The reason businesses have black-out deploy dates is so that they can control the risk. Deploying code 24 hours before a critical business day, like black friday is for some businesses, is an entirely different risk/reward ratio and should be treated different. Even 90 day risk periods can be valid for some businesses, for example seasonal businesses during peak season. That's a completely valid strategy, but as I explained you need to actually embrace the consequences of this strategy in your thinking. If the next 90 days are a "risk period" then when somebody says "Next week" they actually mean "Three months from now" not "Next week" and everybody in the business needs to start thinking that way. Sometimes that's going to cost a bunch of money. For example, if you have such a 90 day period covering November, December, January as in my example, then a system which alerts you to certificates on public facing web sites that expire in less than 30 days time is no good, you can't act for 90 whole days, so that system needs to be re-calibrated for more like 100 days. Once you accept the 90 day risk period as a reality rather than a convenient fiction it gets very expensive. Make sure the people who insisted on this risk period are paying, because that's the only way they'll learn anything from it. If you don't make them pay for the actual consequences of a 90 day risk period (e.g. hiring a lot more staff, buying more expensive products that don't need intervention) then of course they're going to keep increasing this magic "It's not my fault" period and you'll pay the price in your sanity.
- EdwardDiego 7y agoWe have a "don't deploy stuff that could go sideways between Dec 1st and Dec 25th" policy because that's when we have the highest a) traffic and b) spend. But the converse of that, is that in Jan/Feb, we can sorta go nuts, because all our customers blew their budget in the lead-up to Xmas. It's really a case of knowing your business and customers.
- azernik 7y agoI have a similar situation with similar timing, and have found it's a good time to get people going on long-running projects. They're not going to be deploying anything to production within a month anyway, so it doesn't block them.