Team Restructuring Proposal
- Tommy Neidlein
Status | Draft In review Accepted Rejected |
|---|---|
Proposer(s) | @Tommy Neidlein |
Date Submitted for Review | 10/04/2022 |
Date of Implementation |
|
Description of Proposal
FOR NEXT SEMESTER~
Instead of 11 different teams, there would be 5. Each team would focus on a specific area of the rocket. Propulsion focuses on design, analysis, and casting of solid rocket motors. Mechanisms focuses on systems that recover the rocket and facilitate staging. Structures designs and analyzes the primary structures of the rocket, and serves as the interface between all other components. Avionics focuses on electrical and software skills to create a custom flight computer and fly other commercial flight computers for independent verification. They also work closely with structures and mechanisms to design a payload bay for their electronics. The operations team does not have a direct lead, instead having a PM serve as their point of contact. It includes all other subteams that either directly interface with multiple other subteams or exist mostly in a vacuum.
Project Managers are experienced leads who help guide the whole team. Their role is identical to theirs now, where they focus on nontechnical matters, seeking advice from the Project Engineers when they want technical input. For proposals, the PMs get a single vote, even if there are two of them.
Project Engineers are former team leads who still want to be active in the project, but want to give younger members the opportunity to lead teams. PE numbers are not capped, although PEs are expected to attend meetings. They are more active than an advisor or mentor, for example. They exist because it provides a reason for senior members of the team to continue playing an active role. For proposals, they do not have voting power, but they are welcome to voice their opinions.
Primary teams are responsible for a segment of hardware or software. The four main primary teams are each focused on a specific skillset and deliverables that match those skills. Having less leads reduces the number of interfaces that need to exist between hardware, and simplifies communication. Primary teams can have Systems Reps, if HA decides they want those to continue. The operations team does not have a lead, as they are directly managed by the PMs. For proposals, each team gets one vote, with the operations team getting two votes, one is split between the Business, Systems, and IT teams, the other is split between Flight Modeling and Manufacturing. If the FM and Manu teams are in a tie, the PMs get to determine where their vote goes.
Specialist teams have skillsets that are not beholden to specific hardware. They perform analyses, raise funds, and manufacture other teams hardware. Generally, they are the support structure of (usually) upperclassmen who help the primary teams make their hardware a reality. Those outside of the operations team do not receive votes, and work with their lead to get their opinions across in proposals.
Responsible engineers are generally the newest members to teams, and do not formally lead any other students. Their job is to serve as a point of contact for systems that integrate with them. They also advocate for their hardware by reviewing all documentation for thoroughness and correctness. Each piece of hardware has an RE, but REs can be responsible for multiple pieces of hardware on the vehicle. They can also be leads of specialist or primary teams. REs cannot be a PM or PE. They do not get votes on proposals, although are welcome to attend leads meetings.
General members work inside this structure. They can become REs or leads by applications. They can also submit proposals and attend leads meetings.
Pros and Cons of Implementing the Proposal
Pros | Cons |
|---|---|
Less silo’s, so it is easier to interface between primary teams | Some teams transition to specialist teams, which may make some leads feel undervalued |
Clear characteristics for what makes a primary team and specialist team | Requires work to fit existing leads to this structure |
Easier for new students to choose their subteam, because there’s less choices |
|
Purpose of Proposal
Currently on PSP HA, there are 21 leads for 11 different subteams. Teams also vary greatly in size and scope. By somewhat equalizing the sizes of primary teams, and clearly documenting exactly what the intentions and interfaces between these teams are, hardware can be more easily delivered. The large number of teams on HA also presents issues for new members when it comes time to decide which team they would like to join. It silos information and work, making it more difficult for people to work together and be on the same page.
Plan for Action
Leads need to vote :))