My experience is that the team is better off focusing on a smaller number of missions and being able to complete them (always depending on robot performance, of course) - rather than trying to do a large number and being only partly done with each one so there's no chance of success at the robot game. It's really exciting for the team if "what we learn" includes the knowledge that they can create a robot and program that actually accomplishes something. It's not about chasing a high score - more about showing themselves they can reach a goal.
I'd also encourage you to check out these blog posts by my co-coach Scott about how to decide how many missions to do (https://www.startingpoints.com/howmanymissions?category=firstlegoleague/robot/robot-strategy-and-techniques) and some tips for how to plan out those missions (https://www.startingpoints.com/mission-planning?category=firstlegoleague/robot/robot-strategy-and-techniques).
-- To UNSUBSCRIBE or CHANGE your settings, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list".
-- VADCFLL administrative announcements are sent via VADCFLL-ANNOUNCEMENTS-L. Visit https://listserv.jmu.edu/archives/vadcfll-ANNOUNCEMENTS-l.html to subscribe.