Closed ghost closed 7 years ago
One concern here is that one team can essentially assign another team work, without going through that team lead for approval.
All milestones will be worked out such that this issue does not arise. We will probably have a short meeting regarding this with the team leads on Saturday the 16th.
Often, milestones from one team require effort from another team to complete. For example, to make the drive system work, the electrical team needs the chassis from the mechanical team (at least partially). If the milestone is stated in such a way so as to remove this dependency (like running the system in simulation) then problems can be missed until too late.
Does anyone have thoughts on how to properly assign and track work on milestones that must cross team boundaries due to the integrated nature of the rover?