I feel sorry for all those who have been diligintly working hard on the MAV project for the last 2 years because, many of them could only do so much with as little as they were given..
Unfortunately, because the original "go live" date was pushed back to May, most of the "top dog" mav people are likely in hotwater already. Then when it 100% will half work when it's forced to go live in May, the blame will be placed on the engineers, architechs, and managers who were in charge of shhiitt..
@19j I tried explaining total cost of ownership to my boss once. He got a look on his face like a kindergarten might if you tried to 3explaim nuclear physics to them.
When leaders that are high up don't understand the term "technical debt", I have concerns.
The Standardization Paradox occurs when an enterprise replaces high-value, bespoke legacy systems with off-the-shelf SaaS to achieve the consultant pitched cost consolidation and operational simplicity. the greenfield promise is a unified system, but the reality for complex organizations is a regression, unique competitive advantage, buried in custom code, are discarded in favor of "industry-standard" workflows. To regain lost functionality, companies are then forced to build extensive, fragile layers of middleware and PaaS extensions. Shadow IT booms to retain capabilities lost critical for their operation, This ultimately leads to a higher Total Cost of Ownership, increased vendor lock-in, and a significant reduction in organizational agility (black box) compared to the specialized tools they replaced. popcorn...
Only plus is it has kept people in a job for 2+ years albeit doing meaningless work. Least bit surprised, it's the norm, once again yet another great Dell efficiency initiative #fail
HTML and hot links labeled as AI
@fz Except most of not all the good EMC ppl were smart enough to leave this shithole or were layed off.
should have given the project to the legacy EMC folks, it would have been done on time...just saying.
Question: How is Project Maverick different from any other project / product Dell attempts to deliver?
Short answer: It's not
Dell has proven over and over and over again it simply has no idea how to plan, develop, or execute on delivering large-scale enterprise software solutions or integrations. It has no clue. And worst of all, there is never any accountability for the long string of failures year after year after year. That's the biggest problem. JC will blame those he forced into working on this undefined, poorly-conceived cluster fu-k of a project. He will never be held accountable.
Dell is a joke!
@c7 JC is COO and MD's right hand man. He's worth well over 100m and barks orders from his mansion and has a "do as I say, no as I do" mentality. He knows that mav was forced to be delayed by a quarter and I'm sure he gets "updates" from his directs on how things are going and, I'm positive he's not happy with these updates because i personally know that it's not gonna be anywhere near 100% by May.
Let's put it this way... it's not a good sign when a project - especially one as massive as this - is STILL in dev/testing with less than a month until "go-live." At this point, it should have been ready to go 100%, no questions asked. Testing should have been completed at least a month ago but yet, it's still in DEV. Very few things have even been pushed to Prod devices yet because some major hurdles have now popped up.
But in Dell fashion, it will be pushed out in May simply so it can be said that it was "on-time" and then the poor people who have to use it will suffer, and ultimately be blamed. Thankfully I won't have to use any of this cr-p but many of you will... Sales especially. This is "supposed" to replace DOMS - which is a 25 year running joke because DOMS is fighting for it's life at Dell lol...
The literal "training" for this thing was an absolute joke. Because it's NDA, it was just words on what looked like a PowerPoint that someone's kid put together lol. No screenshots, no videos, no look into WHAT anything will even look like when people are forced to use it. The training su-ked also because Dell has NO idea HOW to train anyone on this, either..
@bm It's not ready because it literally is still in the testing/dev phase and, the reason for that is because the PM's and architechts didn't know wtf they were supposed to do. The problem is that NOBODY knows what they were supposed to do. You ask questions and nobody knows the answer to it.
We are STILL doing mav work and the majority hasn't even been pushed to the prod devices yet lol... it's one issue after another, after another, after another lol. But as it stands now, there is literally zero way it will be 100% functional by May.
So if it's true that Mav has now moved out to Aug to avoid complete embarrassment, where is the accountability with the cluster clowns for bungling this project beyond recognition?
What is it now, the 79th time it's been delayed or pushed back? Good God what a cluster!!
I remember the good old early 2000s when DOMS was about to be imminently replaced. The project went live 15+ years after the original deadline.
@c7 Are you new at Dell? Once enough time and money has been invested into something, they will absolutely launch something that's not working with the hopes of fixing it down the road. They've done it time and time again and this time will be no different.
I do agree with previous posts as well that it all comes down to lack of two fundamentals for any program/project: requirements and scope. You would think they would have learned, but no. Same thing every time.
Mav moved to August. Huge layoffs after that.
so, if this is as a bad as you say it is..which I find hard to believe if this is to go live in May. I'm sure JC knows what is going on, unless he's being deliberately lied to. He must feel it can go live in May somehow. This being delivered in bad shape would seem to be far worse than delaying it again and getting it somewhat right. From what it sounds like, people feel it's going to be a disaster. What gives....who is right...folks in the trenches or on the pedestal.
braaah, I can vibe code my own phoosion version for free.
joking, not joking. dell needs to be investing in Ai, internally, and obviously sandboxed and firewalled from John in order to avoid his ill-conceived gauntlets.
the world changed overnight, SAaS isn't cost effective anymore, we're throwing money at a throwaway solution that was made obsolete almost at the same time as it started. those 5000+ old code bases, and 10000 databases mentioned in biz week that they're throwing away are now... are pure gold, worth money, more than anyone realizes, they have the Dell biz logic is right there, decades of hidden knowledge, all prime for Ai to reverse engineer and map.
What are we really looking at here? A centralized HTML based hub that brings together all of the existing sites and tools we already use into one easy to access location. Haha
@bm The whole concept is fundamentally flawed. Anytime you try to make a "one size fits all" solution you at best end up with something that works well only for those involved in its creation. Everyone else gets a hammer when they really need a sc--wdriver or a torque wrench.
@bm All if the above. The simple truth is Dell does not know how to properly plan or execute a project plan. They'll go off half cocked then realize a mountain of technical requirements they failed to contemplate so they have to back track. In most cases, by then it's too late. So they'll brute force in a hack to address the failed architecture, which then results in millions of bugs and brittle code. Testing is an afterthought.
It's not an issue of changing requirements, it's the fact that the requirements we're never defined or contemplated in the first place. Dell simply does not know how to develop large-scale enterprise software solutions or integrations. It's that simple. And the failure stems from incompetent leaders who have no successful background in software management.
so, why isn't it ready? Is dev not done, requirements shift, testing/integration not done, bug?s.....what's the main reason at this point. I mean, they had to know.
Project Maverick is just another in a long line of failed projects led by incompetent, failed leadership. JC is a clown who has no idea how to successfully execute a project plan. That's common with Dell Engineering - a proven inability to execute time and time again.
Maverik won't be anywhere close to even 50% functional in May. It will be delayed AGAIN with some sacrificial lambs taking the fall, not the real Jacka-ses who are ultimately responsible.
You think it will 50% work? You must be an optimist.
So you think they are going to let go of the small percentage of people who actually know how the system functions and how to administer it? That's cute. Based on what I've heard, those who have not been under NDA are the ones who need to get their resumes in order. That's also just logic and common sense
I hope not... I know quite a few amazing managers and people who were forced into this "project" that do not deserve any heat for it going sour.