Should we add more items in a sprint if there is items that are not completed but a developer is open.
Lets say we the development team are made up of 5 team members and we have the following sprint backlog with an average velocity of 29SP and we are currently halfway in a 2 week sprint:
Sprint Backlog - Login 8SP State: In Development - Add User 12SP State: Code Review - Update User 3SP State: Done - Remove User 5SP State: In Development Product Backlog - Save User 2SP State: Ready - ...More Stories...
Story 3 was just completed and team is still busy with the rest of the stories should we rather:
- Swarm/Buddy Program to finish up sprint (I prefer) or
- Can we add another story (Small Story e.g 2SP) for the open developer because all of the other team members are busy with an item
My opinion is to use methods such as XP, Buddy Programming or Swarming to finish the sprint commitment (if they have finished all the items on their plate they can certainly pull in more work as the team deems OK) and if there is time left, they may add another item to sprint backlog.
What is your opinion and how did you deal with this?
(I know what I should do as well is bring this up in retro to understand why did "under commit" or why is the stories over sized etc.)