Onboard Kostiantyn

[marstamm]

Notice: This document is work in progress, help us to improve it.

Onboarding

This document describes prerequisites, the process we follow, additional topics and strategies relevant to the onboarding of new team members.

[!TIP] To create a new onboarding issue, copy the remainders of this file and replace individual parts:

• https://COMPANY_ONBOARDING_CHECKLIST_URL - Link to company onboarding list
• @BUDDY - GitHub handle of onboarding buddy

---

[!IMPORTANT] We want you to be a manager of one. Own your onboarding, reach out proactively to your buddy or the team.

@marstamm is your onboarding buddy. They guide you, connect you to others, delegate to team members for carrying out individual onboarding activities and ensure you get all the help you need.

[!IMPORTANT] We want your onboarding to be successful, and effective. To support this we ask you to give team-related onboarding activities priority over company onboarding activities.

Rest assured, you'll get to know everything that you need to know sooner or later.

Prerequisites

Initial Setup

Manager and onboarding buddy ensure that the following is accounted for:

• [x] Buddy assigned (@BUDDY)
• [ ] Connected to company onboarding checklist
• [ ] Added to rpa-team@camunda.com distribution list (via IT)
• [x] Added to relevant slack channels #rpa-team, [#prj-rpa]
• [x] Invited to team ceremonies (regular invites)
  • [x] Weekly
• [x] Onboarding issue exists based on this document
  • [x] Assigned to new colleague
• [ ] Scheduled sync with Manager

Schedule

[!NOTE]

We created this onboarding plan to guide you through your first weeks. Work your way through it in your own pace, keep it updated and adjust it where you see fit after consulting with your onboarding budy.

First Day

The goal of your first day is to meet the team, get ready for development and work on / complete your first task:

• [x] Set up means of communication (Outlook, Slack, GitHub) and ensure accounts are working
• [ ] get to know the team
• [ ] Get to know our product
• [ ] set up a basic dev environment
• [ ] learn how we work on issues
• [ ] learn about our definition of done

---

See also company onboarding checklist.

[marstamm]

Had a fist chat with @kzraitel

Discussion topics:

• Welcome to the team and team ceremonies
• Quick introduction to Camunda and the Workflow engine
• Deep dive into RPA and the planned architecture

Follow Ups:

• Ensure all services are available for onboarding, especially
  • Camunda Academy for C8 onboarding course
  • C8-SaaS for development setup and getting to know Camunda
  • Miro for our past panning documentation

[natanielstrack]

The following access for @kzraitel were request today:

• Camunda Academy for C8 onboarding course
• Miro for our past panning documentation

[natanielstrack]

The organization bellow was created for the RPA team. @marstamm and @kzraitel were add. ~It is currently in a Trial plan, a request to change it to an Internal plan was send to the Console Team.~ ✅ https://console.camunda.io/org/9061128c-7381-4caa-abbe-e97057e0e1eb

[marstamm]

@natanielstrack : We need to organize Okta access to C8-Saas-Dev as well, so that @kzraitel can access the newly created org.

Reason: Identity enforces SSO login for @camunda emails, but he has no access to the app in okta, so it denies any login attempts