📖
Tech Fleet User Guide
  • đŸŒŋSTART HERE
    • đŸ”ĸGet Started
      • 1ī¸âƒŖWhat is Tech Fleet?
      • 2ī¸âƒŖTech Fleet FAQ
      • 3ī¸âƒŖStart With the Community Collective Agreement
      • 4ī¸âƒŖFirst Steps in the Tech Fleet Community
      • 5ī¸âƒŖHow to Get Discord Roles in Tech Fleet
      • 6ī¸âƒŖHow to Become an Apprentice on Projects
      • 7ī¸âƒŖHow to Become a Co-Lead on Projects
      • 8ī¸âƒŖHow to Register for Masterclasses
  • 😃About us
    • 🤟About Our Org
      • 👋Hello World
      • 💗Mission and Values
      • 🤝We Live by the Collective Agreement
      • 🌎Diversity, Equity, and Inclusion in Action
  • 📰TRAINING OPENINGS
    • 📡Current and Upcoming Program Openings
      • 📜Project Openings
        • đŸƒâ€â™€ī¸Projects to Apply To Now
        • đŸ§™â€â™€ī¸Upcoming Projects
        • đŸ”ĨLive Project Phases in Tech Fleet
        • 🙈See It All In One Place
      • 🎓Masterclass Openings
    • â„šī¸Application Forms
  • 🚀Join The Community
    • How to Join Tech Fleet Discord
    • đŸ› ī¸Onboarding to Tech Fleet
      • 😍Book a Community Onboarding Call
      • 📧Join our Mailing List
      • 📹Onboarding Videos
      • đŸ–Ĩī¸Information Website
      • ✨Community Happenings
  • âš™ī¸RESOURCES
    • đŸ› ī¸Quick Links
      • 🤖Join Tech Fleet Discord
      • 🎨Figma Community Templates from Tech Fleet
      • 📅Tech Fleet Web Calendar
      • 📰Tech Fleet's Project Repository on Notion
      • 📧Join our Mailing List!
      • 🧭Tech Fleet's Roadmap
      • 🔗Common Links
      • 🚩Tools Used in Tech Fleet Programs
    • đŸĢCommunity Tutorials
      • 🌠Portfolio Case Study Guide
      • The Great Tech Fleet Discord Migration Video Tutorials
        • ❔Discord FAQ
        • 🌐Discord Basics
        • âœī¸Sign Up Process for Tech Fleet Discord
        • 🐎Common Channels in Tech Fleet Discord
        • 🔐Security Protocol in Tech Fleet Discord
        • đŸ§ĩBasic Chatting Abilities in Discord
        • 🤝Get a Tech Fleet Buddy
        • đŸ—“ī¸Managing Events in Tech Fleet Discord
        • 🆘Get Technical Support in Tech Fleet Discord
        • â€ŧī¸Using Roles for Alerts, Notifications, and Channel Access
        • đŸĻŽGetting Career Guidance in Tech Fleet Discord
        • đŸ’ŧGetting on Projects in Tech Fleet Discord
          • 👀Observers in Tech Fleet Discord
          • đŸŒŋApprentices In Tech Fleet Discord
          • đŸĒœCo-Leads in Tech Fleet Discord
          • đŸĢ‚Mentors in Tech Fleet Discord
        • 🎓Masterclasses in Tech Fleet Discord
      • đŸ…°ī¸Community Glossary
      • 🎨Join the Tech Fleet Figma Educational Space
      • 🤓How to Get Technical Support
    • đŸ—ī¸Project Team Tutorials
      • đŸĒ„Product Milestone Workbook
        • đŸŽ–ī¸Milestone Basics
        • 👟MVP Milestones
        • đŸŽ¯MMP Milestones
        • ✅Milestone Checklist
      • ⌛Project Kickoff Workbook
  • đŸƒâ€â™€ī¸Agile Portal
    • 🤝Agile Training in Tech Fleet
    • 🛹Agile Handbook
      • Start the Agile Handbook Here
        • 👓Contents of the Agile Handbook
        • 🌎What You Read About Agile May Be Different From What You See in the World
        • đŸŽŦAgile Manifesto Trailer
        • 🔑Introduction to the Agile Handbook
        • 🤖Can AI Replace Agile Teams?
      • đŸ§˜â€â™€ī¸Agile Philosophies
        • 🌊Waterfall Ways of Work
        • 📜Agile Ways of Work
        • 🚂Applying Agile Philosophies to Work
        • đŸŽĸBuilding MVP's and MMP's with Agile
      • 🤝Agile Teamwork
        • đŸ’ĒMaking Strong Agile Teams
          • đŸŒŋPrioritizing Growth Over Skills
          • đŸŒģThe Four Stages of Team Growth
          • 🚀Self-Actualized Agile Teams
            • đŸ—ī¸Building Agile Mindsets
            • Psychological Safety
            • Service Leadership
            • Self-Organization
            • Continuous Improvement
            • Iterative Value Delivery
        • đŸĢ‚Day-to-Day on an Agile Team
          • 👩‍🏭Cross-Functional Agile Teamwork
          • đŸĒœLeadership on Agile Teams
          • 😎Daily Life on Agile Teams
          • â™Ĩī¸Resolving Team Conflict as Service Leaders
          • 📑The Process for Resolving Conflicts
          • ❌Collective Agreement Violations
      • 🧑‍đŸ”ŦAgile Methods
        • đŸƒâ€â™€ī¸Scrum Method
          • 🤔What is Scrum?
          • 🧖Scrum Team Functions
          • đŸ—“ī¸Scrum Meetings
          • âœī¸Common Agile Deliverables
        • 🙉Other Agile Methods
      • đŸĒAgile-Related Outputs and Deliverables
        • â˛ī¸Timeline for Agile Outputs
        • 🙌Team Outputs for Agile
          • Agile Team Outputs Before Projects Begin
            • 🏇Client Kickoff
            • đŸ‘ī¸Agile Team's Vision
            • 👩‍đŸĢAgile Team Process
            • 🍱Backlogs and Kanban Boards
            • đŸĻžRACI Charts
            • 🤗Working Agreements
            • 📈Project Phase Roadmaps
          • Agile Team Outputs During Projects
            • 🧑‍đŸ’ŧSprint Planning Items
            • 👩‍đŸ’ģSprint Demo Presentations
            • đŸĻ¸â€â™€ī¸Sprint Retro Boards
            • 📏Agile Team Maturity Measurement
            • 🏁Project Hand-Off Document
        • 🚧Agile Product Development Deliverables
          • 👟Achieving Milestones on Agile Teams
          • đŸ”ŦResearch Test Plans
          • â‰ī¸Agile Product Requirements
            • 🧐Where's the PRD (Product Requirements Document)?
            • 🧠Documenting Problems, Needs, and Goals
            • â‰ī¸Mapping Product Assumptions
            • đŸ”ĸPrioritizing Problems and Future Work
            • 😎Release-Level Vision
            • 🤠Release-Level Scope
            • đŸ“¯Product Release Roadmaps
            • 🏭Epics, Features, and Work Tasks
            • âœŒī¸User Story Statements
            • ✅Acceptance Criteria
            • 🔷Behavior-Driven Development Scenarios
            • 🤔Use Case Scenarios and Task Flows
        • đŸ–Ĩī¸Deliverables Dashboard
      • 📑Agile Glossary
    • ✨Service Leadership Handbook
  • đŸŒŗPROJECT PORTAL
    • 🌱Learn About Project Training
      • â„šī¸Tech Fleet Projects are Training, Not Volunteer Work or Employment
      • 🧑‍🤝‍🧑Our Approach to Learning
      • 🌎Team Structure on Tech Fleet Projects
      • â›“ī¸Commitment vs. Job Function vs. People on Teams
      • đŸŽĸTeam Functions
        • đŸĒProduct Strategy Function
        • ⌛Project Management Function
        • 🌏User Experience Functions
          • 🎨UX Design Function
          • 🤓UX Research Function
          • âœī¸UX Writing Function
        • 🤖Development Function
        • 👩‍đŸ”ŦSolutions Architecture Function
      • 🤝UX Research Ethics
    • 📃Applying to Tech Fleet Project Training
      • 😎How Tech Fleet Project Applications Work
      • đŸ”ĸSteps to Apply to Project Training
      • âœ”ī¸Application Requirements
      • 🤠Project Timelines and Application Process
      • â‰ī¸Project Application Questions
        • ❔Tech Fleet General Application Questions
        • ❔Tech Fleet Project Phase Application Questions
      • 🤔Updating the General Application
      • 🌠Application Tips
      • đŸ—žī¸See the Latest Project Openings
    • 🔍Interview Guide for Tech Fleet Project Team Building
      • 👀Key Traits We Look For in Team Mates
      • đŸĒœCo-Lead Interview Guide for Project Coordinators
      • đŸĒ´Apprentice Interview Guide for Co-Leads
      • 📨Email Templates for Communicating to Applicants
  • 🎓MASTERCLASS-PORTAL
    • đŸ—žī¸Masterclass Openings
  • 👀OBSERVER PORTAL
    • 😎Observer Dashboard
    • 🙈Life as an Observer
    • đŸ•ĩī¸â€â™€ī¸Observer Handbook
      • đŸŽĸRead the Agile Handbook First
      • 🙈What's a Tech Fleet Observer?
      • â¤ī¸The Benefits of Observing
      • ❓Observer Frequently Asked Questions (FAQ)
      • đŸšļâ€â™€ī¸Daily Expectations of Tech Fleet Observers
        • 👩‍🎓Read the Handbooks before Observing
        • 🐐Join Tech Fleet Discord Before Observing
        • Observer Role in Discord
        • 👈Pick Projects to Observe
        • Seeing Project Deliverables as an Observer
        • 👀Day-to-Day as an Observer
        • 🤔Reflecting on Observations in Tech Fleet Discord
        • đŸĢ‚Get Support as an Observer
        • âš’ī¸Using Tools as an Observer
          • 🎨Tech Fleet Figma Educational Account for Observers
        • 🙌Knowing When you're Ready to Finish Observing
      • â¤ī¸Code of Conduct for Observers
      • 🏁Start Observing Today
  • đŸĒ´APPRENTICE PORTAL
    • đŸ–Ĩī¸Project Dashboard for Apprentices
    • 🧑‍🚀Apprentice Handbook
      • đŸĢ´Life as an Apprentice
      • Application Process for Apprentices
      • Becoming an Apprentice
      • Discord for Apprentices
      • 🎨Tech Fleet Figma Educational Account for Apprentices
      • Code of Conduct for Apprentices
      • Upholding Community Values as an Apprentice
      • Communication as an Apprentice
      • Leaving Your Project Early
      • Meetings
      • Working styles
      • Using Tools as an Apprentice
      • Organization for Apprentices
  • đŸĢļCO-LEAD PORTAL
    • đŸ–Ĩī¸Project Dashboard for Co-Leads
    • đŸĒœCo-Lead Handbook
      • đŸ”ĨLife as a Co-Lead
      • Application Process for Co-Leads
      • Discord for Co-Leads
      • Code of Conduct for Leads
      • Lead Role Breakdown
      • Upholding Community Values as a Lead
      • Principles as a Lead
      • Day-to-Day Lead Expectations
      • How to Select Your Apprentices as a Lead
      • Interviewing Apprentices as a Lead
      • Leaving Your Project Early
      • Using Tools as a Lead
      • 🎨Tech Fleet Figma Educational Account for Co-Leads
  • â¤ī¸COMMUNITY CODE OF CONDUCT
    • 💟Code of Conduct and Anti-Harassment Policy
    • 🏠Safe Space
  • 📐Policies
    • 🌏Community Collective Agreement
      • 🤗Community Core Values
        • đŸĢ´Tech Fleet's Mission and Values
        • 🤝Tech Fleet Members' Rights
        • â¤ī¸Tech Fleet Pledge of Purpose
        • đŸĢ‚Tech Fleet Pledge of Community
      • ❌Prohibited Activity in Tech Fleet
      • đŸ“ŖReporting and Resolving Issues
      • đŸ™…â€â™€ī¸Community Enforcement
      • 🌐Transforming Tension & Conflict
    • đŸ‘Šâ€âš–ī¸Tech Fleet's Policies
      • đŸ’ŧLegal Disclaimers
      • đŸ–ąī¸Slack and Discord Policy
      • 👩‍🎓Masterclass Terms and Conditions
      • âĒServices Refund Policy
      • 📓Tech Fleet Bylaws
      • 👤Tech Fleet Board Member Covenant
      • đŸ‘ī¸â€đŸ—¨ī¸Conflict of Interest Policy
      • 🔎Information Security Procedures
  • đŸ—ī¸GUILD PORTAL
    • đŸ’ģTech Fleet Operations
      • đŸĨŗTech Fleet Operations Workbook
      • âš–ī¸Governance
      • đŸ‘Šâ€âš–ī¸Board of Directors
    • đŸ‘ŖGuild Directory
      • 🎓Growth and Development Guild
      • 🚧Infrastructure Guild
      • 🙏Leadership Guild
      • đŸĒProduct Team Guild
      • 🕧Project Coordinator Guild
      • đŸ“ŧVideo Production Guild
    • âš’ī¸Guild Handbook
      • đŸŖCreating Change in Tech Fleet
      • Code of Conduct for Guilds
      • Guilds in Tech Fleet
      • Creating a new Guild
      • Operating a Guild
      • Guild Bylaws Template
  • đŸĢļProject Coordinator Portal
    • âš™ī¸Project Coordinator Handbook
      • Code of Conduct for Project Coordinators
      • Project Coordinator Process
      • Using Tools as a Project Coordinator
      • Project Intake Process
      • Getting the Team Formed
      • Pre-Kickoff as a Project Coordinator
      • Kickoff as a Project Coordinator
Powered by GitBook
On this page
  • Introduction
  • If they have never been on Tech Fleet projects
  • If they have previously been on Tech Fleet projects
  1. PROJECT PORTAL
  2. Interview Guide for Tech Fleet Project Team Building

Co-Lead Interview Guide for Project Coordinators

Here's a full interview guide for project coordinators to interview co-leads. If you are applying as a co-lead, you can use this as a guideline to prepare for your interview.

PreviousKey Traits We Look For in Team MatesNextApprentice Interview Guide for Co-Leads

Last updated 2 months ago

Did you know?

Do not record video or audio, or AI transcription of team interviews.

Rely on note-taking during the interview. This is for the sake of data privacy policies in Tech Fleet.

If you must record, you must delete the recording after the meeting. You must ask permission to record.

Introduction

Yellow highlighted text is suggested questions to candidates

Introductions
  1. Break the ice a little before beginning

  2. Tell them the agenda:

    1. We will not record this session but I may take notes for my own recruiting efforts

    2. I’d like to get to know you and learn what you’d like to get out of project training

    3. I’d like to tell you more about how Tech Fleet projects operate in our apprenticeship training.

    4. I’d like to talk about Service leadership and Agile with you

    5. I’d like to leave room for questions at the end.

    6. How does that sound to you?

  3. Tell me about yourself

    1. Professional background, other key things to get to know them as a person

  4. How long have you been in the Tech Fleet community?

  5. How much do you know about Tech Fleet community?

    1. If not much, tell them the history of Tech Fleet

      1. Tech Fleet started as a community in 2020

      2. We’re now a nonprofit public charity that’s driven by our community members

      3. We offer project apprenticeship training and masterclass training for a lot of different tech roles related to Agile

      4. We live to open as many opportunities as possible to build skills and experience

  6. How is it going so far for you in the community?

  7. Have you ever been on a Tech Fleet project before?

    1. If yes, go to "Previously been on a Tech Fleet project" section

    2. If no, go to "If they have never been on Tech Fleet projects"

If they have never been on Tech Fleet projects

Yellow highlighted text is suggested questions to candidates

Tech Fleet Basics

How much do you know about Tech Fleet project training?

  1. Always cover the basics:

    1. Tech Fleet is an apprenticeship training organization.

    2. Teams are trained on real Agile methodologies, which are very different from how a lot of schools teach UX and product work, but this is a safe environment to fail and learn.

    3. The priority on a team is to grow and learn, NOT to produce work. This is not a competitive environment.

    4. It's an environment to get things wrong and to embrace failure. Team mates need to be given safe spaces to learn.

    5. When you’re on a team, you’re in an apprenticeship training. You are not in a job or volunteer position.

    6. Teams work with nonprofit clients.

    7. Team members are expected to perform a new way of working as they will be expected in the industry: Agile.

Here's some information about the project you are joining:

  1. Provide basics about the client's mission

  2. Provide basics about the client's project goals

  3. Provide information about any previous phases of work and what we did in previous phases

  4. Provide information about the key outcomes for this coming phase

  5. Remind the candidate that we are going to produce the work in parallel: UX research, UX design, and development work will happen at the same time throughout the entire project, and it will never stop, because we are performing Agile work.

Agile and Co-Lead Basics

Are you familiar with the Agile ways of working versus the Waterfall ways of working?

  • Hopefully they have prepared for Agile in Tech Fleet. If not, they may have done so outside of Tech Fleet, or they may not have had the chance yet.

I’d like to go over how Tech Fleet Agile teams operate so that you know what to expect:

  1. Agile is a way of building things that provides incremental value instead of value at the end of projects.

  2. UX work and development happens continuously and at the same time.

  3. We work in the Scrum method, are you familiar with that?

    1. Either way:

      1. We do “sprints”: 2 weeks of work at a time, and deliver small chunks of UX work every 2 weeks.

      2. Each sprint, the teams deliver research, design, and product work in parallel.

      3. Each project phase is 4 sprints.

      4. When one project phase ends, the team documents a handoff and then we open applications for the next project.

      5. Instead of working alone in a specific title, you will have the opportunity to float across different activities based on what you want to do.

  4. We have Agile coaches that are training in this community who work with teams to coach Agile and get them going as a Scrum team.

I’d also like to go over how apprentices and co-leads operate so you know what to expect:

  1. Co-leads are not bosses or managers. They do not have the answer. They are guides in service to others' growth.

  2. There is no hierarchy on the team. Co-leads are equals to each other, and co-leads are equals to apprentices.

  3. Every sprint, everyone commits to the work they want to do based on a shared outcome of the team. Agile coaches will work with you all to train in how to work cross-functionally. It's up to you to empower growth in your team mates, while they empower growth in you.

  4. Co-leads and apprentices are all servant leaders to each other, and provide psychological safety to each other. Are you familiar with these terms?

    1. They should! They should have prepared pretty deeply in these two things through the . If they do not answer adequately, it's a sign they are less ready for Agile team roles and may have more preparation to do.

  5. Do you have any questions or thoughts about this?

Prior Preparation Work in Tech Fleet

We recommend everyone read the user guide for Agile Handbook and Life in Tech Fleet before proceeding in project team training. Have you read this yet?

  • They should have done this

  • What did you takeaway from the Agile Handbook that you want to bring onto teams with you?

  • If not, it may show less commitment from candidates. Invite them to do so asap. Say that we actively look for people who already observed in Tech Fleet before joining teams. This may not show their commitment.

We recommend everyone spend at least one sprint to observe project training teams in Tech Fleet to learn how Agile life works daily. Have you done this yet?

  • They should have done this

  • If yes: what did you learn during observing that you want to take onto team training with you?

  • If no, this may not show their commitment. Encourage them to do so asap. Say that we actively look for people who already observed in Tech Fleet before joining teams. This may not show their commitment.

We recommend everyone take the Servant Leadership Masterclass before joining Tech Fleet training teams. Have you done this yet?

  • They should have done this

  • If yes: what did you learn during the class that you want to take onto team training with you?

  • If no, this may not show their commitment. Encourage them to do so asap. Say that we actively look for people who already practice Servant Leadership as apprentices and co-leads in Tech Fleet before joining teams.

Suggested Co-Lead Candidate Questions

How would you explain servant leadership in your own words?

  • They should be able to describe it in their own words, not copy-pasted from this user guide. This shows that the learning has been applied beyond something they read.

Servant leaders transfer the power to their apprentices. How will you do this on your team?

  • They should be able to speak to how they approach servant leadership and psychological safety

  • They should be able to compare leadership styles like authoritarian leadership vs. lasseiz-faire vs. servant as they learned in the Servant Leadership Masterclass.

How do you live as a servant leader to your peers and apprentices?

  • They should be listing the traits of daily servant leadership behavior that were taught in the Servant Leadership Masterclass.

How would you contribute to coaching your team in the Agile philosophies?

Some teams find themselves in situations where apprentices wait to be told what to do. Some co-leads tell apprentices what to do or how to work. This is the opposite of the dynamic we want. We want servant leaders who empower other servant leaders. What does this mean to you? How would you accomplish this on your team?

  • They should be able to describe how they would build psychological safety and empowerment for service leadership on the team.

  • They should describe how they will approach building self-organization on their team, where team mates decide together how to work and how to solve problems.

  • They should describe how they will provide space for people to have a voice and feel a true sense of ownership in the work.

How would you handle a situation where a team mate is not being a servant leader to you or to someone else?

How would you handle situations of uncertainty, or situations where the client is not providing direction you need as a team?

  • They should speak to their self-organization principle in Agile.

Do you have any questions for me?

  • Look for their readiness to dig into the project work and their prior preparation in the Notion deliverables that were produced by previous teams.

  • Look for their willingness and initiative to be an Agile servant leader and what they are looking to give back to others over giving to themselves.

  • Look for how much they have prepared their questions.

If they have previously been on Tech Fleet projects

Yellow highlighted text is suggested questions to candidates

Tech Fleet Basics

Tech Fleet is trying to improve its Agile training. Our new structure for projects will include Agile coaches to train teams in Agile cross-functional teamwork. Here's what that means:

  1. We will bring an Agile coach into projects to coach team mates in Agile.

  2. The priority on a team is to grow and learn, NOT to produce work. This is not a competitive environment.

  3. It's an environment to get things wrong and to embrace failure. Team mates need to be given safe spaces to learn.

  4. When you’re on a team, you’re in an apprenticeship training. You are not in a job or volunteer position.

Here's some information about the project you are joining:

(If they have never been on this particular project before)

  1. Provide basics about the client's mission

  2. Provide basics about the client's project goals

  3. Provide information about any previous phases of work and what we did in previous phases

  4. Provide information about the key outcomes for this coming phase

  5. Remind the candidate that we are going to produce the work in parallel: UX research, UX design, and development work will happen at the same time throughout the entire project, and it will never stop, because we are performing Agile work.

(If they have been on this particular project before)

  1. Provide information about the key outcomes for this coming phase

  2. Remind the candidate that we are going to produce the work in parallel: UX research, UX design, and development work will happen at the same time throughout the entire project, and it will never stop, because we are performing Agile work.

Agile and Co-Lead Basics

Are you familiar with the Agile ways of working versus the Waterfall ways of working?

  • Hopefully they have prepared for Agile in Tech Fleet and been through it on the other project. If not, they may have done so outside of Tech Fleet, or they may not have had the chance yet.

I’d like to go over how Tech Fleet Agile teams operate so that you know what to expect:

  1. Agile is a way of building things that provides incremental value instead of value at the end of projects.

  2. UX work and development happens continuously and at the same time.

  3. We work in the Scrum method, are you familiar with that?

    1. Either way:

      1. We do “sprints”: 2 weeks of work at a time, and deliver small chunks of UX work every 2 weeks.

      2. Each sprint, the teams deliver research, design, and product work in parallel.

      3. Each project phase is 4 sprints.

      4. When one project phase ends, the team documents a handoff and then we open applications for the next project.

      5. Instead of working alone in a specific title, you will have the opportunity to float across different activities based on what you want to do.

  4. We have Agile coaches that are training in this community who work with teams to coach Agile and get them going as a Scrum team.

I’d also like to go over how apprentices and co-leads operate so you know what to expect:

  1. Co-leads are not bosses or managers. They do not have the answer. They are guides in service to others' growth.

  2. There is no hierarchy on the team. Co-leads are equals to each other, and co-leads are equals to apprentices.

  3. Every sprint, everyone commits to the work they want to do based on a shared outcome of the team. Agile coaches will work with you all to train in how to work cross-functionally. It's up to you to empower growth in your team mates, while they empower growth in you.

  4. Co-leads and apprentices are all servant leaders to each other, and provide psychological safety to each other. Are you familiar with these terms?

  5. Do you have any questions or thoughts about this?

Prior Preparation Work in Tech Fleet

We recommend everyone read the user guide for Agile Handbook and Life in Tech Fleet before proceeding in project team training. Have you read this yet?

  • They should have done this

  • What did you takeaway from the Agile Handbook that you want to bring onto teams with you?

  • If not, it may show less commitment from candidates. Invite them to do so asap. Say that we actively look for people who already observed in Tech Fleet before joining teams. This may not show their commitment.

We recommend everyone spend at least one sprint to observe project training teams in Tech Fleet to learn how Agile life works daily. Have you done this yet?

  • They should have done this

  • If yes: what did you learn during observing that you want to take onto team training with you?

  • If no, this may not show their commitment. Encourage them to do so asap. Say that we actively look for people who already observed in Tech Fleet before joining teams. This may not show their commitment.

We recommend everyone take the Servant Leadership Masterclass before joining Tech Fleet training teams. Have you done this yet?

  • They should have done this

  • If yes: what did you learn during the class that you want to take onto team training with you?

  • If no, this may not show their commitment. Encourage them to do so asap. Say that we actively look for people who already practice Servant Leadership as apprentices and co-leads in Tech Fleet before joining teams.

Suggested Co-Lead Candidate Questions

How did the last Tech Fleet project go for you? What did you learn in the previous Tech Fleet project you were on that you want to take into this project phase?

  • Look for their takeaways in Agile philosophies and how they will approach work differently compared to the last project.

  • Do they look at things as opportunities or as problems?

  • Do they initiate change constructively and lead the way by example as a servant leader?

  • How do they handle adversity, and "beans up the nose"? They should be masters of beans and noses by now. How much do they showcase this? How much can they speak to it?

How would you explain servant leadership in your own words?

  • They should be able to describe it in their own words, not copy-pasted from this user guide. This shows that the learning has been applied beyond something they read.

Servant leaders transfer the power to their apprentices. How will you do this on your team?

  • They should be able to speak to how they approach servant leadership and psychological safety

  • They should be able to compare leadership styles like authoritarian leadership vs. lassies-faire vs. servant as they learned in the Servant Leadership Masterclass.

How do you live as a servant leader to your peers and apprentices?

  • They should be listing the traits of daily servant leadership behavior that were taught in the Servant Leadership Masterclass.

How would you contribute to coaching your team in the Agile philosophies?

Some teams find themselves in situations where apprentices wait to be told what to do. Some co-leads tell apprentices what to do or how to work. This is the opposite of the dynamic we want. We want servant leaders who empower other servant leaders. What does this mean to you? How would you accomplish this on your team?

  • They should be able to describe how they would build psychological safety and empowerment for service leadership on the team.

  • They should describe how they will approach building self-organization on their team, where team mates decide together how to work and how to solve problems.

  • They should describe how they will provide space for people to have a voice and feel a true sense of ownership in the work.

How would you handle a situation where a team mate is not being a servant leader to you or to someone else?

How would you handle situations of uncertainty, or situations where the client is not providing direction you need as a team?

  • They should speak to their self-organization principle in Agile.

Do you have any questions for me?

  • Look for their readiness to dig into the project work and their prior preparation in the Notion deliverables that were produced by previous teams.

  • Look for their willingness and initiative to be an Agile servant leader and what they are looking to give back to others over giving to themselves.

  • Look for how much they have prepared their questions.

They should have a firm understanding of servant leadership and how it relates to : psychological safety, self-organization, and continuous improvement.

They should be referencing the tenets of .

Everyone plays a role in this, every single team mate, .

Everyone should be building the tenets of starting with psychological safety. Strong co-lead candidates will should describe how they will approach this.

They should be able to describe how they will handle conflict resolution as a servant leader according to their .

They should have read the and understand how to resolve conflict while still being a servant leader with psychological safety to others.

They should be able to describe how they will introduce iterative value every moment when there is no certainty, they will empower their team to make value and introduce .

They should! They should have prepared pretty deeply in these two things through the . If they do not answer adequately, it's a sign they are less ready for Agile team roles and may have more preparation to do.

Look for their willingness to themselves and help others do so as well, as part of the .

They should have a firm understanding of servant leadership and how it relates to : psychological safety, self-organization, and continuous improvement.

They should be referencing the tenets of .

Everyone plays a role in this, every single team mate, .

Everyone should be building the tenets of starting with psychological safety. Strong co-lead candidates will should describe how they will approach this.

They should be able to describe how they will handle conflict resolution as a servant leader according to their .

They should have read the and understand how to resolve conflict while still being a servant leader with psychological safety to others.

They should be able to describe how they will introduce iterative value every moment when there is no certainty, they will empower their team to make value and introduce .

đŸŒŗ
🔍
đŸĒœ
Tech Fleet agile training
self-actualized agile teams
self-actualized agile teams
even apprentices
self-actualized agile teams
agile training in Tech Fleet
conflict resolution guidelines
recommended value iteratively
Tech Fleet agile training
continuously improve
Agile team tenets
self-actualized agile teams
self-actualized agile teams
even apprentices
self-actualized agile teams
agile training in Tech Fleet
conflict resolution guidelines
recommended value iteratively