Great. You are unbelievable in how you sort of get it all together in a small place. Scrum-poetry!

Yeah, I basically took all the prio 1 stuff from the old checklist list and subdivided those into categories. I intentionally left most of the old prio 2 and 3 stuff out of the new checklist because I wanted it to be short, concise, and fit on a single page. The prio 2 & 3 stuff was also very much more subjective than the prio 1 stuff. I'm considering maybe creating a "backside" with the prio 2 & 3 stuff, if enough people ask for it.

I'm trying to decide what to put on the backside. Either a scrum overview picture, or more checklist stuff (the stuff that was priority 2 on the old checklist).

Thanks Alex! I put a link to the Russian version from http://www.crisp.se/scrum/checklist

Because many of the most important problems are related to communication between the team and customers/users/stakeholders. The PO has an instrumental role in that. With the PO present, we increases the likelihood of constructive problem solving and reduce the likelihood of "It was the PO's fault" or "If only the PO would xyz".

It's the first item on the list. "Delivers working, TESTED software every 4 weeks or less". Other than that, Scrum doesn't define *how* testing is done, that is up to the team.