📖
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
  • General
  • Communicate with the other Leads (and Project Coordinator)
  • Meetings
  • Service Leadership
  • Team Norms
  • Team Liaisons
  • Conflict resolution
  • Consensus options
  1. CO-LEAD PORTAL
  2. Co-Lead Handbook

Day-to-Day Lead Expectations

PreviousPrinciples as a LeadNextHow to Select Your Apprentices as a Lead

Last updated 1 month ago

General

  • Use the project channels for all project-related discussions (it keeps everyone informed) - no sidebars

  • Write dates as Month 00, instead of 00/00 to avoid confusion with the American vs. Global format

  • Write times as 00:00 am/pm in a 12-hour format with a time zone

  • Be inclusive of everyone’s time zone

  • If you cannot attend a meeting or will miss a deadline, let your Lead know as soon as possible

  • Meetings will be scheduled when 60% of folks can attend. Meetings will be recorded and notes will accompany meetings so if people miss, they can catch up.

Communicate with the other Leads (and Project Coordinator)

Communication is vital for any project to succeed. We recommend once you have determined the list of apprentices to interview share that on the Lead’s channel. It is common for apprentices to apply to multiple roles on a project, so it is nice to share with other leads just in case you both are competing for the same person. Having the Project Coordinator informed can also help. They might have knowledge about the applicant, whether they accepted a role on another project but has not been announced or if the apprentice has a history of poor performance.

Meetings

  • Daily stand-ups (async should take 2 minutes) to make sure team is aware of what you’re working on and of any potential roadblocks

  • Stand up channel

    • Encourage all members to do daily stand-ups for proper agile methodology experience

      • This is not a place for detailed information. These daily slack stand-ups are to be used as cross-functional exchanges of information for your team to stay up to date on what everyone is doing so there are no surprises as the work progresses.

      • Use the “Reply” function to post your standup under the first standup post of the day.

        • Y: What did you do yesterday?

        • T: What are you doing today?

        • B: Do you have any blockers?

  • Schedule all meetings ahead of time with agendas in mind you never want to come to a meeting unprepared

    • Use the project name as a prefix when scheduling meetings: “Project” Daily Stand Up, “Project” Research, “Project” Sprint Planning, etc.

  • Post all meetings on the shadow channels and always add to all meetings to make sure they’re reflected on the tech fleet calendar for everyone to see

  • Make sure you’re on track with the product roadmap and that you’re letting your product team know of any necessary pivots

Service Leadership

Service leadership is crucial for successful Agile teams. Being a service leader means you're not telling people what to do or giving them the answer, or preventing them from failing. You are their guide and empowering them to find the answer on their own. Leads are not managers, they are not above anyone else on the team; they are contributors on the team who happen to lead and guide others to success while learning themselves.

Read more about Tech Fleet Agile principles that need to be adhered to in the Agile Handbook.

Team Norms

💡 As we all work remotely, it’s important we clarify how we’re going to work together to be most effective.

  • Treat one another with dignity and respect

  • Actively listen

  • Be open-minded with all suggestions

  • Celebrate accomplishments

  • EVERYONE is welcome to join all meetings - this will assist with cross-functional interactions! (with the exception of NDA projects)

Team Liaisons

Something started in the Earth Hero project that has proven to be a great way for teams to collaborate and encourage cross-team understanding is team liaisons. A team liaison is a member of a different team that commits to attending another team’s meeting. One person from design goes to all the research meetings, another goes to content meetings, another goes to strategy meetings, and so on. If an apprentice has an interest in another specialty this is a good opportunity to pair them up with that team.

Here is an example of how The Serious Type Phase 4 organized their team liaisons:

Conflict resolution

  • Strive to understand each other's perspectives, rather than jumping to conclusions

  • Try to resolve problems without blaming

  • It is important that the team feels heard or that they are able to talk about their concerns. Make it known that they can reach out to you or other leads. We are all here to support & uplift each other!

Consensus options

  • Differing opinions are valuable but remove ego when making a consensus decision

  • Agree to discuss how an idea could work and why it is a viable option

🫶
🪜
techfleetnetwork@gmail.com
🛹Agile Handbook
Team Schedules