It can be fairly common for multiple team members to work concurrently on one story, so while it is hard for me to state "yes or no" definitively on whether you need to decompose further, I think it's fair to say your current situation could certainly be valid.
The answer of how to approach the issue of over-allocation in this scenario can often be found in process. An ideal scrum team will be mostly cross-functional, which should lead to most team members feeling somewhat comfortable performing most tasks on the project. If this is indeed the case, then it is often best to not assign work to individuals during iteration planning, but rather for the individuals to pull work from the iteration backlog as necessary throughout the sprint. In this way, so long as the team has capacity to complete the assigned stories the work should naturally distribute itself amongst the team members.
If the team is not yet cross-functional enough to work in this manner, and it is necessary to assign specific tasks to individuals up-front in the planning phase, then unfortunately the visibility within TeamPulse in regards to task estimates and allocations is somewhat lacking. Aside from breaking those tasks out into their own stories I cannot think of a suggestion on how else to gather this data from within TeamPulse. I will add this feedback into our backlog in hopes we can address it in future releases.
the Telerik team
Are you looking for the fastest way to get started with TeamPulse?
Do you want to be able to directly talk to our professionals and ask questions about the things that interest you?
Reserve a seat
for the TeamPulse Weekly Live Demo today!