Team Structure on Tech Fleet Projects
Learn all about how we structure team training in Tech Fleet.
Last updated
Learn all about how we structure team training in Tech Fleet.
Last updated
Project structure is set up on Tech Fleet projects so that there's redundancy in roles. Leads who are taking leadership positions for the first time can sign up with co-leads to help mentor them as a servant leader, or contribute to work alongside each other as equals.
All leads and co-leads are equals on teams. No lead is "above" another lead or co-lead. No lead is a "above" apprentices either. Apprentices and leads are on equal footing when it comes to work; everyone pitches in to what they commit to each week in sprint planning sessions, lead and apprentice both. On the team you are one collective team doing work together, and roles matter less when progressing as a whole. You will experience different things on different Tech Fleet projects, as it should be in the real world on Agile teams who fit Agile to their context.
Each teammate is able to float across responsibilities as part of a cross-functional team. Each team position has daily expectations for responsibilities under each role they play. Here is a summary:
Product Strategy function == Scrum Master commitment + Business Analyst commitment + Product Owner commitment + Product Manager commitment + UX Research commitment
UX Design function == UX design commitment + UX Research commitment
UX Research function == UX research commitment + UX Research commitment
UX Writing function == UX writing commitment + UX Research commitment
Project Management function == Scrum Master commitment + Project Manager commitment + Account Management commitment
Development function == Front-end developer commitment + Back-end developer commitment + QA commitment
Solution Architecture function == Information Security commitment + Solutions architect commitment