Skip to end of metadata
Go to start of metadata


Training HomeOnboarding SequenceFunctional Roles HomeTechnical Roles HomeTraining Events



Onboarding Sequence


About Onboarding 

The onboarding sequence may be triggered by the Program director or any of the team leads.They will work with the Project Coordinator (STUDENT:Cheryl), who will meet with the team lead to develop an individualized onboarding plan for the new team member. This individualized plan will include the steps in this sequence. One of the key steps will be for the team lead to assign local and/or peer role "buddies" to delegate part of the onboarding process.

If you are someone administering the onboarding, checkout the Onboarding Coaching Guide for more information about the process, as well as a sample welcome email.

Sample Individualized Training Plans

For non-project resources

Important Players

  1. Team Lead
  2. Local Leadership
  3. Project Coordinator (PC) - STUDENT:Cheryl 
  4. "Buddy" Local and/or Peer/role 

Team Lead is in charge of connecting a new member with these people and any individuals that would pertain to their role on the project. The Team Lead also introduces new member to Training and Onboarding Resources page.

Local Needs

Target Date: Before start date.

Leader: Local Leadership, local Buddy. Team Lead may trigger this process as needed.

  • Workspace
    • Desk, workstation, computer, printer, etc (Some roles have specific RAM requirements. Make sure Developers, Services, QA, and UX have enough RAM to do their jobs. 8GB RAm at least)
    • Set-up collaboration tools: phone, camera, microphone, headset, PVX software (optional)
    • Set-up software (institutional access to software like MS Office)
  • Local security requirements (i.e., photo ID, badge, building access keys, parking pass, etc.)
  • Local employee, network, and email user IDs

Kuali Setup

Target Date: On/Before start date.

Leader: Team Lead, PC

  • Team Lead meets with PC to develop an individualized plan for the new team member.
  • Team member uses this Welcome document to setup a KIS account, Confluence/Jira, and Google, which they should receive in their welcome email.
  • Team Lead emails PCinformation on the appropriate groups and teams on KIS, Google calendars for the team member
  • PC acquires a CLA and sends to Kuali Foundation (
  • PC works with new member on setting up Kuali Tools (Skype, Google, etc). 
  • Developers with a signed CLA can request SVN commit access at
    • Developers also need to setup their Development Environment. It is important that the Team Lead assign a resource to help them with this process (it may be the Buddy).
    • Developers also need to complete OWASP training and record it on their KIS account. If you have questions, send a note to
  • Create a Training Blog to journal training experiences. Why journal? Read this post...

Kuali Orientation

Target Date: First two weeks

Leader: PC, Buddy

After the team member is setup with their local needs and their Kuali Tools (including a dev environment for developers), they are ready to move on to orientation. The Team Lead will assign an orientation schedule to the Buddy and the PC based on the role they expect the team member to play. Team Leads are encouraged to use the Training and Onboarding site as a guided tour and explorable text book for their new team member. They should also be aware of the Kuali Student Training Curriculum, a collection of learning objectives for onboarding as a benchmark for their training experience.

The Team Lead may modify this curriculum as they see fit. They may also suggest the team member attend project-wide training sessions as they are available at the time of orientation.