Getting the Team Formed

Creating the Job Description and application

Owner: Project CoordinatorLink: Tech Fleet Drive Project Folderhttps://drive.google.com/drive/folders/1x5sjPC7E-WTTilsso7oYnzR9NbYbMA7h?usp=sharing

  • From the above link: create a folder for a new project or create a new phase folder within a project folder

  • Go to the β€œNew Project Templates Make Some Copies” folder and duplicate the Job Description, Leads application, Apprentice application docs

  • Move them to your new folder

  • Edit as necessary using the Work Agreement as a base to fill in the appropriate information

  • Delete roles that will not be used on the project from applications and the job description

  • Ensure all links are working and up to date

  • Turn on the β€œAccepting Responses” to both applications

Posting on Tech Fleet Slack

In Slack create a template for posting new projects (and save it in a message to yourself) or edit the below version:

<aside> β†˜οΈ Applications will be open from ___ to ___

Please read the full project description before applying LINK TO JOB DESCRIPTION!

Project Summary: Copy and paste from Job Description Doc

Roles (Click the link to view job descriptions): Copy and paste from Job Description Doc

Direct Application Links: Lead Application: Copy and paste from Job Description Doc Apprentice Application: Copy and paste from Job Description Doc

Apprentices and leads are expected to contribute 15 - 20 hours per week commitment.

✨Read the Tech Fleet apprentice handbook for detailed day-to-day expectations ✨

</aside>

Post in the #project-postings and #announcement channels on Slack. Morgan will usually post to specific Bootcamps & Social Media.

Building the Leads Team

Based on how many Leads apply you can start reaching out to people before the applications close. If the project is not getting very many applications send a new post to the #project-postings and #announcement channels on Slack to encourage more applications. Once the applications close, determine how many Leads are needed for the project. If there are multiple applications per position, reach out to see if they would be okay with a co-lead. Otherwise assess the project needs and best fit. Interview candidates and confirm commitment (recommending a 12-week commitment for leads) and give them a brief timeline of upcoming events

β†˜οΈ Week of ____ Lead team forms. Leads decide who to interview Week of ____ Leads reach out to schedule interviews and begin interviewing Week of ____ Leads finish interviews and make decisions Week of ____ apprentices are notified, pre-kickoff activities Week of ____ official project kickoff

Recruiting more Leads as necessary

  1. Look through the apprentice applications to interview and offer the lead to the strongest responses

  2. Reach out to other Leads and Project Coordinators for additional recommendations

  3. Repost for Leads only

  4. Have Morgan post an inspiring message to help build confidence in the community

Once you have filled all the Lead positions, have Morgan create a #project-leads leads channel (Usually a private channel for the Leads team to discuss the project freely)

Give the Leads a more detailed list of the upcoming steps and encourage them to start introductions:

β†˜οΈ Send on Leads channel

  1. Let’s set up a time for the Leads to meet!

  2. Project Coordinator will share a spreadsheet of candidates for the individual leads to rank. Each team has its own tab at the bottom.

  3. Leads determine the criteria they are looking for in apprentices (Apprentices that are currently on other projects are listed in the notes, please make them the lowest priority to interview. Unless the current project will end before this one starts)

  4. Leads interview apprentices

  5. Leads choose and inform apprentices

    1. Also share apprentice list on leads channel

    2. If time allows, give feedback to those not chosen

  6. Project Coordinator or Team Lead makes the announcement listing all apprentices on the project in Slack

  7. Team Leads each run their own icebreaker meeting for everyone to get to know each other on each team. Additional recommended topics:

    1. Scheduling

    2. Working agreements

  8. Project Lead and Product Strategy Lead conduct Sprint 1 planning with the team before kickoff

  9. Project Kickoff

    1. onboarding with apprentices (sending links or case studies from previous phase work, etc)

    2. All team icebreaker meeting

    3. Schedule all team meetings (Any cross-functional meetings, Daily stand up, Weekly Sprint Planning, and Retro)

If applicable, share the Client Intake Form with the Leads team. If this is an ongoing project share the previous phase’s documentation (Notion). This is an excellent time to see how curious the Leads are and will help you determine how much help they might need.

Last updated