What do you do with programmers who fail a sprint?

Question

Project management

Hello! A couple of weeks ago, I got a job as a product manager in an outsourcing company. I like the work, tomorrow I will conduct the first sprint review and demonstration of the demo of the work done. But I feel that the demo will fail and some of the stated tasks will not be completed on time. Accordingly, I had a question for experienced products: what do you do with programmers who miss deadlines?
Initial data:
1) The project is the development of native mobile applications
2) I was assigned to the project in the middle of the first sprint
3) The scope of tasks from the backlog that were planned to be completed was determined by the programmers. The priority of tasks is not set by the customer. Work is performed on screens from the first screens to the end.

Answer 1

Do not rush, go through a couple more sprints, find out the real speed of the team ( https://www.scruminc.com/velocity/) maybe they failed the sprint not because they worked poorly, but made a mistake in the estimates. Decompose large tasks with the team into smaller ones. They are easier to evaluate accurately. And the task tracker will automatically sum them up for you and you will see the whole picture. Conduct daily statuses and find out what obstacles the developers have and what progress is happening in one day (what was done yesterday and is planned today). Work more closely with the team. If the team loses all the time and nothing improves, the first thing to do is to change the coach, if he could not set up or rebuild the team so that it wins.

Answer 2

Didn't understand. Did you get hired a couple of weeks ago, in the middle of a sprint?
1 So how long is your sprint?
2 If the backlog is adequate, and the scope was chosen only for the first sprint, you need to understand in retrospective what went wrong - whether they hurried up the scope and piled up an inadequate one, or they just merged it.
That is, since this is only the first sprint, it is the retrospective that will show what to do next. In fact, the first sprint is needed to determine how the team works. It's sad, of course, that they fail at the very first sprint, but this is not a tragedy - a retrospective, you realize the problem and see what to do next.

Answer 3

I agree with DevMan, a product manager cannot have a sense of time.
First, take a breath. You are not the first, and you are not the last who broke the deadlines.
Second, work with the facts. Who set the task? Who is responsible for implementation? Raise people, collect status. If I were you, I'd start doing this right now. Understand who failed, ask what is connected. Take it to the "pencil". Make it a habit not to collect status at the end of the sprint, but to make checkpoints when the situation can be corrected.