Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
QA Release Policy
Transcript of QA Release Policy
To be fam
with the dif
ow the different QA rele
When should a product be released?
“Product is compiled
and can run with as few bugs as possible”
“Product met the minimum
- Program Managers
“Product satisfies the minimum market expectations in a timely manner”
- Product Managers
“Pre-determined acceptable bugs have been reached.”
“By bug triage.”
must undergo testing
for projects under Product Change (PC) and Product Development (PD)
on Project Plan (PPL) and Project Member List (PML) for projects under PD
Uploading of Design Verification Report (DVR) by
- Inclusion of Testing Activities on the schedule
All releases that have been
Severity 1 defects and blocking problems were found
Fixes for required defects to be resolved have side effects
Non-compliance to the standard operating procedures and project collaboration program process and documentation
All releases must be classified depending on their
Weekly monitoring of Testing
Number of test cases
Number of Bugs
- Priority (PM), Severity (QA)
Number of Executed Test Cases
All releases must complete the
PCP process and documentations
Monthly monitoring of the upper management and follow-ups by PCP Champions
PCP summary chart (PCP champions)
must be resolved
and approval by
Test plan creation wi
and DSP ID using Traceability Matrix b
leases must be scanned fo
must be scanned using
ALL virus total
VR for upload
All candidate releases must be archived and made available to
Back-up every after release in:
//acsmanila/Product Information Directory
All activities prior to testing were performed
The product has undergone unit testing and code review
Additional features or functions are expected
The product has undergone UIS Testing and Code Review
The product can be unstable and could crash or suffer data loss
Ends with a "feature freeze", indicating that no more features will be added. At this time it is said to be "feature complete"
Examples: SM Demo
This release is for evaluation purposes
All required features to be supported for the release were verified to be implemented correctly according to specifications
All Severity 1 (Showstopper) and High priority bugs were verified to be completely resolved
All significant non-compliance issues affecting the release were completely resolved
The product was verified to serve its intended purpose
All Alpha criteria was satisfied
All medium priority bugs were verified
to be completely resolved
All reported bugs in the defect database were verified to be completely resolved
No Low and Aesthetic issues found
No pended Change request items
End - Of - Life
to be sold or supported. The product is said to have
, to be
or deemed as
, but user’s loyalty may continue its existence for some time, even long after its platform is obsolete.
All necessary commercialization activities have been completed and the product has been made available to the
either via the web or physical media.
Any change, even a change for the better, is
accompanied by drawbacks and discomforts.