By the way, the concept of a project manager in pure Scrum is not, but there is the role of a scrum master. Its task is to help comfortably go the way and get all the team members to the goal. He is a forger, psychologist, trainer, mentor, assistant, change agent, "alarm clock," and a reminder all rolled into one. His task is not to push, not to do all the work himself and not to allocate responsibilities, but to help, guide, and resolve issues that impede the development process.
In a Scrum book, the role of the scrum master is usually played by a separate employee. Our process is primarily modified, and the project manager acts as a scrum-master.
After the team is formed and all the formalities are observed, we can begin to work.
For a comfortable start of work, we devote a lot of time to creating a backlog. Product backlog - a list of requirements, stories, features, Wishlist, functionality, which the product owner arranges by the degree of importance, prioritizing after agreeing with stakeholders. The development team also has its voice in priority tasks on the advice of the team, you can add technical tasks and explain to the product owner why this is important. All team members are closely connected and take part in the discussion. Moreover, all requirements are described in a language that is understandable for business. Elements of this list are user stories, "user stories."