Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed.  The three pillars of empiricism in Scrum are transparency, inspection and adaption.  We must keep this in mind when conducting planning, daily Scrums, reviews and retrospectives.
Sprint Planning looks to answer what can be delivered in the next Increment during the upcoming Sprint, and how the work will be done. 
Inputs to planning:
The inputs must be transparent to the team and understood. It is the role of the Product Owner to ensure this during Sprint Planning.
Outputs of planning (Sprint Backlog):
The outputs must be transparent to the team with the Product Owner understanding what will be delivered within the Increment. The planning event provides opportunity for inspection and adaptation of work.
The purpose of the Daily Scrum is to inspect progress towards the Sprint Goal and adapt the Sprint Backlog as necessary.  The Daily Scrum is not a status report meeting but rather an opportunity to re-plan based on progress.
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.  Work is presented by the team for review by key stakeholders. The review provides an opportunity to reflect upon the Increment towards the Product Goal and adjust accordingly.
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.  The team inspects aspects of delivery (e.g., individuals, interactions, processes, tools) seeking areas for improvement. The team can also inspect previous improvement ideas and the impacts of their implementation.
Throughout all of these events we consistently apply the pillars of empiricism relating to the artefacts for that event. It is helpful to remind ourselves of these each time we conduct events.
If we introduce other events to assist with delivery or business operations, we want to continue to apply these pillars.