104
edits
2023-2024 Qubo Software Projects: Difference between revisions
→Spring Overall Goals
|
'''Deadlines.''' Leads will work with teams to develop a detailed semester plan that includes estimated deadlines. The focus will be on becoming competition-ready; nice-to-haves should be separated or removed entirely from the plan. Aiming for a Minimum Viable Product. Both so that we can test early and often, and so that we have something nice working at competition.
However, we have a large team. We do not need to stop working on longer-term projects. It will mainly be that urgent and key projects will build a minimal, rather than aspirational, plan. So for example the GUI has the potential to greatly increase testing and competition efficiency, but it is not 100% necessary; the GUI plan won't have to be as minimal as the controls plan. At the same time, there may be aspirational tasks on controls that a subteam is working on; but we also need to get something simple working quickly, so that we can start testing.
Missing a deadline is not the end of the world. The main goal is to be realistic about what we can accomplish within the time we have. If we are not progressing as fast as we hoped, then we'll have to remove something non-essential from the plan.
Look for easy points in RoboSub tasks. Focus on reliability rather than having many features.
'''Keep the bus factor and integration hell in mind.''' We're not sure on the best ways to do this. If you have ideas or experience, let us know!
Large teams often take longer to finish a task; there's only so many things to do. But also if someone has schedule conflicts, how can we be ready to pick up what they were working on?
Pair programming? Detailed plans with small, concrete tasks?
== Autonomy ==
| |||