Classic patterns in disputed IT project: Hertz v. Accenture
Just ran across this article at the always-irreverent-but-usually-spot-on Register, an IT news site out of England. The standard patterns of a troubled IT project are so evident in this one report that I may well use it as a case study for my CS 428 (“Real-world software engineering”) class this fall. Here are some of the classic tropes that I teach in my class:
- multiple missed deadlines
- failure to produce a functioning system
- unreasonably limited architecture and design
- failure to design for extensibility and maintenance
- poor quality assurance
- adoption of new technology in the middle of the project
- lack of proper security implementation and design
As the saying goes, read the whole thing.
https://www.theregister.co.uk/2019/04/23/hertz_accenture_lawsuit/
About the Author: admin
![The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]](http://bfwa.com/wp-content/uploads/2018/01/intel-cpu-150x150.jpg "The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]")