Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
24 views1 page

Sop 3

The document outlines the development and quality assurance process, detailing steps from design and implementation to code review and branch merging. It emphasizes the role of the QA team in validating the product through knowledge transfer, test case development, and issue reporting, culminating in a business sign-off. Finally, a release call is conducted to ensure compliance with regulatory and business standards before deployment.

Uploaded by

Shreya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
24 views1 page

Sop 3

The document outlines the development and quality assurance process, detailing steps from design and implementation to code review and branch merging. It emphasizes the role of the QA team in validating the product through knowledge transfer, test case development, and issue reporting, culminating in a business sign-off. Finally, a release call is conducted to ensure compliance with regulatory and business standards before deployment.

Uploaded by

Shreya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Steps:

1. Design & Analysis: Developers and leads review requirements, gain the needed
clarity from the Product Team, do an impact analysis and decide on design
approaches—either reusing existing components or creating new functionalities.

2. Implementation: Developers work on their assigned tasks, documenting code


changes and implementation details. Parallelly, QA team prepares the basic test
cases.

3. Code Review: Development leads conduct unit testing and a thorough review to
ensure code quality, performance, and compliance with standards.

4. Branch Merging: Once reviewed, code is merged into the main development branch
and handed off to QA for testing.

E. Quality Assurance (QA) / User Acceptance Testing (UAT)

• Objective: Validate that the developed product meets the documented requirements
and performs as expected.

• Participants: QA team, Development Leads

Steps:

1. Knowledge Transfer (KT): Developers provide QA with an overview of the


implementation and key testing areas.

2. Test Case Development: QA team creates enhanced test scenarios and cases,
covering functional, performance, and security aspects.

3. Testing & Issue Reporting: QA performs testing, logs any defects found, and assigns
them to developers for resolution.

4. Lead Review: QA Lead reviews the test results to confirm completion and readiness
for UAT.

5. Business Sign-off: A report (including test results, videos, and samples) is shared
with the business team for final approval.

F. Release Call

• Objective: This call happens after the deployment branch is finally freezed to ensure
the release complies with regulatory and business standards before deployment.

• Participants: Product Team, Development Leads, QA Lead, Release Management


Team.

Steps:

1. Checklist: Product team verifies that all requirements are met.

You might also like