DevOps and project management are very separate practices and knowledge domains that can borrow from each other. Any other answer is likely an opinion about process implementation.
DevOps Isn't a Synonym for Agile Project Management
DevOps is primarily a culture of collaboration between diverse roles such as requirements analysis, testing, development, deployment, operations, and maintenance. To a lesser extent, it is also a set of tools and practices for enabling rapid feedback for collaboration, and providing delivery and deployment pipelines.
Project management as a practice or profession is the art of planning and controlling projects. To the extent that DevOps provides a framework for product delivery, and to the extent that it creates feedback loops and process controls, a project manager can leverage the framework and controls when planning, organization, or measuring the project. However, DevOps as a culture or as a tool chain has no defined role for a project manager, making the question as asked confusing and vague.
You can implement a project without agile frameworks or practices. Likewise, a given framework like Scrum or Kanban does not rely on DevOps culture, tools, or practices to provide process controls. Borrowing sensible tools and practices from DevOps to create feedback or processs controls within an agile framework is often wise, though.
Even though there is no defined role titled "Project Manager" in DevOps culture or agile frameworks, that doesn't mean a project manager can't leverage them. However, if you're going outside the formal definitions, then your mileage may vary.