[GreyingJay]

I see the benefits mostly in breaking down the big tasks into smaller, manageable sprints each with smaller stories, broken further into tasks. At work, a task should be something that one developer could do in a day or two. A sprint would be about two weeks.

For FRC, perhaps a sprint is a week, maybe two. A task could be a chunk of work that one student could do in one build meeting, whether that's a 3-hour evening or an 8-hour day or however your team works.

For example, your first sprint could have three stories and look something like:

Sprint 1:
- Assemble the KOP chassis
--- Cut the frame pieces to size
--- Assemble the frame and cross pieces
--- Assemble motors and gearboxes

- Wire up the control system
--- Build battery cable and circuit breaker connector
--- Connect the PCM, VRM, PDP
--- Wire the RoboRio power and CAN
--- Connect the bridge
--- Connect the motor controllers

- Prototype mechanism idea
--- Build plywood frame
--- Build wheel and axle driven by drill motor
--- Experiments to determine best placement