Solved

Post-implementation testing for Change Management process

Hi all. My current organisation has instituted change management procedures from cradle to grave. As an IT auditor, our team has raised an issue on the lack of documentation for test results (UAT/QAT/SIT and Post-implementation testing), and we are concerned that the lack of documentation may not provide sufficient assurance that the testing has been performed with sufficient rigor.

However, we hear concerns from the IT software development team that our audit recommendation of retaining all test results for each change request, including the provision of post-implementation test results from the end-users or BAs, may cause the process to be less efficient.

Hence, would like to seek the view of all IT professionals out there: is the documentation of test results key to a good Change Management process in an organisation? How much documentation is 'too much'?

Would appreciate it greatly if anyone would be able to share on the best practices in the industry. Cheers :)
2 answers Last reply Best Answer
More about post implementation testing change management process
  1. Best answer
    I believe the levle of documentation/rigor will depend on a number of things. How much automated regression testing is built-into your dev-ops process. How major was the change? A DR fix for a specific problem, is different than a major feature addition. What is the consequence of a latent bug? An airline reservation system probably gets more regression testing for each DR fix than does a preschool game.

    At some point it does come down to do you trust your developers? You are paying them a significant salary to be professionals and to do the necessary testing.
  2. And your company culture becomes important.

    What happens to someone who reports issues as a result of the testing? Or finds errors in the documentation?

    At one time I tested and "failed" some code. Reason: although the code fixed a problem it seriously broke something else and the lead programmer who "never made mistakes" raised H*** about my work.

    Fortunately I had senior management that went to the mat for me.

    Fully agree with kanewolf - everyone must be professional.

    Egos should be put aside and when things go wrong as they will - just fix them. Do not turn it all into the proverbial "blame game". Maybe a post mortem of sorts to reduce reoccurrences, i.e., a "learning experience".
Ask a new question

Read More

Management Business Computing Team