This is a very basic question but I don't see any answers on it yet.
Scenario: We did sprint planning and I noticed some one saying
Not all developers have a task to do. We need to add more tasks so that everybody has work.
I have a problem with that for the following reasons:
- If our velocity is 60 and you add tasks so that everybody has work you may end up with going way over your average velocity, you are setting yourself up for failure.
- With agile I would rather promote peer programming instead of everybody doing a task and when the sprint ends we have more tasks that is in development than those that are closed.
Idea Maybe stories should be split so that each team member has a task but in all they are working towards the same goal.
Question: Do you give each team member a user story or do you plan according to the velocity and then the team should work together to deliver a potentially releasable sprint rather than a half completed sprint?
Do you have experience in this and how did you deal with it?