G UI DEL INE

Q UAL IT Y A SSUR ANCE FO R SCR UM PR O JECT

Code 13e-HD/CL/HDCV/FSOFT

Version 1/1

Effective date 20/Aug/2015

Guideline_Quality Assurance for Scrum Project v1/1

TABLE OF CONTENT

1 INTRODUCTION ........................................................................................................................... 3

1.1 Purpose ......................................................................................................................................... 3

1.2 Application scope .......................................................................................................................... 3

1.3 Related documents ....................................................................................................................... 3

1.4 Definition ....................................................................................................................................... 4

2 CONTENT ..................................................................................................................................... 5

2.1 Role and Responsibility ................................................................................................................ 5

2.2 QA Activities at Organization Level .............................................................................................. 5

2.3 QA Activities at Project Level ........................................................................................................ 6

3 RECORD ..................................................................................................................................... 17

4 APENDIX..................................................................................................................................... 18

13e-HD/CL/HDCV/FSOFT Internal use 2/18

Guideline_Quality Assurance for Scrum Project v1/1

1 INTRODUCTION

1.1 Purpose

The guideline is to help the staff can understand how quality assurance activities are carried
out in Scrum projects.

1.2 Application scope

This guideline is applied for QA who works in Scrum projects at FSOFT.

1.3 Related documents

No Code Name of document

1 16e-QT/PM/HDCV/FSOFT Process_Agile Project Management Based

on Scrum Framework

2 32e-HD/PM/HDCV/FSOFT Guideline _Scrum Based Software Life Cycle

3 CL/STQT/FSOFT FSOFT Quality Process Handbook

4 11e-HD/CL/HDCV/FSOFT Guideline_ Quality Assurance

5 08e-QT/CL/HDCV/FSOFT Process_Prevention

6 04e-QT/CL/HDCV/FSOFT Process_Correction

7 02e-QT/CL/HDCV/FSOFT Process_QA Control

8 03e-QT/CL/HDCV/FSOFT Process_Internal Audit

9 09e-QT/CL/HDCV/FSOFT Process_Organization Process Performance

Management

10 12e-CL/PM/HDCV/FSOFT Checklist_Final Inspection

11 Xxe-BM/PM/HDCV/FSOFT Checklist of Work Product Review

12 07e-CL/PM/HDCV/FSOFT Checklist_Process Compliance Verification

for Scrum project_Multi Team

13 06e-CL/PM/HDCV/FSOFT Checklist_Process Compliance Verification

for Scrum Project_Single Team

13e-HD/CL/HDCV/FSOFT Internal use 3/18

Guideline_Quality Assurance for Scrum Project v1/1

1.4 Definition

Abbreviations Description

SLA Service Level Agreement

SCM Steering Committee Meeting

POD Project Opening Document

PM PM

PP Project Plan

SM Senior Manager

PTL Project Technical Leader

QA Quality Assurance

RADIO Responsibility matrix

SC FSOFT Subsidiary Company

KPI Key Performance Index

CSS Customer Satisfaction Survey

PCV Project Compliance Verification

HR Human Resources

13e-HD/CL/HDCV/FSOFT Internal use 4/18

Guideline_Quality Assurance for Scrum Project v1/1

2 CONTENT

2.1 Role and Responsibility

Role and responsibility of QA at all levels are specified in Job_Fsoft radio for Scrum project/
QA RADIO

Moreover, in Scrum project, project QA is responsible for process quality assurance in

projects. He/she is in charge of monitoring and supporting Project management activities by:

Assisting in defining and following processes, providing any needed process training.
Verifying process compliance against the defined processes.
Independently evaluating project health & project risks and reporting to senior management
on process and quality issues.
Defining & recommending process improvement.

2.2 QA Activities at Organization Level

Refer to section 2.3 - QA Activities at Organization Levels in Guideline_Quality Assurance.

13e-HD/CL/HDCV/FSOFT Internal use 5/18

Guideline_Quality Assurance for Scrum Project v1/1

2.3 QA Activities at Project Level

Figure 1: QA Activities Lifecycle

13e-HD/CL/HDCV/FSOFT Internal use 6/18

Guideline_Quality Assurance for Scrum Project v1/1

2.3.1 QA Activities in Opening sprint

When Project is started, during Opening sprint

Purpose To establish project defined process and quality control plan

Support the project to do planning and perform necessary activities

required in Opening sprint

PIC QA

Input Project information get from Senior Manager, PM/ SCM, service contract,
particularly the commitments with customeretc.

POD

Steps QA Leader collects information of tentative projects, started project from

various source, identifies if projects/activities under QA control or not (QA
control is mandatory activity for software projects/activities that are paid
by customer).

- In case of QA control activity is required, QA Leader allocates

resource to perform QA activities in the projects and appoints
Project QA Lead (Project QA Lead is ultimate responsible for QA
activities in the project, and must be QA ranked 2 upward).

- Once being assigned as project QA, you are to promptly collect

and study as much as possible project information to
understand project requirements, scope of work, project context
and its characteristic, the standards/regulations that are applied
in the project, as well as the lessons, practices, know-how of
previous similar projects

The information could be get from various sources:

Record of project commitments that made to customer (it could

be different names such as contract, proposal, service order,
master agreement, purchase spec, estimation),

Have a talk with PM/ SCM about the project

Study customer supplied inputs, mails exchange between the

project and customer

Study standard/regulations applied on the project

Study historical data from similar, previous projects in process

database, process asset

Project QA Lead develops QA SLA with clear acceptance

13e-HD/CL/HDCV/FSOFT Internal use 7/18

Guideline_Quality Assurance for Scrum Project v1/1

criteria, then get those reviewed with QA Leader, SM, PM/ SCM
and relevant stakeholders, then approved by QA Manager.

- Project QA reminds/ follow ups PM/ SCM to do the followings:

Prepare Opening sprint backlog

Conduct Opening sprint planning meeting

Develop PP by using Scrum_ProjectPlanSample

Send Project plan to related people for review as per FSOFT

RADIO

Define Initial product backlog and Initial release backlog

Conduct Opening sprint review and retrospective meetings

- Project QA Lead establishes project QA plan and customizes QA

templates, checklist for the project based on the approved
project defined process in Project plan (Process Compliance
Verification, Final Inspection and Work Product Review). Then,
get those reviewed with QA Leader, SM, PM/ SCM/ Scrum
master and approved by QA Manager.

- QA Leader provides training to persons who carry out QA

activities on the project.

- Project QA Lead provides guidance/training to the project team

on process related matters as necessary

- Project QA verifies status and result of project planning activities

by using Process Compliance Verification Checklist Sheet
Opening sprint

- Project QA follows up comments from Opening sprint

review/demo meeting and Opening sprint retrospective meeting,
and review comments on planning docs in accordance with
Process_Correction & Process_Prevention.

- Project QA reminds/follows up PM/ SCM to print the Project plan

and get it signed-off after all comments on the document are
closed.

- Project QA performs final inspection for first shippable product

and sprint

- Project QA reminds/follows up PM/ SCM to do sprint report and

review once it done, then send sprint report to all member of
project and related people

Output Opening sprint review checklist

13e-HD/CL/HDCV/FSOFT Internal use 8/18

Guideline_Quality Assurance for Scrum Project v1/1

POD, Project Plan are reviewed and approved

Sprint report is sent

QA SLA, QA Plan is approved

Reference Process_Scrum

Checklist_Process Compliance Verification for Scrum project

Guideline_Review Procedure

Process_QA Control

Process_Prevention

Process_Correction

Note

2.3.2 QA Activities in Construction sprint i

When Construction sprint is started

Purpose Guarantee project process and quality of product and project

PIC QA

Input Project plan

Steps - Project QA reminds/ follows up PM/ SCM to do the followings:

Conduct sprint planning meeting parts I and II as PP defined

Conduct daily meeting as PP defined

Conduct Sprint review meeting and Sprint retrospective meeting

as PP defined

Collect project sprint assets and complete Sprint report/ KPI

report

Update Project plan and send to related people for review/Sign-off

as per FSOFT RADIO

- Project QA verifies status and result of project activities using

Process Compliance Verification Checklist - sheet Sprint1-n

- Project QA follows up defined action from previous sprint

retrospective meeting

- Defining & recommending process improvement

- Project QA performs final inspection for shippable product and

sprint

13e-HD/CL/HDCV/FSOFT Internal use 9/18

Guideline_Quality Assurance for Scrum Project v1/1

- Project QA reminds/follows up PM/ SCM to do sprint report and

review once it done, then send sprint report to all member of
project and related people

- Project QA will be verify and make sure all data are correct, then
send Sprint report/KPI report to QA accounting every Tuesday
the latest file for QA weekly report at FSU level.

Output Updated Project planning review checklist

Updated PP reviewed and approved

Final inspection checklist

Sprint report is sent

Reference Process_Scrum

Checklist_Process Compliance Verification for Scrum project

Guideline_Review Procedure

Process_QA Control

Process_Prevention

Process_Correction

Note

2.3.3 QA Activities in Construction - Ending phase sprint

When End of phase

Purpose To verify necessary activities to close Phase

To verify project records, data before incorporating to Process asset and

Process database

PIC QA

Input Project plan

Steps - Project QA reminds/ follows up PM/ SCM to do the activities which are
not only as a construction sprint, but also others following activities:

Obtain customer acceptance and survey. (If team cannot get CSS
before ending of this specific sprint, Point of phase will be
calculated in the next sprint)

Collect project phase assets and product phase report including

all accumulated KPI for project, and then send to authorized
reviewers as per FSOFT RADIO together with the meeting

13e-HD/CL/HDCV/FSOFT Internal use 10/18

Guideline_Quality Assurance for Scrum Project v1/1

request

Request QA accounting to verify data for last phase to get

allowance and for all project to submit to process assets.

Complete and sign off phase Acceptance Note

Update Project plan and send to related people for review/Sign-off

as per FSOFT RADIO

- Project QA do all activities as one normal construction sprint meeting

and also others activities to close phase:

Calculate customer satisfaction point and project point

Participate Sprint retrospective meeting

Follow up comments in the sprint retrospective meeting to update

PM/ SCM report and project data if any

Use Process Compliance Verification Checklist- Sheet Closing-

to make sure the procedure requirements are satisfied before
project closed

Copy project records to QA server :

o Audit folder

o Post-mortem records (Acceptance note, Post-mortem

report, Post-mortem meeting minutes, Project point
calculation file, and Customer survey, Know -how file if
needed)

Request SC QA Accounting to verify data before closure

Ask PM/ SCM to complete Phase Acceptance note and get it

sign-off when passing all SC QA Accountings comments

Output Phase is closed

Updated Project planning review checklist

Updated PP reviewed and approved

Final inspection checklist

CSS result

Phase report is sent

Phase acceptance note is approved

Project records and data are approved by SC QA Accounting and

archived properly

Reference Process_Scrum

13e-HD/CL/HDCV/FSOFT Internal use 11/18

Guideline_Quality Assurance for Scrum Project v1/1

Checklist_Process Compliance Verification for Scrum project

Guideline_Review Procedure

Process_QA Control

Process_Prevention

Process_Correction

Note For staring new phase, QA must to use new PCV checklist for new
phase. Project phase data need to be refresh to 0 (expected leakage). At
the end of project, project metric will be calculated by average of all
phase metrics

2.3.4 Perform Process Compliance Verification

Refer to the following documents

Process_QA Control.
Checklist_Process Compliance Verification For Scrum Project

2.3.5 Perform Work Product Review

Refer to Guideline_Review Procedure

2.3.6 Perform Final Inspection

When At the end of sprint or as defined in Project QA Plan

Once Shippable products are going to be delivered to customer

Purpose Guarantee the quality and integrity of the components to be released to

customer.

Guarantee the quality and commitment of Sprint.

This activity is mandatory for all releases planned in Project Plan

PIC QA

Or assigned persons

Input Project QA Plan

Products to be released

Sprint scenario

Test report

Sprint acceptance criteria

13e-HD/CL/HDCV/FSOFT Internal use 12/18

Guideline_Quality Assurance for Scrum Project v1/1

Steps - PIC studies customer requirements, project plan, product requirements

and develop specific final inspection checklist for every deliverables:
acceptance criteria, specific checked items

- Once receiving to be final inspected from project, PIC does final

inspection using Final inspection checklist as follow:

Based on the defined acceptance criteria, QA compares PP

Sprint planning, Sprint scenario with products to verify whether
the deliverables items are included in the release, if not, does it
reported in Sprint scenario/Sprint report.

Check if all products to be released are reviewed and approved or

tested, all review comments or defects are closed.

In case delivering is executables, QA decides whether the

delivered products need to be installed on a fresh environment
or not. If yes, project team will perform installation. QA conducts
test the product.

- Log defects detected by final inspection into FI2.0 to track to closure

in accordance with Process_Correction and Process Prevention

- The inspection result is reported to the stakeholders (Senior Manager,

PM/ SCM, inspectors, QA Leader, etc)

- For the big deliverables (not sprintly deliverable), in case the release
does not pass the final inspection:

QA suggests STOP the release or NOT.

If PM/ SCM does not agree with this result, QA will get the
consultancy and decision from QA Leader/QA Manager
depended on project ranking. QA Leader/QA Manager is
responsible for reviewing the result and giving the final decision
STOP the release or NOT.

PM/ SCM can deliver only if there is evidence that customer or

QA Leader/QA Manager agrees for this case.

A penalty point is given for each release without the permission.

Refer to Introduction sheet of Checklist_Final Inspection and Regulations

sheet of Template_Scrum Project Point for more detailed guides.

Output Final inspection report

List of defects detected by final inspection in FI2.0.

Decision on delivering the products

13e-HD/CL/HDCV/FSOFT Internal use 13/18

Guideline_Quality Assurance for Scrum Project v1/1

Reference Checklist_Final Inspection

Guideline_Review Procedure

Process_QA Control

Process_Correction

Process_Prevention

Note There are 2 types of FI in Scrum.

1- Sprintly deliverables: QA only do FI to verify and make sure

Project keep commitment which were committed with customer
at the beginning of sprint

2- Big deliverable: QA will do FI as normal of Fsoft process.

2.3.7 Calculate Project Point

When End of phase

Purpose To measure and report project performance via project point system

PIC Project level: Project QA

Organization level: QA Accounting

Input Project records and data (KPI report)

Steps - Once project phase are closed, project QAs calculate project point
according to the regulations documented in Project Point template and
record on FI or in Project Point template.

- At the end of month, SC QA Accounting verifies project point calculation

of all projects, and ask project QAs to update as necessary and then,
gather the information to put into project point database.

Output Project point database is updated

Reference Template_Project Point for Scrum project

Note KPI report will be done by PM/ SCM every sprint. Project QA will be verify
and make sure all data are correct.

2.3.8 QA Activities in Closing sprint

When Customer accepts our final product;

Receive requests to close projects

Purpose To verify necessary activities to close projects

13e-HD/CL/HDCV/FSOFT Internal use 14/18

Guideline_Quality Assurance for Scrum Project v1/1

To verify project records, data before incorporating to Process asset and

Process database

PIC QA

Input Project records and data

Customer acceptance letter

Steps - Remind/ follow up PM/ SCM to

Support customer to fix defect if any.

Obtain customer acceptance and survey.

Produce post mortem report including all accumulated KPI for

project, and then send to authorized reviewers as per FSOFT
RADIO together with the meeting request

Request QA accounting to verify data for last phase to get

allowance and for all project to submit to process assets.

Collect project assets to be ready for Handovers & Archive.

Complete and sign off Acceptance Note

Handover & Archive project assets

- Confirm PM/ SCM about time to send the survey

- Guide the project in metrics analysis and post-mortem report

preparation

- Calculate customer satisfaction point and project point

- Participate post-mortem meeting

- Follow up comments in the PM meeting to update PM report and

project data if any

- Use Process Compliance Verification Checklist- Sheet closing- to

make sure the procedure requirements are satisfied before project
closed

- Copy project records to QA server :

Audit folder

Post-mortem records (Acceptance note, Post-mortem report,

Post-mortem meeting minutes, Project point calculation file, and
Customer survey, Know -how file if needed)

- Request SC QA Accounting to verify data before closure

- Remind/ follow up PM/ SCM to complete Acceptance note and get it

sign-off when passing all SC QA Accountings comments

13e-HD/CL/HDCV/FSOFT Internal use 15/18

Guideline_Quality Assurance for Scrum Project v1/1

- Change status from On-going to Closed on FI.

Output The projects are closed.

Acceptance note and project mortem report are approved

Project records and data are approved by SC QA Accounting and

archived properly

Reference Guideline_Scrum Based Software Lifecycle

Process_Scrum

Process_QA Control

Checklist_Process Compliance Verification for Scrum project

Note

13e-HD/CL/HDCV/FSOFT Internal use 16/18

Guideline_Quality Assurance for Scrum Project v1/1

3 RECORD

No Name of Records Storage Duration Important Location

Modality (year(s)) Level

1 QA plan and report Soft 3 years High Server Backup-

pqa

2 QA report Soft 3 years High Server Backup-

pqa

3 QA checklist and report Soft 3 years High Server Backup-

pqa

4 Minutes and decisions about Soft 3 years Medium Server Backup-

QA activities pqa

13e-HD/CL/HDCV/FSOFT Internal use 17/18

Guideline_Quality Assurance for Scrum Project v1/1

4 APENDIX

Process_Agile Project Management based on Scrum framework

Guideline_Scrum Based Software Lifecycle

Template_Project Plan for Scrum project

Approver Reviewer Creator

Do Van Khac DMO Tran Khanh Ly

13e-HD/CL/HDCV/FSOFT Internal use 18/18