📖
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
  1. APPRENTICE PORTAL
  2. Apprentice Handbook

Meetings

Meetings can be an effective way of garnering feedback and input from members of your team, unblocking a team or team member, or simply staying aligned. Some meetings are recurring on a daily or weekly basis and require attendance from the entire team or a subsection of the team. Other meetings are organized on a case-by-case basis to address ongoing tasks or make decisions. Keep in mind, whatever can be done asynchronously (or ‘async’) should be done asynchronously.

When part of a call, please make sure to make sure your camera is on when possible. Talking to a picture or a name label isn’t fun and makes conversation feel less intuitive. Also, when your camera is on, using the ‘blur’ feature can minimize distractions and keep team members focused on you.

When to call a meeting

Meetings can be called by any member of the team provided there is a strong enough justification for doing so. A good rule of thumb is, if you’ve gone back and forth more than twice and haven’t come to a decision or agreement, a quick five minute meeting may be required. If something requires active feedback and input from multiple team members and cannot be addressed during a working session, a call can be scheduled to do so. Always make sure to go into meetings with an agenda and come out of them with action items.

Working sessions

Working sessions are daily blocks of time dedicated to workshopping with the greater collective. For example, the product strategy team may want to perform a prioritization activity using the MoSCoW method (Must have, Could have, Should have, Won’t have) to determine overall strategic direction. The goal of a working session is to unblock teams and help them make progress asynchronously. Any activity that requires attention from the entire team should default to a working session.

Sprint planning

Sprint planning is a weekly meeting dedicated to organizing the upcoming sprint. This meeting always requires attention and input from the entire team and should be facilitated by the strategy team and a scrum master. Representatives from each department can use this time to catch everyone else up on their progress and determine direction moving forward.

Sprint retrospectives

Our team processes are imperfect and often require shaping and molding on a weekly basis. Sometimes we are satisfied with how a process has been carried out and want to replicate it moving forward. Other times, we may feel a process needs to change. Retrospectives (or ‘retros’) are a time for apprentices to communicate these thoughts. There should be minimal leadership in attendance so as not to influence the discussion being held and all thoughts and outcomes should be prioritized by the strategy team for future implementation. During sprint retros, you will focus on:

  • What you liked - ****Here you’ll focus on the aspects of the sprint you enjoyed and would like to highlight or replicate.

  • What you learned - We all take something away from our experiences. This is a chance to discuss what may have been for you.

  • What you longed for - No process is perfect and we often wish we were able to do something differently. Talk about that here.

  • What you needed - Did something really block your progress during the sprint? Talk to the team about what could have helped you get past that blocker and how everyone can access that solution.

Happy hours

All play and no work. This meeting is a non-meeting. It is entirely up to team members as for when they’d like to schedule a happy hour but once on the call, no work talk is allowed. Apart from that, the sky is the limit.

Recording meetings

Meeting recordings are incredibly useful when multiple teams should have access to information discussed during call (i.e. a client demo). Some meetings such as client demos should be recorded by default, whereas others should be recorded only if needed. Keep in mind that they require a significant portion of our resources (storage space in the cloud) to hold onto. A good set of meeting notes and action items can often go a much longer way to keep a team productive and moving.

PreviousLeaving Your Project EarlyNextWorking styles

Last updated 8 months ago

🪴
🧑‍🚀