Good Scrum - How does it look like? 

 Realistic expectation from Scrum by all stakeholders including the Scrum team. All sprints may not meet their sprint goals 

Everyone in the scrum team understands scrum as defined in the scrum guide 

There is role clarity for the product owner, scrum master and the development team 

The product owner along with other key stakeholders have done the release planning 

Dependencies are pro-actively managed 

There is clarity on requirements  including the acceptance criteria, prior to the sprint planning meeting 

The whole team should have a common understanding of Definition Of Done (DoD)

Sufficient time & participation by the whole Scrum team during the planning meeting  (5 to 7 hours) 

Minimal disruption of the developers work with unscheduled meetings / work outside the sprint 

Ability of the team to self organize 

Proper conduct of the daily scrum (daily meetings)  (15 minutes) 

Proper conduct of the sprint review meeting 

Proper conduct of the sprint retrospective meeting 

Effective implementation of the corrective and preventive actions in the subsequent sprints 

Quantitative decision making (empiricism) - transparency of velocity