Embed Size (px)
Citation preview
HRMS Plan for 2017
2017 HRMS and Applicant Tracking
Objectives, Goals, and Activities
Raleigh, North Carolina
February 3, 2017 1
Agenda
• Overview
• 2017 focus from HRMS and SchoolJobs
• Review of activities by role
– Project Management
– Business Analysis
– Development
– Testing
– Training
– Support
2
Overview
• In 2017, management of the HRMS team will began anew due to
personnel changes and the winding down of a challenging period with
the PeopleAdmin ATS.
• In 2017, the HRMS team should be able to focus on multiple issues
that have been delayed due to higher priority activities and significant
team level distractions.
• In order to take advantage of and optimize the business benefit
delivered by our HRMS team’s increased bandwidth, direction is
being put in place to guide HRMS team activities throughout the 2017
calendar year.
3
Focus for 2017
• Throughout 2016, while some updates were made to HRMS, the
primary objective was to provide mission critical support.
• In 2017 we will change and focus more on incremental
enhancements, browser compatibility, and a review/rewrite of our
“two technologies” reporting function.
• An updated CEU API should help with current deficiencies in CEU
information updates .
• Additionally, the existing HRMS test environment and methods will
be reviewed and updated where needed based on direction from
the HRMS team, and input from our test partners.
• Finally, we will “complete” the ATS rollout. While other LEAs will no
doubt elect to join the State ATS solution in the future, they will be
managed on an one off basis.
4
In scope HRMS activities for 2017
include:
• Release updates to HRMS that focus on high priority enhancements
• HRMS browser compatibility for Edge and Chrome
• Development of a new API to support CEU Vendors using UID (under
review)
• Enhanced reporting to include a potential rewrite of the “Reporting Tool”
• Identify/review the HRMS test environment, test methods, and update them
as required
• Update HRMS training materials
• Provide HRMS support to meet our customer’s needs – mature Remedy
approaches/communication of significant issues to leadership
• Help with AS400 to SAS move
• Plan to sunset NC School Jobs (under review)
5
In scope Applicant Tracking activities
for 2017
• Complete and test final enhancements
• Roll out to all LEAs desiring to opt-in
• Work with large LEAs to help encourage opt-in
• Roll out to Charters
• Refine and implement ATS marketing approach
• Continue to coordinate support for Social Media adoption
• Use Tableau for ATS reporting
• Provide ATS support to meet our customer’s needs
• Work with PeopleAdmin to include functions rolled out to their
base SAAS that are not part of the NC solution
6
Project Management
• Provide direction, leadership, and management for all HRMS and ATS
activities
• Drive ATS adoption by LEAs; special focus on large LEAs
• Coordinate and manage ATS maturation – bugs, new features,
reporting
• Lead the development and implementation of the ATS marketing plan
• Coordinate overall ATS rollout to LEAs and Charters
• Support linkages between Business Analysis, Testing, and Training
• Work with PMO to define test requirements for SAAS solutions
• Work with test partners to continue (or replace) test methods started
by Alice Roebuck (former HRMS tester)
• Support Social Media maturation activities within the LEAs
• Support School Business Systems Modernization support
7
Business Analysis
• Standard analysis required for support activities
• Management of the enhancements backlog
• Work in support of the ATS rollout (various analysis on an as
required basis)
• Standard analysis required for enhancements and new functions
(including 6.5.3)
• Requirements for new reports
• Requirements to support Reporting Tool updates/rewrite (if
undertaken)
• Develop appropriate E-Verify and IAMS function definition
• Support required linkages with testing and training
8
Development
• Ensure ATS interfaces are working and updated as required
• Ensure ATS reports are provided as required
• Code fixes as required to support browser compatibility test findings
• Code updates to HRMS function
• Update NC SchoolJobs as required
• Identify/update software and hardware environment and identify any
hardware or source code issues
• Make sure all source code is backed up in a way to benefit from
“Enterprise Back-up” schemes and protocols
• Recommend reporting updates for the entire ATS and HRMS reporting
function
• Implement approved updates to the reporting function
• Work with the test function after requirements are provided to identify
test cases
• Work with Support to resolve technical challenges
9
Testing
• Provide end to end test of ATS in preparation for migration to support
• Ensure JIRA is updated to include DPI test guidelines and DPI best
practices
• Identify test artifacts from Alice Roebuck and provide assessment of the “as
is” state of the current HRMS test methods
• Continue to provide testing support for the ATS as it goes into support
• Continue to provide testing support for HRMS
• Provide test support to identify defects associated with various browsers
such as Firefox, Edge and Chrome
• Work with BA and development as requirements and design are formulated
in order to define test cases prior to/or as development begins
• Work with training as they leverage test cases to help support training
approaches and training material development
10
Training
• Continue to update ATS training artifacts
• Continue to mature ATS training approaches
• Schedule training sessions on an as required basis
• Work in support of the ATS rollout (various activities to be defined as
needed)
• Collaborate as a training/support team to make sure that all team
members are level set regarding training and support direction and
discrete issues
• Leverage Gordon Millspaugh for HRMS team training on “as is” HRMS
functions
• Review HRMS training approach and update as required
• Review HRMS training materials and update as required
• Keep the HRMS and ATS Wiki updated as required
• Serve as a key source of communication to the LEAs
11
Support
• Support all HRMS district and related users
• Support old SchoolJobs district users and applicants
• Support new NC SchoolJobs powered by PeopleAdmin
district users
• Leverage Remedy for all support calls (exceptions as
approved)
– Interim usage of the “SmartSheet” on a temporary
basis approved
12
Next Steps – planning for success
• Continue with ATS Rollout
• Reengage the Applicant Tracking Advisory Board
• Rollout to the Charters
• Begin Browser compatibility initiative
• Update CEU API and work with LEAs to engage TNL
• Engage Guilford, Wake and CMS in May 2017
13
Thank You – Questions?
Joel Leeper
HRMS and Applicant Tracking Project Manager
919-807-3317
Quentin Parker
Manager, Enterprise Applications
919-807-3215
14
