I work in software, with very, very complex systems that are subject to quite a bit of risk management and process control. The company has a team whose sole purpose is to audit projects and ensure that all development teams deliver the required documents/artifacts, pass through all the milestones in the proper order, etc., before taking a project live.
Recently I was given the task to create a design document, which is required by the official process. In theory the document is written before the development work is performed so that all the programmers are doing the right thing. However, we recently switched to an Agile process which is very light on the documentation. So all the development work has already been completed, based mostly off of tasks stored in our TFS system. The document is being created retroactively just to satisfy the audit. Nobody will ever actually use this document.
Aside from the simple fact that this is busywork, it also seems like it is intended to fool the auditors into thinking we followed a process that we didn't actually follow. I believe the correct remediation would be to go back to the auditing folks and re-negotiate the way the process is defined, but management doesn't want to do that. They just want to write a dummy document to make the problem go away. I was literally told to insert just enough text and diagrams to convince a layman that the document was authentic.
Are there any ethical problems with this approach? Am I committing an unethical act by writing the document at my manager's direction? Should I escalate this over my manager's head?