Illustration of people working on devices, making updates, and coding.

AIMS Transition Project roadmap

Transition planning to bring Administrative Information Management Services (AIMS) and the Division of Information Technology (DoIT) together began in earnest in late February 2022. Team members from both AIMS and DoIT are meeting regularly to map out the strategy. The following roadmap of the AIMS transition project activities is published monthly.

More information about this project can be found on the AIMS Transition Project page. If you prefer to receive this roadmap in your inbox, please subscribe to our Google Group. Within a minute or two of sending this subscription request email, you will receive an email from Google that includes steps to confirm your membership.

Do you have questions and concerns? Please contact us. We will regularly review and answer your feedback during the weekly transition team meeting. 

Previous updates: May 1 | April 1


May 1, 2022

Complete

  • Published an informational project website for the transition.
  • Held AIMS/User Services/SEO information sharing sessions and the first combined leadership team meeting.
  • Sent an initial communication to all AIMS customers.
  • Created a feedback form and implemented a process for tracking and responding to questions, concerns, and feedback.
  • Created a JIRA board for task tracking and project management.

Now

  • Completion of a project plan and reporting structure.
  • Create an Organizational Change Management (OCM) plan.
  • Create a comprehensive list of tasks in the backlog of work.
  • Develop a communication plan.

Next

  • Begin execution of OCM plan.
  • Organize and prioritize the comprehensive backlog of work for the project.
  • Identify all AIMS/DoIT services to be evaluated for unification.

Later

  • Planning for system integrations (e.g. Cherwell).
  • Evaluate and prioritize AIMS/DoIT services identified for unification.

April 1, 2022

Complete

  • Transition teams kick-off.
    • Divisional leadership team – Provide support and guidance for the project; manage the financial and human resources requirements for the project; remove barriers as needed.
    • Transition planning team – Plan the general activities of the project team, subject matter experts, and sub-teams involved in the project. Responsible for project deliverables.
    • Transition monitoring team – Provide upward communication to project leadership,  keep the pulse of the organization,  and understand the impact of the transition on people involved in the transition.
  • Transition project charter approved.
  • Initial meeting with the Office of Strategic Consulting as a partner in the transition.
  • Work plan completed.

Now

These are the activities and features we are currently working.

  • Project plan development, which will include a firm target end date.
  • Informational project website for the transition.
  • AIMS/User Services information sharing sessions.

Next

These are the activities and features we plan to work on next.

  • Engagement with the Office of Strategic Consulting to create an Organizational Change Management (OCM) plan.
  • Create initial integration plan of AIMS and DoIT groups for feedback and refinement.
  • Begin developing the backlog of work.

Later

These are activities, features, and requests that are being explored and are potential candidates for working on next.

  • Begin execution of OCM plan.
  • Identify all AIMS/DoIT services to be evaluated for unification.
  • Develop a comprehensive backlog of work for the project.