Empiricism requires transparency for an effective inspection to occur.
What artifact is inspected during the Daily Scrum?
What makes the artifact transparent?

How is transparency impacted by technical debt?
What is the correlation between technical debt and velocity?

Scrum is an empirical process. For empiricism to work, all artifacts must be transparent.
Why is transparency important?
Give an example of how the actions of a Developer or Product Owner might contribute to decreased transparency.
For the example provided, what would you do as a Scrum Master to help increase transparency?

“Technical debt is the sole concern of the Developers”. As a Scrum Master, do you agree with this statement? Why or why not?

Two Scrum Teams work on the same product. They pull from one Product Backlog and develop in the same codebase. The Product Owner and the Scrum Master perform their roles for both teams. At the combined Sprint Review each team shows the work they’ve done from their separate code branch.
What is the impact of this situation?
What is the Scrum Master’s accountability in this?

Your organization uses a product that is architected with multiple specific application layers (for example, front end, middle tier, back end, and interfaces).
Discuss several ways of organizing Scrum Teams for a major enhancement project on this product.
Discuss the advantages and disadvantages of each.