The UK's The Times newspaper (28th September 2015) in an article on the VW emissions scandal, states: “Matthias Müller, the new VW chief, has made hunting down those directly responsible his priority.” It goes on to say about two senior executives ‘relieved of their posts’: “Both deny commissioning the controversial software or knowing about it.”
Matthias Müller’s search for the guilty will not be helped by the fact that the use of this software appears to have been going on for some time. It is also being reported that “Volkswagen was reportedly warned about rigging emissions tests on its vehicles” in 2007 and 2011.
It will, of course, be interesting to see what happens. Can VW survive? What will it cost them?
But, I hear you ask, what does this have to do with document review?
Well, the answer is that Matthias Müller’s search for the guilty would be helped if there is a comprehensive audit trail for all the reviews of documents associated with the software. We do not know whether this comprehensive audit trail exists, but I doubt it. I expect that there's a whole bunch of long forgotten emails which contain the data. Even now, I suspect, management within VW are searching their personal email databases preparing their ‘Pearl Harbor files’.
However, what I do know is that somewhere there will be specifications for the software (Functional, Design, Test, etc.) and some other documents associated with the process, and that these documents will have been reviewed. There may well be minutes of product management meetings. Also, the software itself would have been peer reviewed. There would also, presumably, be some form of output documentation (user manual, technical release notes, etc.) associated with the software. We do not know how the review of these documents took place, but we do know that it did. No one delivers a bit of software which is going into production in, reportedly, 11 million cars without detailed specifications, design, testing and the review of all those items.
Currently The Times is suggesting that Bosch, a VW subcontractor, provided the software. It matters not. What would help the new management at VW is a clear audit trail of all decisions. In this, the review process is critical as it’s where a lot of far reaching suggestions and decisions are made.
Maybe, and I stress I have no knowledge of this and am purely suggesting a plausible scenario, an innocent comment in a review of a discussion document on how to meet the emission level tests sparked the whole process. Who knows? However, an audit trail of the reviews would certainly help in the process of uncovering the truth.
PleaseReview provides an audit trail, tracking every comment and change including who made it and when. It also captures the reasons for accepting and rejecting changes, as well as who did so and supports advanced comment and change categorization. All the information I bet the new VW management team wished it had to hand!
An increasing number of companies are using PleaseReview in association with the software and other product development life cycle as it supports review of associated documentation including, in fact, the software itself.
With the increasing need for compliance and transparency, the availability of comprehensive audit trails are an important side benefit to the real savings obtained by using PleaseReview. As, perhaps, the sorry case of VW illustrates.
So, I leave you with our current review cartoon ………