In a case with limited people like 5, you need to go through an iterative process.
If you weight, distribute and assign the stories to be developed in a way that everyone is orchestrated well and you go in a 2-week sprint and normally you go through the following "steps"
- Unit Test
After unit tests, one of your resources finished the last story from sprint while others don't and for some reason there is 1 day or 2 days left. This idle resource what is suppossed to do?
In traditional approaches as everything is sequential mostly everyone finishes at the specific date or late than planned. Also in traditional, you risk to do rework and re-plan again, but how to manage that idle resource in a sprint. How do you track or do with those excellent story makers who finished before time?