The document outlines the roles and responsibilities of different groups involved in the software release process. The build/deployment group is responsible for builds and deployments. The peer testing group inspects work products for defects and is the point of contact for external stakeholders. The BVT/sanity testing group verifies builds and performs basic testing before passing to the system testing group. The system testing group tests the full system and signs off on builds moving between stages before production.

1. Dev/Build/Deployment/Testingt A Successful
Project
Release Process
-: Md. Jawed
jawed.ace@gmail.com

2. Responsibility of Various Group
Build/Deployment Group: Responsible for Build and Deployment process.
Peer testing group: A group of Smart testers to work closely along with Developer to inspect
the Software and other works product for defects. This group of Tester would be having
knowledge of Black box as well as White box testing. And Peer testing group will be point
contact for outside world(Stack Holder, Support, testing etc) for bug verification and any kind
of application discussion.
BVT/Sanity Testing Group: This group would be responsible to Perform Verification of Build
deployed of various environment. And after build verification this group would perform Sanity
testing(verify only happy Path) on just deployed Build. And at the end this group will give
signoff to System Testing Group.
System Testing Group: This group of tester will responsible to perform testing on entire
system in the context of a Functional Requirement Specification(s) (FRS) and/or a System
Requirement Specification (SRS). System testing team tests not only the design, but also the
behavior and even the believed expectations of the customer. It is also intended to test up to
and beyond the bounds defined in the software/hardware requirements specification(s). and
This group would be having Authority to sign off or reject any build to move for next step. Until
unless System Testing Group are not satisfied with the Build, the binaries cant be put on
production.

3. Flow Diagram about Involvement of Various Groups
L
o
g
i
c
a
l
F
l
o
w
D
i
a
g
r
a
m

4. Stories/Defects
L
o
g Build Deployment
i
Dev Deployment Server
c Peer
Developer
a Testing
Group Dev1
l Group
F
Build Automation And Deployment
Sign Off to Test Deployment Server
l
go for Dev-
o Q1
Q
w
Sign Off
from BVT/Sanity Q2
N
BVT/Sanity Testing
o Group
t Group Staging Deployment Server
a Sign Off from
t System testing
Group for Dev- System
i Q testing
o Production Deployment Server
Sign Off from Group
n
System testing
s Group for
Staging

5. Questions & Answers