Is the Product Owner managing a team acceptable?

Unsure if there is a "best practice" answer in regards to Scrum, as the Scrum Guide is quite clear on the subject:

• They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality
• The Development Team self-organizes to undertake the work in the Sprint Backlog
• the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team
• Every day, the Development Team should understand how it intends to work together as a self-organizing team

So in your opinion, can the above take place if the Development Team is "managed" by the PO?

Is the Product Owner managing a team acceptable?

It would indicate a lower level of aptitude within a self-organizing team. Would that be acceptable?

@Timothy's answer is from the Scrum Guide and focuses on the Development Team. But I think you may be referring to the Scrum Team as a whole.  There is nothing in the Scrum Guide that actually mentions management at all.  I believe that is intentional because Scrum is built on self-organization, self-directed teams (entire teams not just Development).  If someone "manages" that implies control which is against the servant-leader model of agile.

My current company has manager roles for the individuals. They help in career development and those obligatory "annual reviews".  But they play no role in how the individuals participate in the the teams, how the teams work or even what the individuals do with in the teams. 

No one manages a team in Scrum or agile. They manage themselves. 

Hi Chris, 

Is that a real case? Can you give some examples of how the Product Owner you are referring to manages the Scrum Team or Development Team? 

No one manages a team in Scrum or agile. They manage themselves. 

Correct, usually in the terms of organizing. There are a couple of levels to this; self-organizing, self-managing and self-directing. Whilst asuming self-organization needs no explanation, the other side of the spectrum, directing, encompasses the team having their own budget, doing their personal development, providing their own salary raises, training, direction for the product at hand, etc. 

Best practices in Scrum don't really exist, I guess. Best practices is like: eating soup with a spoon is best practice. Using a hammer for slamming in nails is a best practice. But due to the complex environments with Scrum, there are no best practices. Emergent practices, yes. My apologies for being the "know-it-all", just venting my vision on best practices:D

Thanks guys. I agree with the above comments, in the scripture of the Scrum Guide the PO is supposed to guide and provide clarity to the Dev Team on PBIs, and probably be at a distance (so to speak) from the Dev Team during the Sprint.

Managing does seem to go against being self-organising so.

Think I have just over thought this one.