Notes

BizOps Playbook Quiz -
EBOps_RMA_002 =
3 types of Release Process -
1. Monthly Release - Also called Green Channel Release. The release is planned based on a release calendar. It goes through full feature and regression testing.
2. Adhoc Release - Also called Grey Channel Release. It is an intermediate window for changes to move to production. It goes via approval by 'Release Management Committee'.
3. Emergency Release - Also called Red Channel Release. It is done only for critical bugs and it also goes via approval by 'Release Management Committee'.

Release Management Committee is a six member team coming from different products and departments.

At the beginning of the approval process a code risk alert is assigned by the requestor and then the request is sent to the 'Release Management Committee'
1. Code Red - Force upgrade feature, impacting all accounts
2. Code Orange - Force upgrade feature, impacting many accounts
3. Code Yellow - Force upgrade feature, impacting one account
4. Code Blue - Live extention feature, impacting no account
5. Code Green - New feature, impacting no account

EBOps_RMA_003 =
Release Planning and Execution Steps -
1. Planning - Feature requests, Value based prioritization, Sprint planning.
2. Sprint Artefacts - Product specification doctor, Technical specification document
3. Development - Implementation of Sub-modules for planned features, Unit testing, Feature integration testing
4. Quality Assurance and Testing - LAR, System integration testing
5. Production Push - Deployment of code from SIT to Production

Process Workflow of Dev -
SIT(n-1) week to Release week 1 -
1. Dev starts receiving completed PRS and TDS in week prior to actual sprint start date
2. Dev start working on stories in local environment
3. Over here Dev works on some Bug Fix/Prod fix activities for previous releases
Release week 1 to Release week 2/3 -
1. Dev keeps on executing stories in local environment in week 1
2. Dev does unit testing and pushes code to Dev environment for code review by POD lead/Architect
3. As and when code gets code reviewed it gets pushed to FIT environment for QA team for testing
4. Dev Fixes any bug/defect raised by QA
Release week 2/3 to Release week 4 -
1. Dev keeps on executing remaining stories in local environment in week 2 and 3 ang get is unit tested and code reviews
2. By week 2 and 3 100 % of stories should be completed and should be tested by QA team
3. All the stories should be demoed by end of week v3 by PM, Dev/QA Manager
Release week 4 to Ready for Release -
1. In the Final or SIT week entire code should be pushed from FIT to SIT environment for SIT/LAR regression testing
2. Dev should be ready to fix any application/story bug in this phase
3. Support Prod activity
4. Prepare for stories for next sprint

Process Workflow of QA -
SIT(n-1) week to Release week 1 -
1. Sprint Activities for next release should happen over here.
2. Test plan fir FIT
3. Test plan for SIT
4. Authoring of test cases and linking with story
5. Reviewing the test cases by PMs/POD leads and final approval by QA Manager
Release week 1 to Release week 2/3 -
1. Creation of sub-test execution for stories
2. Creation of Test execution cycle
3. Reviewing the test cases by PMs/POD leads and final approval by QA Manager
4. Authoring of test cases and linking with story
5. Execution of test cases with respect to subtest/test execution and creating defects for failed test and linking them
6. Retesting of failed test cases using different execution cycle
Release week 2/3 to Release week 4 -
1. Execution of test cases with respect to subtest/test execution
2. Creating defects for failed test and linking them
3. Create new/multiple execution cycles for failed test cases until all test cases are passed
Release week 4 to Ready for Release -
1. Execution of regression cases with Test Execution
2. Execution of P0 and P1 test execution cycle having critical/failed scenarios across all stories in the release

EBOps_RMA_004 =
PMs should do planning and deliver the PRS by W-1
Architects/Dev PODs shoulddeliver TDS by W1
Dev and QA should start execution by W1

EBOps_PM_001 =
3-4 use cases of Jira -
Jira asoftware is designed to help teams of all types manage work.
1. Jira for requirements and test case management - For test management, Jira integrates with a variety of add-ons.
2. Jira for agile teams - Jira provides scrum and kanban boards to practice agile methodologies
3. Jira for project management teams - Jira can be configured to fit any type of prokect.
4. Jira for software development teams - Jira provides planning and roadmap tools so teams can manage stakeholders, budgets and feature requirements.

EBOps_PM_003 =
To create a page in confluence, select your space, click on the '+' sign on the left side and select blank or any template and finally click on Create button on the bottom right.
To link with Jira -
1. Select a page in the space that is to be linked.
2. Click on the Edit icon on the top right corner of the page to enter the editing mode.
3. Place the cursor on any of the panels on the page and then click on '+' sign on the top right of the page. Then go to JIRA Issue/Filter option
4. Once the pop-up opens enter the JIRA issue/task id in the box as per instructions
5. Once entered the id click on insert as soon as you press insert button the IRA issue will automatically get linked to the page.
6. Once done click on Publish button on the bottom right.

EBOps_PM_004 =
New Phase, PRS Design phase, TDS design phase, Ready for sprint phase, In development phase, unit testing phase, code review phase, demo in progress, dev completed, QA testing, QA completed, ready for release, descoped.

PRS Design is very important for Product Managers and is also consumed by the Architects and POD leads.
TDS Design is relevant for Architects and POD Leads.
In Development and Unit Testing are consumed by the Developers mainly.
Code Review is relevant to the Architects and POD Leads.
Demo in Progress is important for the PMs and engineering managers.
QA Testing is meant for the QA team
Descoped and On Hold can be consumed by all the roles.

EBOps_PM_005 =
Test Set and Sub Test Execution are XRay Issue Types to successfully execute testing activities in JIRA through X-Ray.
Test Set is a group of test cases used to associate all included Tests with other Xray issue types like Test Execution and Test Plan to provide test coverage and test status. This can be reused any number of times as it is not tied to any release and is independent. Once the test sets are created with repeated test cases, it saves a lot of effort.
Sub test execution can be created for a parent issue like a requirement in order to execute the test cases associated with it.