Hard freeze through May
12 replies (most recent on top)
Proof that agile doesn't work. Nothing is getting done any faster than before, and we're having failures that are so bad now that management (including our new "head of technology" who has no technological background) simply doesn't know how to even tell what failed or why.
So in the end, we all pay and WF falls farther and farther behind our peers because we can't roll out anything new when we're frozen with fear half the time and under change freeze the rest of the time.
I wish my manager would at least offer to sit on my face.
"payment and deposit problems last week"
Did it involve wires?
@OP you really need to just let it go, let it go
Malibu Stacy here. What’s with the freeze? Isn’t it springtime? I’m wearing my pride lanyard from the spring collection.
DEI poster child, Leo is the only one who can approve emergency tech changes during the freeze. Yet he’s not to be found. Gonna be some serious application outages next week.
thank goodness for agile
With all the freezes WF have reverted to a quarterly release cycle.
There were some payment and deposit problems last week. The freeze started with some of those systems and now it’s company wide.
details?
Was there another major outage we didn't hear about? I thought it was a sort-of kind of freeze. And apparently there's some new internal site outlining what releases are planned, potential impact, etc. Doesn't mean squat if people aren't testing properly all the way from requirements, test plans, unit test, and actual f'ing acceptance testing.
We are frozen for a few weeks to fix the last several years worth of problems. This will test our location strategy 'collaboration'. I'd be ok with freezing all changes until 2025.