Testing Process in a software Development life cycle environment

We have the below Testing process in the SDLC enviroment in each organisation which is in Software Development business.

Test Plan : Writing Test Plan for the project and define Scope of test, 
    Modules to be tested, Not in scope items,Phases of the project, 
    Milestones of the project. Resources to work on the project. Effort Esitmation, testing                types to be perfomed during projects,Entry and Exit criteria. Risk and mitigation plan

Test case Design : Designing the test cases based on the FRD

Test case Review : Review Test Cases and provide feedback to update/add/delete if required

Business Review  : Send the test cases to Business for review and sign off

QA Environment   : Prepare the QA Enviroment separately from the Dev env , Builds to be deployed to QA environment

Test data  : Prepare/get the test data to be used for testing, Send emails to Developers/business for the test data requirement

Sanity testing   : Sanity/Smoke Testing of the application once the Build is deployed and identify Bugs before testing starts.
   Logging the Critical/Show stopper Defects of the application before functional testing starts

Traceability Matrix: Prepare a Traceability Matrix in Excel sheet and tag with requirements
Update this while test execution phase.

Test Execution    : Execution of the already designed test cases 

Defects     : Logging Defects in JIRA and assign them to Developers with screenshots

Fixing the Defects  : Push Developers to fix the defects and QA to retest them

Re-Testing : Retesting the defects and close them if fixed

Daily QA Status Report  : Publish a daily status report to all the project stake holders

Security Testing scope and execution : Identify the scope of security Testing in each project , identify the test areas, Perfom the security test in parellel to functional testing

Security testing sign off : QA team lead to ensure the sign off has been provided before the UAT

SIT Testing Sign Off   : Sign off testing by closing all the Critical/High/low defects

UAT Test Design   : UAT test cases to be designed by Business  

UAT Test Execution   : UAT  to be perfomed by the Business and report defects if any

UAT Sign Off   : UAT Sign off to be provided by Business Users/Business Team Lead for each project

Deployment-Prod   : Deployment to production Live