Soft audit practice・Preparation 1: Explanation of audit plan
- 1. Introducing the practice of software development audit in detail
- 2. In software development audit, we first explain the audit to the other party.
- 3. Explanation of software development audit and installation of consent of the other party
- 4. Presentation of software development audit plan
- 5. Overview of development audit
- 6. Explain the general work flow on the day of the audit in the itinerary
- 7. If the audit schedule is domestic, it is basically one day
- 8. 2.5 to 3 days when auditing overseas companies
- 9. Even if the foreign language is not good, there is a computer language at the end. .. ..
Introducing the practice of software development audit in detail
Since we have introduced the outline of software development audit in the previous articles, we will introduce the concrete procedure of software development audit from here . There is no right answer because the method of software development audit is a unique method that Gutara’s father calls it in the first place. It is an introduction that my father Gutara did this, so if there is something that seems to be useful, I think that you can use it as a reference when auditing software development contractors.
In software development audit, we first explain the audit to the other party.
Software development audits are roughly divided into three stages: (1) advance preparation by the day, (2) on-site audit work on the day, and (3) utilization of audit results (follow-up). I will introduce them in order, but first of all, I will introduce (1) advance preparations up to the day.
As introduced in the article on Software Development Audit Overview / Method 1, the procedure for software development audit is based on the ISO9001 audit procedure. Therefore, we will proceed with the work in the order of advance preparation, on-site audit, and follow-up after the audit. In this article, we will introduce the contents of preparations to be made by the day of the audit. If you are accustomed to ISO9001 auditing, you can skip this article and proceed to the next article on practice and confirmation points on the day .
Explanation of software development audit and installation of consent of the other party
Software development audits are like those created by Gutara’s father, so there is no activity called software development audits in general . So, first of all, I explain to the other company that software development auditing is done for this purpose, and start by getting the other company to approve the audit.
This area is a bit more work than the methods that are widely known in the world, such as ISO9001 and CMMI. Well, if you ask , " Roughly speaking, it’s a software development version of ISO9001 auditing!" , Most companies will understand that they will be audited. However, the other company has various questions about how many days the audit will take, what kind of things will be confirmed and what are the pass / fail criteria, what will happen if the audit results fail. It is often held.
As introduced in the article on the outline and purpose of software auditing, the purpose of software development auditing can be broadly divided into three categories: selection of contractors, improvement of development capabilities of contractors, and quality confirmation of defect-fixed versions. Therefore, if you explain the outline of the audit according to the purpose of the software development audit at that time, it will be easier for the other company to understand.
Also, even if you explain the software development audit without materials, it is difficult for the other company to understand, so it is also a theory to explain the software development audit while presenting the template of the audit plan as introduced below. It is effective in advancing.
Presentation of software development audit plan
In order to explain the software development audit to the other company and have them understand it, and to prepare for the audit in the other company, first create an audit plan for the software development audit and then write it. It is good to explain how to proceed with the specific audit. In addition, by writing an audit plan, the contents of the audit preparation will be concreted.
So what should you write in the audit plan for software development audits and what should you do to prepare for the audit? Let’s take an example of the audit plan template that Father Gutara has used so far.
Discussion
New Comments
No comments yet. Be the first one!