Job ID: MNSITE-1419 (99990321)3P
JIRA Admin with add-ons (Confluence/Tempo Timesheets/Planner/Portfolio), Jira Base, Service Desk, Agile, migration, upgrades and training experience
Location: St Paul MN (DPS)
Duration: 3 months
Interview: In-person
Positions: 1 (1/1)
Minimum Qualifications
oThree years of experience working with Jira administration and configuration.
oTwo years of experience specifically configuring and implementing Jira 7.6 or higher.
Desired Skills
oAtlassian Solutions Partner
oExcellent communication skills
oExperience within the last two years configuring Jira Atlassian and third party add-ons including the following:
-Configuring a Jira base instance from the beginning (prefer more than one in the last two years) based on customer needs and requirements.
-Configuring a Jira Service Desk instance through implementation, including multiple workflows and issue types based on customer requirements.
-Configuring Agile related tools and dashboards for use in Jira
-Configuring Jira Atlassian and third party add-ons including: Jira Confluence, Tempo Timesheets, Tempo Planner, and Jira Portfolio.
-Advising for effective migration from retiring tools to the new Jira instance.
-Effectively training on Jira functions for users of varying roles and needs.
-Preparing for and applying Jira upgrades.
Description of Project
Personnel throughout the Minnesota Justice Information Services (MNJIS) area rely on a number of technical software tools to perform their daily job responsibilities efficiently and effectively. The MNJIS Technical Toolset has evolved over many years, and several essential tools are approaching end of life – a few are beyond end of life and/or vendor support. The current tools also do not readily interface with each other, which can cause duplication of effort or loss of continuity as work flows. The older tools become, the more we are at risk of their complete failure; or discovering an inability to accommodate technology updates we need to keep our services running and secure for our customers. Our approach to this situation has been to identify and prioritize the functionalities in our current toolset for replacement. We have made the decision to move to Atlassian’s JIRA as the base for our toolset. We do have an instance of JIRA Core currently in use for one product/application, but do not have personnel in house with the JIRA/Atlassian expertise needed to lead the broader set up and implementation needed for an all MNJIS configuration. We want to bring in consultant(s) or a vendor who has JIRA/Atlassian expertise to work with us on the set up and initial functionality for MNJIS JIRA.
All work must be conducted onsite at 1430 Maryland Avenue, St. Paul, MN 55106.
Deliverable 1 – Jira Service Desk: Set up to Proof of Concept
•Requirements gathering and design for Service Desk Ticket intake.
•Configure Jira Service Desk, Confluence, and whatever additional Jira core or other add-ons are required for Jira Service Desk to function based on requirements.
oIdentify ticket/issue types needed (i.e.) Questions, issues, problems, account management (person and agency based), work requests, technical requests. Starting with at least 20 request and 20 issues types and supporting data as needed.
oDefine and build processes, work flows, etc. as needed. Starting with at least 10 workflows and supporting data as needed.
oConfluence categories and relationships set up. Starting with at least 10 spaces and 10 child pages per space.
•Recommend interfaces for BCA data with Jira and Jira Service Desk (i.e. User identification information.)
•Make recommendations for transfer of any Service Desk Express (SDE) to Jira. Data migration will be done by MNJIS personnel.
•Make recommendations for information transfers from Knowledge Base to be Confluence.
•Document Jira item parameters, MNJIS hierarchy levels, and any other identifiers for triage, support, search, and work request ticket required fields.
•Review and define data needs for next steps for tickets referred to other areas for resolution.
•Define and identify key metrics for related performance tracking and reporting.
•Complete initial training with Service Desk personnel in preparation for POC testing and the Pilot.
•Complete proof of concept testing with Service Desk.
Deliverable 2 – Jira Service Desk Pilot to Production –
•Pilot completed for MNJIS Service Desk intake and triage processes using Jira Service Desk, Confluence, and related elements; and production turnover of these processes.
•Define/identify key metrics for related performance tracking, dashboards and reporting on Service Desk tickets.
•Requirements gathered and processes defined to resolve tickets delegated by the Service Desk to other areas of the BCA and/or MNJIS.
•Data needs and workflows defined for next steps for tickets to be passed to other MNJIS areas for resolution. (How do we go from issue reported to initial review complete and it triggers a new work item for a future release?)
•Training and proof of concept testing with Desktop Support or other POC areas.
•POC/ small group pilot for resolution of tickets passed to them by the Service Desk for resolution.
•Production implementation of processes for other MNJIS areas to respond and resolve tickets from the Service Desk.
•Training for supporting personnel and management on processes to respond and resolve tickets.
•Change management ticket/information workflow and reports established and implemented in Jira.
Deliverable 3 – Jira Core with Agile Tools Set Up, POC to Production
•Requirements gathering and design of Jira item parameters and set up for Focus Teams’ work to transition out of RTC and into Jira.
•Define and set up hierarchy levels and identifiers for development / support / work request ticket required fields. (Issues, problems, work requests, epics, stories, journeys, testing, application/product, product family/suite, relationship to source code, etc.)
•Set up Agile related views/dashboards including Kanban boards and scrum tools. Backlogs with priority, release plans, sprint plans, burndown charts, etc.
•Advise on transfer of any Rational Team Concert (RTC) data needed by Jira, and Jira migration planning.
•Conduct a POC test with a subset of Focus Team members on setting up and doing planned work in Jira. Move this functionality to production.
•Training for identified teams on Jira Core and Jira Agile. (Including set up of team and individual dashboards/home pages).
•Review set up and advise on handling of Jira updates/upgrades.
Deliverable 4 – Tempo Timesheets
•Requirements gathering and design for Tempo Timesheets set up.
•Time tracking processes and work flows defined and installed.
•Approval and review processes and parameters defined.
•Incorporate settings to assist in implementation of Tempo Planner as needed.
•Limited resource pilot prior to production implementation.
•Dashboards/ initial reporting set up based on identified parameters.
•Training on Tempo Timesheets – several levels of users. Training on modifying dashboards/reporting (as functionality is available).
•Tempo Timesheets implemented for resource time tracking and reporting. (This may go out to MNJIS personnel in stages. First 20% of staff implemented for deliverable completion.)
Deliverable 5 – Internal Jira Service Desk Interface
•Requirements gathering and design for Service Desk Ticket intake.
•Configure Jira Service Desk, Confluence, and whatever additional Jira core or other add-ons are required for Jira Service Desk to function based on requirements.
•Gather requirements and design internal BCA interface for our Jira Service Desk instance.
•Configure and pilot an interface / ability for MNJIS and other BCA internal areas to self-enter tickets.
•Updates and/or additions to Confluence as needed to support this interface.
•Pilot completed and production turnover of interface for internal personnel to enter tickets to be triaged by the Service Desk.
Deliverable 6 – Tempo Planner
•Requirements gathering and design for Tempo Planner set up.
•Incorporate settings to interface with Tempo Timesheets as needed.
•Define and implement processes for use of tool.
•Limited resource pilot/POC prior to production implementation.
•Dashboards/ initial reporting set up based on identified parameters.
•Training on Tempo Planner – may need to start at a lower level as this functionality is new to us.
•Tempo Planner implemented for resource planning and reporting.
Deliverable 7 – Jira Portfolio
•Requirements gathering and design for Jira Portfolio set up.
•Incorporate settings to interface with Tempo Timesheets and/or Planner as needed.
•Limited resource pilot/POC prior to production implementation.
•Dashboards/ initial reporting / plan visuals set up based on identified parameters.
•Training on Jira Portfolio – functionality via tool is new to us.
•Jira Portfolio implemented for product/portfolio planning, management and forecasting.
Deliverable 8 – External Jira Service Desk Interface
•Requirements gathering and design for Jira Service Desk Ticket external interface (at a high level).
•Initial high level configuration for a Jira Service Desk external facing interface (at a high level).
•Updates and/or additions to Confluence as needed to support this interface.