Work still not completed even after some sprints

I am a newbie myself.

1. did you do a sprint retrospective? what were the findings of the teams for the impediments faced?
2. did you try reducing the velocity of a sprint by choosing fewer estimation points for a sprint?

Hi Daniel,
what do you mean with "on last day"? What does the team say, why they didn't finish them? Are there impediments? Are the stories too big and should be decomposed? Are they not able to fulfill the definition of done without external help? Is there even a definition of done? I think we need a bit more information to help you.

Hi Daniel,

This is indeed quite broad. Agree with Ludwig.

Some more answers that may help --

A) What is your role on the Scrum Team?
B) How long are the sprint cycles?
C) How many sprints have passed?
D) How large is the team?

Are people over estimating what they believe they can achieve in a sprint? maybe they need to start breaking user stories down further. Also, are there external dependencies that are stopping the team complete their tasks - this has caught me out in the past!

I too worked on a team in the past and we did not complete all stories in the sprint.

Within the Scrum Framework it is safe to fail. As this highlights bottle necks with in the process.

I suggested we re visit our Definition of Ready and use the INVEST Model

I Independent The user story should be self-contained, in a way that there is no inherent dependency on another user story.
N Negotiable User stories, up until they are part of an iteration, can always be changed and rewritten.
V Valuable A user story must deliver value to the end user.
E Estimatable You must always be able to estimate the size of a user story.
S Scalable (small sized) User stories should not be so big as to become impossible to plan/task/prioritize with a certain level of certainty.
T Testable The user story or its related description must provide the necessary information to make test development possible

Some Scrum team will bring in stories knowing they will not be completed, which will then make the bottle necks transparent, so that the impediments can be address by the Scrum Master.

If the Scrum Team is newly forming then most new Scrum Teams do fail at first, and then after a couple of sprints they start to deliver and reach an achievable velocity.

When Scrum teams are formed or new people join a Scrum team the following phases:

Forming
Storming
Norming
Performing

> My team has been realizing that they have not
> finished even a single story on last day since past few Sprints.

This sounds like a team without a sprint plan. During Sprint Planning, how do team members agree to measure Sprint progress? For example, do they identify and prioritize sized tasks against which a burndown can be tracked?