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

The team has all competencies needed to accomplish the work without depending on

others not part of the team

There shouldn't be any specific area of knowledge for each team member

Developers need to be able to test and QC engineers have to be able to develop when

needed

Each team member has all skills needed to accomplish the work during the Sprint

Scrum team

Stakeholders

Project manager

Product Owner

Scrum Master

Stakeholders

Project manager

Product Owner

Scrum Master

Depends on the project needs and budget

7 plus-minus 2

9 plus-minus 2

3 to 9 people