+1 that Scrum or an Agile software design methodology does not exactly match up with an FRC project.
I've been on a number of Agile software projects where the project manager used VersionOne to assign tasks, review task progress and to record task completion. You could run your build as a 6 week sprint and add redesign activities as needed.
The software team would hold brief daily meetings and weekly meetings to insure each professional was focused on accomplishing their task so the parts could be combined into the finished product at a defined point in time.
On my team not every student can attend every meeting and sometimes we have to train another student to work on a task to keep it moving.
If you have enough students and mentors, I would suggest planning out the next meetings activities and kitting the needed parts. By this I mean if you need to install a pneumatic cylinder, find all the needed parts and bag them together. Then at the next build meeting, you can hand the bag and the task to a student. If they need some training, have them stop and ask.
I've done this time permitting and it works great. It allows me to engage a far larger number of students at the same time. If your students already know how to find the parts and how to install them, that is great and you can skip the kitting!
To make these parts easy to find, I like to tape the bags to a glass window. Tape works great and its a visual reminder of what we have to get done.
It doesn't help with documenting project status, that would have to be a separate manual activity.
If you want to try the software approach, here are some options:
https://www.versionone.com/
Gantt Charts to visually map project activities
https://www.google.com/search?q=gant...utf-8&oe=utf-8
http://agilescout.com/best-agile-scrum-tools/
Dave