Quote:
Originally Posted by jds2001
See this thread, starting at the post that I've linked (and maybe some above) for my thoughts on the topic.
TL;DR - I don't think full-on agile is appropriate for a FRC project. It's quite well suited when there are distinct iterations that you can "deliver". Another poster in that thread made the point that the requirements change very little once they're delivered (in 12 days now, can you believe it?!?!) |
I agree completely that full-on agile development wouldn't work that well for FRC, primarily due to the time concerns, but I do think that a modified version would be perfect for subteams who are adding more complex iterations to their basic prototypes. It would set clear deadlines to follow for sub-systems of the robot without creating an "all or nothing" approach to the system's functionality.
Some of the posts on the thread you linked mentioned a stand-up meeting in which all the teams gather to report on progress. I really like the idea of having these both at the beginning and end of meetings; it could really keep everyone focused on the end goal.