Page Comparison

Page Summary      ODE Team Program-Wide Support Cadence       Tracking Requests       The Request Process       Email      ODE Team Program-Wide SupportLinks    Task Format  

Summary:  

This page is intended to provide the detailed process and procedures for how the legacy ODE Team will continue to support , going forward starting 01 Jun 2018, the ODE Program and its various Stakeholders.

Requests for support will be handled by the legacy ODE Team on a case-by-case/on-demand basis similar to the Tiered Support structure of a help desk system. All requests for support should be sent to ODE_Support@bah.com which will be sent to the Legacy ODE Team Members. In addition, please CC:  ariel.gold@dot.gov and Kristin.Tufte@dot.govlogged in GitHub Issue Tracker.

Anchor
Cadence Cadence

Cadence: 

The legacy ODE Team will operate in Monthly Sprint Cadences beginning with the first day of the month and ending on the last day of the monthoperates in a 2-week Sprint Cadence. All requests for support will be recorded within Github GitHub & managed/tracked within Jira and each request will be properly aligned to a Sprint.

Anchor
TrackingSupport TrackingSupport

Summary: How to Request Support from the

ODE Team:

During each Sprint (Monthly Cycles), ODE Stakeholders will use Github GitHub to formally request support from the legacy ODE Team. GithubGitHub's auto-notification service will alert the ODE Team to the request. Once the ODE Team receives the notification from GithubGitHub, a Jira ticket (Task) "issue" will be created to manage and track progress of the request as well as notifying/acknowledging receipt of the request to the Requestee Requester. Jira Tasks will use the following simplified format:

appropriate format as specified here:

For each support request from ODE Stakeholders, an initial evaluation will be conducted to understand the nature of the problem, validate the feasibility of request (i.e. can the legacy ODE Team service the request?), and to conduct an initial estimation (in hours) of how long it will take to complete the request. For requests that are valid, feasible (actionable by the ODE Team), and are estimated to require more than two hours of work - approval from the PM & PO will be obtained first, prior to servicing the request.

All actual hours of work will be recorded in Jira and all work accomplished during the Sprint will be summarized in monthly reports.

Anchor
RequestProcess RequestProcess

The Request Process: 

Step 1		ODE Stakeholders Stakeholder creates a support request, for the Legacy ODE Team, in GithubGitHub The Legacy ODE Team is subscribed to GithubGitHub's auto-notification service and will be notified by email of the request Within 6-8 business hours of the Github GitHub request, the Legacy ODE Team will Acknowledge receipt/awareness of the Request within GithubGitHub
Step 2		Upon receiving the Github GitHub notification, the Legacy ODE Team will: Create a corresponding Jira Task associated with the Github GitHub request (using the simplified Task format) Assign the Task to the Proper Legacy ODE Team POC that will service the Task Within 24 48 hours of being assigned the Task, the Legacy ODE Team member assigned to the Task will conduct an initial assessment (maximum 1/2 hour) to determine if the Team can service the request and to determine the level of effort (in hours) If the request can be completed by the Team - an initial estimation (in hours) will recorded If the request cannot be completed by the Team - the Requester will be notified
Step 2A		If the ODE Legacy Team determines it cannot service the request A message will be made within Github GitHub to alert the Requestee Requester or an email will be sent to the RequesteeRequester, providing the explanation and a chance for the Requester to modify the Request The Jira Ticket will be updated: with comments, initial Triage time will be recorded, and the Jira Task will be closed if new information is received from the Requester, modifying the original request details, then either a new Ticket is created or the original Jira ticket will be re-opened
Step 2B		If the ODE Legacy Team determines that it can service the request then an initial estimation of the level of effort to complete the work will be recorded in the Jira Ticket. If the estimated level of effort to complete the work is less than 1-1/2 hours or less, then the work will be completed by the POC within 48 hours. if during the course of servicing the work , the original estimation actual LOE is found to incorrectbe higher than the original estimate, the process flow will revert back to step 2A.
Step 3A	<2hours<=2 hours	If the ODE Team estimates the level of effort to complete the work is less than 1 1/ 2 hours or less (in addition to the maximum 1/2 including the initial triage time) then The work will be completed by the ODE Team within the next 48 hours If, if during the course of servicing the work , the original estimation actual LOE is found to incorrect and the work now requires more than 1 1/2 hours to servicebe higher than the original estimate, then the original estimate will be updated and the PM & PO will be notified for approval to continue working on the Request.
Step 3B	>2hours>2 hours	If the ODE Team estimates that the level of effort to complete the work is greater than 1 1/2 two hours (in addition to the maximum 1/2 including the initial triage time) then The PM & PO will be notified (by email) for approval to continue working on the Request If the request is denied, then a clone of the Jira Task will be added to the ODE Jira Backlog, the Requester will be notified, and the original Jira Task and Github GitHub request will be updated with any relevant information and closed.
Step 4		Upon completing the work, the ODE Team will A notification will be sent to notify the Requester update and close Jira will be updated with the proper documentation, comments , and Actual hours worked, and closedThe Github request will be updated and closed update and close GitHub issue

Anchor
Links Links

Links: 

Anchor
Task Task

Task Format