Collaboration kick-start

Just an initial demo map, so that you don't start with an empty map list ...

Get Started. It's Free
or sign up with your email address
Collaboration kick-start by Mind Map: Collaboration kick-start

1. Infrastructure design

1.1. Attended/Unattended

1.2. Team size

1.3. Nr. of robots

1.3.1. UAT/Prod

1.3.2. Security policies (per department?)

1.4. Virtual/physical machines

1.5. Operating System for Dev/Robot machines

1.6. Cloud vs on-prem

1.7. Limitations

1.7.1. Internet access

1.7.2. Citrix

2. Infrastructure provisioning

2.1. Acquire license keys

2.2. Orchestrator

2.2.1. RACI Automatify/Internal IT

2.2.2. Machine creation

2.2.3. Software prerequisites

2.2.4. Install & configure orchestrator

2.2.5. Tennants/Folders design

2.2.6. Dedicated test orchestrator

2.3. Development

2.3.1. Machines

2.3.2. AD accounts

2.3.3. VPN access

2.3.4. Mailboxes

2.3.5. UiPath studio installation

2.4. Robots for Test/Prod

2.4.1. AD accounts

2.4.2. Robot machines

2.4.3. Install & configure UiPath

3. Collaboration

3.1. File sharing

3.2. Demo frequency

3.2.1. Video

3.2.2. Live demo

3.3. Weekly status meetings

3.4. Communication

3.4.1. Teams

3.4.2. E-mail

4. Process-specific

4.1. Infrastructure

4.1.1. Install & configure applications&mailboxes

4.1.1.1. User creation (where no SSO)

4.1.1.2. Assign rights to robot users

4.1.1.2.1. DEV

4.1.1.2.2. UAT

4.1.1.2.3. PROD

4.2. Test data

4.2.1. Happy flow

4.2.2. Frequent exceptions

4.3. Rollout

4.3.1. UAT

4.3.1.1. Establish accountable

4.3.1.2. Timeline

4.3.1.3. Deploy

4.3.1.4. Kick-off session

4.3.1.5. Regular status check (every 1-2 days)

4.3.1.6. Sign-off

4.3.2. PROD

4.3.2.1. Deploy

4.3.2.2. Hypercare access/communication flow

4.3.2.3. First tests