SR's Blog

JIRA basic 6 steps 1. Create a project 2. Select a template - scrum - used for sprint wise task - kanban - track the Epics status release wise 3. Setup board 4. Create issues - will go in backlogs - Initiative - are collections of epics that drive toward a common goal. - Epic - an “epic” is a large body of work that can be broken down into smaller Stories and not completed in a sprint. - Story - Stories further divided into tasks, QA, Spike. Stories are distributed in multiple sprints - Task - Digging down the story in small tasks. All tasks in a story sould be completed in a sprint. Many subtasks can be created under tasks - Bug - Defect reporting - QA - QA tasks - Automation code for E2E test. Completed in a sprint - Spike - To take knowledge - Investigation - Troubleshooting 5. Invite your team 6. Setup my workflow - To Do - In Progress - In Testing - In Review - Done Reports - Burndown chart - Sprint report

Q: What's your current role and responsibilies? I have played a offshore team lead role when we had the seperate QA board. I managed a team of 4 people. My roles and resonsibilities were to co-ordinate with onsite team lead to discuss the PI objectives and communicate the team so that they can ramp up with the knowledge of new features and fixes. I do participate in each sprint planning to estimate the tasks and define story points according to the velocity of resources and discussion on the scope of testing. Now I do assign the tasks within the team accordingly. Also, I come up with a plan and helping the team if we are lacking to achieve the target. In case still we are lacking to complete the task, I co-ordinate the onsite team lead who further update to srrum master. Also, I try to rotate the features among the team members to avoid any dependency of a resource. I do arrange the KT sessions once we have lien time. Now, we all are moved to a common board so I am working as ...