1 / 11

Improved JIRA Process

Improved JIRA Process. Unscheduled Backlog. Connect Team. Outside Contrib. Bugs Feature Requests. Requirement Docs. BA Review. Large Tasks or Features Measured in T-Shirt Sizes. Epic. Epic. User Story. User Story. Collection of common tasks sharing a theme

jaguar
Télécharger la présentation

Improved JIRA Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Improved JIRA Process

  2. Unscheduled Backlog Connect Team Outside Contrib Bugs Feature Requests Requirement Docs BA Review Large Tasks or Features Measured in T-Shirt Sizes Epic Epic User Story User Story Collection of common tasks sharing a theme blocked to fit into a sprint Task Task Subtasks Dev Task Dev Task QA Task Doc Task

  3. Change in Process Before Now All mine Task Task Sub Task Sub Task Sub Task Sub Task Sub Task Sub Task

  4. Work Types Development Task QA Task Document Task Infrastructure Task Research Task

  5. Issue Creation Checklist for Tasks/Bugs Give it a brief / descriptive summary Assign it a work type, priority, . Give it a fixed and affects version. Fill out the description with the template considering all work and completion criteria. EXAMPLE: Gateway 1001 Summary: Update JIRA to include work types Description: Development: Add JIRA work type pull down to create tickets and make it a mandatory option. Include the following work types … QA: Create sample ticket with work type. Infrastructure: Allow assignee access to JIRA admin. Documentation: Update wiki for JIRA process. Research: n/a CC: Mandatory work type option added to JIRA task/subtask issues, can create and alter this value on tickets.

  6. Issue Creation Checklist for Tasks/Bugs 5. Assign the ticket a point value. Process for pointing tickets mid sprint: 5? 3 5 points Skype, Phone, Face to face Account for Our Work! 5

  7. Issue Development Checklist for Tasks/Bugs • Assign ticket to yourself. • Review the description creating subtasks and linked tasks where needed. • If separate work type tickets are created, ensure that they are appropriately • assigned. Estimate and enter work log (keep in mind all subtasks will log work to the main task).

  8. Link QA Large Task: New Test Suite Alteration of CI Task New QA Task Add Comment To Task Medium Task: Alter Existing Tests Deep Dive into Logs Multi-step Verification Small Task: Run CI Confirm Results Run Existing Test QA SubTask

  9. Link Doc Large Task: New Multi-page Doc Requires extensive edit Task New Doc Task Add Comment To Task Medium Task: Addition to Doc Requires brief edit Create new wiki Small Task: Wiki Edit Small Installation change Doc SubTask

  10. Issue Closing Checklist for Tasks/Bugs Ensure that all created subtasks have been closed including QA and any other outside work types. Check that the CC and all work has been completed from the description. Make sure all work has been logged on the main task. Zero out the time remaining log. Double check that the task was pointed. If there is an affected version that did not get worked on as a part of this task, make sure that a ticket is created to encompass this work and link it to the task. Resolve and close the issue.

  11. Suggested JIRA plugin Create and Link https://studio.plugins.atlassian.com/wiki/display/JCLP/JIRA+Create+and+Link+Plugin

More Related