User Stories are a technique used to define product or system functionalities from the perspective of the end user. They provide a concise, simple description of a feature, told from the user's perspective, in a way that establishes value. Acceptance criteria, on the other hand, are conditions that are used to confirm when a User Story is completed and working as intended. It serves as an agreement between the Product Owner and Development Team, specifying functionality, design, and performance.

Customer-Centric Design is a strategy in agile development that places the customer at the center of design decisions. It requires an empathetic understanding of customer needs and involves the continuous evaluation of evolving user experiences. It also includes going beyond just asking what customers want, but observing their behaviors and understanding their pain points. Customer-Centric Design ensures that products are not only functional and reliable, but also usable, and delightful from a customer’s perspective.

The Product Owner is one of the key roles in Scrum and is responsible for defining and communicating the project vision. The Product Owner is typically the project's key stakeholder and has a vested interest in the project's outcome. They are responsible for defining the product backlog, ensuring the team understands the items in the product backlog to the level needed, and more. The Product Owner's decisions are visible in the content and ordering of the product backlog, and through the inspectable increment at the Sprint Review.

Sprint Review and Retrospective are two of the main events in Scrum methodology. Sprint Review is a meeting held at the end of the Sprint to inspect the increment and adapt the product backlog if needed. The Scrum Team presents the results of their work to stakeholders and progress towards the product goal is discussed. During the Sprint Retrospective, the team examines the past Sprint to learn and improve. They inspect how the last Sprint went with regards to individuals, the interactions, techniques, tools, and the Scrum process.

Backlog Refinement, basically, is a practice where the Product Owner and the Development teams collectively review items on the backlog to ensure that they are appropriately prepared and ordered in a way that makes them readily executable in future sprints. It provides richer, deeper detail so that the team can rapidly start delivering on those items in the next Sprint. This helps to keep the flow of valuable functionality to the customer while preserving team flexibility to best achieve goals in the near future.

The Scrum Master is a key role in Scrum, which is a servant-leadership position. The ultimate responsibility of the Scrum Master is to help the team in understanding and utilizing Scrum effectively. They are not involved in decision making but facilitates the team to reach consensus on their own. They help remove obstacles that the team might face in the course of their work. Furthermore, they ensure that the Scrum principles and values are followed within the team and by the organization.

The Scrum Framework is a lightweight and simple framework for effective team collaboration on complex products. It describes a set of tools and roles that work in concert to help teams structure and manage their work. Scrum employs an iterative, incremental approach to maximize predictability and control risk. It consists of Scrum Teams and their associated roles, events, artifacts, and rules, which are defined to bind them together to form the framework.

Empirical process control is a core principle of Scrum, which is based on the three pillars of transparency, inspection, and adaptation. Transparency ensures that aspects which affect the outcome is visible to those managing the outcomes. Inspection involves routinely checking these aspects to detect unwanted variances. Adaptation involves adjusting the process if one or more aspects deviate outside acceptable limits. This approach is ideal for complex work where the path to the goal cannot be fully predicted in advance. The empirical process allows the scrum team to adapt to changes and continuously improve the product and the working process.

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It is a commitment by the Development Team about what they aim to achieve during the sprint. It guides the Development Team on why it is building the increment. The Sprint Goal offers a target and purpose, facilitating decision-making and collaboration throughout the sprint. It promotes focus and creativity by providing the team with a target outcome.

Burndown Charts are visual tools used in Scrum to track the progress of a sprint or a release. They show how much work is left to be done versus the time left in the Sprint. Burndown Charts helps teams to monitor and maintain the pace of their work and make adjustments if necessary. It brings a clear understanding of their progress and whether the team is working efficiently or they need to speed up.

The Daily Stand-up is a short, everyday meeting where the development team members update each other about what they did the previous day, what they're planning to do today and whether there are any obstacles in their way. The Daily Stand-up helps promote quick decision-making, improves teamwork and ensures everyone on the team has a clear understanding of what’s going on. This process promotes self-organization of the Development Team and helps identify impediments for resolution.

Incremental Development is a core principle in Scrum where a large task is broken down into smaller tasks and then worked on and delivered incrementally. This provides the opportunity to review and adjust the product frequently, thus ensuring a high-quality product that meets user needs. This concept enables better risk management, quicker feedback loops and a potentially shorter time to market.