📖
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
  • Video Version
  • Waterfall is the Opposite of Cross-Functional Agile Teamwork
  • Cross-Functional Agile Teams are More Flexible
  • Agile Teams are Like a Heist Crew
  •   Carrying Out Agile Cross-Functional Teamwork
  •  Agreeing to Daily Responsibilities
  • Deliverables for Cross-Functional Work
  1. 🏃‍♀️Agile Portal
  2. 🛹Agile Handbook
  3. 🤝Agile Teamwork
  4. 🫂Day-to-Day on an Agile Team

👩‍🏭Cross-Functional Agile Teamwork

Agile teams collaborate across their job titles. In fact, there should be no "job titles" limiting people to responsibilities! Read more below.

PreviousDay-to-Day on an Agile TeamNextLeadership on Agile Teams

Last updated 2 months ago

Video Version

Waterfall is the Opposite of Cross-Functional Agile Teamwork

Waterfall teams dedicate people to specific functions. In a traditional waterfall team, each person has a dedicated duty that they do all the time.

 The designer designs. The coder codes. The researcher researches. They all rely on each other to do their specific function.

 When one person leaves, everyone else waits. The specified duty must be filled.

 Work stops.

 When the researcher is busy, the rest of the team waits for them to finish.

 Work stops.

 That's not efficient at all.

 When they don't involve others in their work, they create what's called a "work silo". Someone who is dedicated to a role does the work alone, and only for what they were hired for.

  Waterfall teams are made up of "work silos".

Cross-Functional Agile Teams are More Flexible

 We need to work together to achieve shared outcomes. We need different perspectives to make decisions. We need to share knowledge and information across teams for them to succeed. Cross-functional teamwork achieves this.

 "Cross-functional" Agile teams are teams that contribute across functions together.

 They have diverse backgrounds and perspectives. They pitch into each other's work, and they aren't working in one single function. Perspectives are shared across all functions when performing duties. Everyone can contribute to responsibilities across functions whenever they want to.

 Cross-functional team members contribute toward a "shared outcome". The entire team, and all of its functions, equally pitch in to get the outcome achieved. When designers volunteer to code, and researchers volunteer to design, and designers volunteer to research, this is celebrated. 📍

Agile Teams are Like a Heist Crew

 A cross-functional Agile team is assembled for the "perfect heist". They have no titles. They do not stick to one duty. They will only achieve success by working with each other collaboratively.

They all have different backgrounds. They each bring their own unique capabilities. They collaborate with each other in work across different skill sets and functions. They volunteer in the moments that work is needed to achieve the outcome.

Each teammate pitches in to collaborate on work that the other teammates are doing all the time. Diverse perspectives are heard in the work. The more diverse perspectives are heard, the stronger the outcomes. Everyone is a valuable member of the Agile Heist Team.

 Each week, the duties change because the team asks who wants to own work whenever they prioritize tasks. People agree to the responsibilities they play in the moments that work needs to be prioritized. They self-organize and agree together who's going to be involved, and how.

You've got the psychological safety to take risks, and you've got service leaders around you helping you grow while doing work that you may have never done before. You and the team self-organize to agree to who will pitch into work. The team prioritizes opportunities for people to continuously improve and try things for the first time.

  Carrying Out Agile Cross-Functional Teamwork

 Here are some things you will hear on strongly performing Agile cross-functional teams:

 If there's strong psychological safety:

“I’m a developer, but I want to participate in user testing this sprint with the designers and researchers.”

 If there's strong service leadership:

"How do you want to be supported in the work? How do you want to get involved in other team roles?”

If there's strong self-organization:

“All teams can vote together on what tasks we’re going to take on this iteration”

If there's strong continuous improvement:

“Let’s get with the research team to discuss how this design task went and discuss how to change the way we collaborate in the future”

If there's strong iterative value delivery:

“We’re going to have a usable feature to test with users by the end of the week”.

 Agreeing to Daily Responsibilities

 All of this may sound confusing to you if you've never experienced it. Why not stick to your job duties? Work silos are good for expectation setting, right?

 If your job title is one thing, and you are supposed to work cross-functionally, does that mean you are not doing things in your job title?

No!

Everyone makes their own decision about what they want to contribute to on the team as part of the heist team. No person tells other people what to work on. Teammates assign themselves work based on the team goals and their interests.

 If teammates want to stick to a particular function, they'd still collaborate with other kinds of work. Others will rely on their perspective.

 During meetings like Sprint Planning in the Scrum Method, teams get together to agree to the shared outcome with Sprint Goals. The Scrum Master helps teammates assign themselves work based on goals. They all self-commit to who's responsible, who's accountable, who's consulted, and who's informed in the work.

No one else tells them what to do, or assigns them work.

 They must self-commit. If they commit to work in their own function, great! If they self-commit to work outside of their function, they should be supported!

This is when the team cross-functionally spans across different roles if they want to do so.

The important distinction is this: the team has the capabilities to span across any function while performing work, and they may need to do so in their daily cross-functional work together.

 Someone might get sick. Someone might leave the team. Someone might be busy with other things.

 That's ok! You have a cross-functional team! No one is siloed. The important thing is for the team to not wait. They are a psychologically safe, self-organized team, and the people who are not in those functions can also do all kinds of other work if they are in a supported environment.

Deliverables for Cross-Functional Work

Agile teams maintain a deliverable called a RACI chart (which stands for "Responsible, Accountable, Consulted, Informed") to map out a team's desired functional activities based on the needed tasks.

The chart will change every week because the heist team contributes to different work every week. Team members maintain the details. No one dictates this. The team gets together to agree and build consensus about who does what tasks. This deliverable helps cross-functional teams set expectations across the team.

Learn more about this in the Agile Deliverables section of the Agile Handbook.

Credit: Tech Fleet
https://youtu.be/VvUi6MJNeTU
The Agile team is like the team assembled for the perfect heist. Credit: Tech Fleet.