CMMI评审（四）

质量管理相关问题

CMMI （Capability Maturity Model Integration For Software，软件能力成熟度模型集成）是在CMM（Capability Maturity Model For Software，软件能力成熟度模型）的基础上发展而来的。CMMI是由美国卡耐基梅隆大学软件工程研究所（Software Engineering Institute，SEI）组织全世界的软件过程改进和软件开发管理方面的专家历时四年而开发出来的，并在全世界推广实施的一种软件能力成熟度评估标准，主要用于指导软件开发过程的改进和进行软件开发能力的评估。

1.如何制定QA计划？. How to make QA plan?

遵循组织已定义的标准过程文件和规程模板，根据项目的总体计划制定项目的质量保证计划,定期对项目的过程活动和相关产出进行符合度检查。
在里程碑点所做的检查更加详细；
每个产品的正式评审之前，QA要做产品检查，评审时，QA要做过程检查。
对检查时发现的问题进行记录，知会相关责任人和项目经理，提出整改意见；
定期出具质量报告，通报给项目的相关利益者。
Follow the document and procedure module of organization defined standard process, as project overall plan to make project QA plan, and check regularly about the project process activities and products comformity.
do more details check in milestone;
every products, before formal review, QA check product.
QA implement process review in review"

2.QA人员如何对过程和产品进行检查？ How QA check process and product?

QA进行检查的工作方式主要有三种：
（1）查。检查相应的工作产品，评估其格式符合度、内容符合度；
（2）问。访谈相关人员的过程执行情况，评估其过程定义的理解程度、过程活动的符合度；
（3）看。旁观或参与项目活动，评估其过程符合度、产品符合度。
QA checking work include three ways:

1. check. Check work product, evalutae format and content;
2. ask. Interview relative performance, evaluate the understanding of process definition, and process activities to meet process.
3. look. look at or participate in project activities, evaluate process conformity and product comformity"

3.对于在检查过程中发现的问题，如何处理？ How to solve any problems in checking process?

QA通过对工作产品与过程符合度的检查,发现存在的问题并且记录在《问题跟踪表》，然后通知相关责任人并且提出整改意见；QA需要持续跟进已发现的问题，直至该问题被解决。
QA定期通过《问题跟踪表》和《质量报告》与项目经理进行正式沟通。
QA check the comformity of work product and process , find problem and record in problem tracking list, and then notice responsibility and give improvement suggestion;
QA need to monitor problem till the problem is solved.
QA communicate regularly with project manager by problem tracking list and QA report.

**4.当检查发现的问题存在争议时，如何处理？**How to handle with any discussion about the finding?
当QA和项目组成员就问题存在争议时，通过与项目经理沟通来解决；
当与项目经理无法对问题取得一致意见，或者问题级别为高的时候,QA将问题上报高管,由高管来裁决问题的处理方式。
If there any debate between QA and project team members, solved by communicaation with project manager;
if cannot come to an agreement with project manager about the issue, or a higher issue, QA can report to senior manager to decide the solution.

5.QA主要的工作文档及其作用？ What is the main working document for QA and the function of thses document?
（1）《QA检查单》，根据组织过程文档和质保计划制定，用于规范QA活动；
（2）《问题跟踪表》，日常检查填写，用于汇总和跟踪存在的问题；
（3）《QA周报》，每周填写，用于记录和汇总QA活动和结果；
（4）《QA工作报告》，里程碑点或阶段性编制，用于报告项目的质量状况，供利益相关者和高管评估项目质量。
(1) the QA checklist is developed according to the organization process, documentation, and QA plan to regulate QA activities;
(2) ““problem tracking list””, filled in the daily inspection, and condolidate and track the existing problems;
(3) QA weekly report, will be filled in, to record and consolidateQA activities and results;
(4) QA work report, milestone or stage preparation, for reporting project quality condition to relatives and senior manager yo review."

6.QA相关工作文件是如何进行管理? How to manage QA working document?

纳入配置库进行管理 add into configuration library to manage

7.QA检查的活动有没有规划？有哪些内容？ Is there any plan about QA checking activities? Any contents?

有，在《QA质量保证计划》及《WBS》中有反映。
规划的内容包括过程和产品评审的时机、频率、检查方式、检查依据、汇报方式、汇报对象等，其中汇报对象主要是明确高管或项目上层经理的参与。
Yes. Wbs reflected in QA plan, which include process and prodct review about the timing, rate, checking way, checking evidence, report way, who to report,etc, and define senior manager and project manager participation"

8.《QA质量保证计划》里，除了规划，还有哪些内容？ In QA plan, besides planning, is thre any other content?

定义QA的职责，指定QA人员；
明确QA活动的资源需求；
提出对QA的专业要求，确定是否需要培训
define QA responsibility,
appoint QA people.
Define resource requirement for QA activities"

9.QA活动除了QA外还有哪些人参与，如何发挥作用？

In QA activities, besides QA, is there any participants, how it works? "
（1）项目经理、项目成员、项目评审人员。参加评审活动，或者被检查、被访谈；
（2）项目上层经理、高管、第三方QA。接受QA的工作报告，检查QA的工作。
project manager, project team members, project review people. Participate in review activities, or checked , interviewee"

10.请描述在项目生命周期的各个过程，QA分别做了哪些审计？ Please describe every process in project lifecycle, what audit that QA will do ? "
（1）立项过程的审计。项目立项审请,立项评审的执行情况,项目公告发布情况；

1. audit establishment process. in project planning application, review the performance. publish the condition
   （2）策划过程的审计。根据项目的特征检查PDP，PDP的受控情况，工作任务的分解，项目的估算，项目的策划，支持计划，测试计划,计划的评审等；
   2.audit planning process. according to project features to check PDP, PDF, about the controling condition, wbs, project estimate, planning, support plan, testing plan, review,etc.
   （3）监控过程的审计。项目的周报是否定期提交,发现的问题是否纳入问题跟踪表中,里程碑的跟踪,里程碑的评审,评审是否符合相关规程,评审是否产出相关的报告，是否识别了风险,对风险是否采取了规避措施；
   3.audit PMC. project weekly report handed in regularly? any found problem recorded in problem tracking list? track milestone, review milestone, ensure review to meet specification. any report from review? has recognized risk? has any mitigation measure toward risk?
   （4）需求开发和管理过程的审计。需求的分析与定义，需求的确认，需求的跟踪、需求的变更；
2. audit requirement development and management process. requirement analysis and definition, requirement validation, requirement tracking, requirement change.
   （5）设计与编码过程的审计。主要包括概要设计、详细设计、单元测试等文档的审计活动；
3. audit design and coding process. include high-level design, low-level design, unit testing, relative audit activities.
   （6）产品集成与测试过程的审计。主要包括测试准备、测试用例、产品集成计划、测试环境、缺陷管理等审计；
4. product integration and testing process audit. include testing preparation, testing use case, PI plan, testing environment, defect management.
   （7）配置管理过程的审计。配置库的建立状况，配置项的的标识，基线管理，配置项状态跟踪，配置审计活动，产品发布管理，变更管理；
   7.CM process audit. configuration library establishment, configuration item recognization, baseline management, configuration item condition tracking, configuration audit activities, product publishment management, change management.
   （8）结项过程的审计。结项的申请，结项的移交等；
   8.audit conclusion. conclusion application, transfering,etc.
   （9）培训过程的审计。培训的准备活动，培训的执行过程，培训的总结，培训的效果等。
5. audit training process. training preparation, performance, conclusion, effect,etc."

11.对于公司的工作流程，有没有发现需要改进的？如何处理?

About company process, is there any requirement for improvement? How to handle?

自编故事 you can write own story ~ 。 。~