Scrum Master requiring PO's approval

I have some concerns if the first time the Product Owner is seeing the functionality is with the stakeholders during the Sprint Review. 

Shouldn't the PO know what is "Done' and "Not Done" going into the Review? 

Tony actually it is the "scrum master" who's asking the PO for his approval. The PO is actually siding with me and says that he just needs to provide his feedback on the increment and probably add some new PBIs if neccessary. 

Ah I see, I guess I'd be curious what this Scrum Master feels is being accomplished by having another approval of "Done" work by the Product Owner especially since it sounds like your PO does not see the value in what is being asked of him. 

I could, however, see the PO approving certain Product Backlog Items for release after the Sprint Review but that doesn't seem to be what is being asked. 

Well if the story has already been  pulled  onto a sprint backlog for the increment, then it has  clearly "passed" the   "definition of ready" . The PO is the person who is grooming /refining the PB and ensure's that the stories are  in true "ready ready" status.   Once "done" the PO can release or not release the increment.  

Not sure, why a scrum master is wanting "Approval" of stories  after review event. 

Is the SM asking that all work remain open even if finished, and then closed after Sprint Review?

During the Sprint the PO can approve stories as they are "Done". Should have at least approved all the finished work before going into the Sprint Review.

The purpose of the Sprint Review is to demonstrate the completion of the Sprint Goal and that's when "The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done"". It's about ensuring expectations were met. If the PO hasn't approved prior to Sprint Review, how could the PO be able to explain what is/isn't "Done"?

Based on feedback that comes from the Stakeholders, create new tickets and/or update one's that have not started yet. There shouldn't be a need for any other Approvals. 

How can I convince a fellow scrum master bec he keeps on insisting that user stories after sprint review should be approved by the PO.

Approved for what, exactly?

@Tony and Ian: The user stories are just to be approved if it has "passed" the PO's "liking". The software is not on prod yet. If the question was should the PO be approving which stories should be released, i would probably have a different sentiment.

@John: I agree. The output of the Sprint Review is an updated product backlog based on the "feedback" we gained from the discussion.

@Peter: I told him that it would be better to include "PO Approval" in the DoD but he said it is not the right way.

The user stories are just to be approved if it has "passed" the PO's "liking".

Why wait until a Sprint Review for that? Why allow wasted effort to accumulate until no time is left in the Sprint? How could a PO possibly reconcile such poor collaboration, and lack of timely inspection and adaptation, with the maximizing of value?

@Peter: I told him that it would be better to include "PO Approval" in the DoD but he said it is not the right way.

Interesting, I have come across something similar. Not sure if it is right or wrong but curious to know what others think of this practice. Sometimes, I feel a PO approval, tends to become a superficial practice because the PO already knows the work is done and just has to move the Backlog item to final column.

Adding PO Approval to the DoD is not a good practice in my opinion. The DoD should only contain things that are in control of the Dev team. I don't think "PO Approval" is in control of the dev team.

Approved for what, exactly?

 

Ok I am going to Echo @Ian's comments.  What is supposed to happen once a story has been "approved"  ?