What's an alternative Hertz could have chosen? A phased approach, slowly changing over parts of the customer experience and getting feedback as they went. Start with the simplest transactions, and for users not doing those, just send them to the (still live) old system.
-
Show this thread
-
Hrm, okay, yeah I don't know what to say here. If Accenture built a smartphone-responsive and desktop-responsive site, then wanted hundreds of thousands more dollars for a TABLET-responsive layout, "world class" may not the best label for their capabilities.pic.twitter.com/AydXODm5Ux
11 replies 43 retweets 422 likesShow this thread -
This one I quibble a bit more with. Hertz wanted an extensible design to be used across all its brands. Sure, this is doable, but the best approach here is probably starting with 1 brand, getting it live, then refactoring to make it extensible. (Again, though, never went live.)pic.twitter.com/fNo9a4Yid5
5 replies 4 retweets 111 likesShow this thread -
Two minor comments here: 1. I'm VERY interested to know how the front end code created (a) security and (b) performance problems. cc
@slightlylate 2. "FED code" = the front end. That's a new one for me! (Please do not re-use this phrase, very potentially confusing.)pic.twitter.com/SHg1z5dtuJ
13 replies 7 retweets 158 likesShow this thread -
Ooo, what's "misleading" testing?? Fun fact for Hertz and others. There's a thing called Test Driven Development (TDD) where the tests are written first! You might consider insisting on that, and also looking into Behavior Driven Development (similar, but for capabilities).pic.twitter.com/iL2YiMn0it
12 replies 9 retweets 188 likesShow this thread -
-
Replying to @slightlylate
It appears from the lawsuit that the Accenture codebase was never "deployed" if we're defining that as being available to real end-users. In fact, it looks like the new system, rewritten by a new vendor, is still not yet live.pic.twitter.com/XImTZYMdwk
1 reply 0 retweets 3 likes -
Replying to @allafarce
While I very much think it's possible for frontend code to create security ("frontend" construed broadly) and performance issues (even narrowly), would also caution against taking the analysis of an org that hired Accenture to build a "website" in the Year of Our Lord 2016.
1 reply 0 retweets 9 likes -
Replying to @slightlylate @allafarce
*Perhaps* Hertz had internal experts who were just so busy making internal tools that they couldn't build out a public site revamp; also that $32MM was cheap compared to their rate. *Perhaps* they were consulted only when the failure turned into "real money". *Perhaps*
1 reply 0 retweets 2 likes -
Replying to @slightlylate @allafarce
*Perhaps* Hertz believed that $32MM was _quite enough, thank you_ and that the vendor proposal to purchase additional HW/SW was a bait-and-switch. *Perhaps* Hertz was also short of lawyers, so went with a "gentleman's agreement" regarding scope changes and supplemental charges.
1 reply 0 retweets 2 likes
*Perhaps* Hertz is a competent global technology-acquisition and management organization which you should *totally* give your credit card to. *Perhaps*
-
-
Replying to @slightlylate @allafarce
The hard part of this case for Hertz, ISTM, is the notion that any judge or jury would by sympathetic to any org that knowingly wrote a check to Accenture.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @allafarce
...much less an org that had been knowingly writing checks to Accenture since... <checks "Factual Allegations" section> ...2004
1 reply 0 retweets 4 likes - 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.