CICD:

The criteria are

- PM follow
commitments between
Process_CICD to assess
customer and project
solution to apply CICD
team, normally written in
on EZ Service and
Proposal or Customer’s
transferred to project
mail. Acceptance criteria
members. If project does
are transferred into
Program: Product Quality Gate Review not for apply CICD process,
Development Project
corresponding product
Project Name: PET.COP.D2M.2023 PM
Completed
Project get confirmation
Key: products and at PETCOPD2M2023
template, convention,
approval
the of
gate-checking Authorized week
product review checklist,
Person
meet
- the
Review onstrategy
EZ Service
defined (group
Template: None test
Status: case, test viewpoint,
-review,
acceptance Test
CICD strategy
environment
peercriteria. (test type:
review, set Approved
Created By: Linh Nguyen Phan Thuy UT/IT/ST, and transfer
Updated By:test to member Nhung Bui Thi Hong
technique,
up
For
leader and
scrumconfigured
review...)projects, is user
PICs.
test Clear
tool...) information
is defined
Created Date: 27/Feb/24 Updated
following
stories
defined
who accept
Date:
atinCICD
leastthenext
Project Planinor 27/Feb/24
Project
Assessment
sprint
Quality Plan
are
Plan metor and Quality
definition
project/deliverables
Plan from
ID Are products
Checked acceptance
Item Resolution.
-of
The ready.
project
Review needs is
checklist
Guideline to Product Priority Use Note
customer Project side.
prepares the
criteria
Do clearly defined
the completed -describe
customizedInput source
theby code
defect
Team
01 infrastructure as DOC,SC Mandatory Yes
and review
Are committed
products meet to
the
activities committed
Ex:
management
lead Acceptance
base to CICD
on projectcriteria
mechanism
02 Ex:
specified Acceptancein the criteria DOC,SC Mandatory Yes
customers?
acceptance criteria environment
of and CICD
03
correctly
Are test
source implemented
activities
code as andof the
commitment
project:
system
characteristic/common
project are: for
to
each
customer
type
DOC,SC Mandatory Yes
defined? bugs
- All of that
Design input
defect source
rate
04
defined
correctly
Are inimplemented
project review
the quality
scanning activities -of
suchas defects comment
user
(Test/Production stories in
have the found
have SC Mandatory Yes
Are defects
strategy?
defined found by code
2defects/1page
Project are
by FPT/Customer. Plan ignored before
as CICDinand
assessment project
OSStest of detail
activities
Environment acceptance )Design criteria
05 FPT/Customer
Are there any
strategy
the review/test
performed as planreview -'Assess
starting
- All Fixed
FPT some
coding
all
review:
Thecontent
sprint defects
of
has
related
review
beenthat SC Mandatory Yes
06 recordedininProject
the defect Check
-
quality
found The
comments, all
project
Source metricsthe
code
bygoal, tickets
performs
FPT/Customer.
source by
scanned codeof DOC,SC Mandatory Yes
defects/Q&A/Issues
implemented?
defined checklists
Plan or defined filled definition
management system as related
testing
comparing
by
=> DevOps
QA to
with
checks the full
actual product
stages,
toolchain
out value
if to
and
07 -related
Compare
Quality to the
Plan? product
actual not comments,
value completely/fully.
done test case
of ifUS/sprint DOC,SC Mandatory Yes
find out
technologies there and is any
tools
08 the
withproject
resolved defined?
despite
target/norm missing with
value? passed
-Design
comments,
- Products
planned/norm
Design
CICD
achieves test
are
defect
quality
report
reviewed
rate
value:
defect DOC,SC Mandatory Yes
overdue
as
gate.
rate defined
-comments,
Defect one.
of 2 Rate or
UTnot
defects/1 bug,page IT
-the deadline?
Does the project and approved
2defects/1page by
-bug, Check
Defect ifDistribution
UTdefectscoverage/
analyze the quality when OSS: and fixes
STall
authoritative
-orFixed bug,all
defectsOther that
-foundUTfollow
Test
PM result
Case term
or meets
Density in the
not achieving the target? defect. by not.
stakeholders.
found FPT/Customer
-commitments
Reviewand/or effortor not (if
- Are actions defined and -contract - Customer
Content ofreview: design
applicable)
Guideline_Using
Customer defect. as in
implemented? covers all functions
OSS_3rd party
SRS
component to plan for
- Use the customer
con`trolling OSS in
template...
project
- Project maintain the list
of open sources what are
used in product and got
the approval evidence
from customer.
- Source code scanned
and passed Open
Source Scan tool
provided by DevOps.