Sprint planning and Testing for Tasks and User Stories.

Have you done any root-cause analysis around the reasons why some story development is not being completed until the end of the sprint?   How large are the stories?

Are the team sufficiently focused on completing one story at a time, so that testing occurs early and throughout the Sprint?

If the team is only designing the work for the first days ; then coding the next days ; then trying to test the last days, they are just working in small waterfall cycle with phases, but not as a whole rugby scrum team carrying the ball forward for a try.

Are they discussed in Retrospective meetings about any impediments causing delay in testing to last day.

Thank you Timothy, Olivier and Ian for always replying my post.

The team is struggling only for those User Stories which are completed on last two days of sprint completion, as testing remain pending for those User Stories.

If we keep buffer for testing coverage, the other developers are not utilized for that last days.

Thank you Timothy for suggesting RCA.

Thank you Ian for suggesting focused work.

Thank you Olivier. We will find out if we are doing small waterfall cycle.

If we keep buffer for testing coverage, the other developers are not utilized for that last days.

How so? If the testing is not done yet, the team hasn't finished the product increment. So all the tea embers must collaborate to finish it.