It is an informal event to discuss team work, so no output is needed

Meeting notes

List of action items

Sprint Goal

All of the above

All tasks to be done during the Sprint and responsible person for each of them

Ground rules for cooperation inside the team

No more that 2 hours for each week of Sprint length

No more that 1 hour for each week of Sprint length

No less that 1 hour for each week of Sprint length

No less that 2 hours for each week of Sprint length

It depends on the Scrum team size

To inspect progress toward the Sprint Goal and how progress is trending toward

completing the work in the Sprint Backlog

All of the above

To get status updates from the team

To successfully manage team work

a 1-2 weeks during which all Scrum events take place

a time-box of one month or less during which a "Done", useable, and potentially releasable

product Increment is created

a time-box of 2 weeks or less during which a "Done", useable, and potentially releasable

product Increment is created

Change requests

Feedback on the presented Increment

List of accepted or rejected PBIs

Review the timeline, potential capabilities, and marketplace for the next anticipated

release of the product

All of the above