This concept is important as it states that the Scrum artifacts should be transparent in a way that all the stakeholders can understand what's going on. A lack of transparency could lead to wrong decisions affecting the outcome of a project. The three Scrum roles, Product Owner, Scrum Master, and Development Team, work together to ensure the transparency of the artifacts.

The Scrum Product Backlog is essentially a to-do list for the project managed by the Product Owner. It consists of all the features, functionalities, enhancements and fixes that form the changes to be made in the product in future releases. The items in the product backlog are usually written in the form of user stories and are ordered by priority. The product backlog is a living document and is subject to changes and updates as the project grows and customer needs or market conditions change. The Scrum team and the product owner refine the backlog regularly to keep it updated and relevant.

Scrum Sprint Backlog is the set of product backlog items selected for the sprint, plus a plan for delivering the product increment and realizing the Sprint Goal. It is a forecast by the Development Team about what functionalities will be made available in the next increment and the work needed to deliver that functionality as a 'Done' increment. It is owned exclusively by the development team. The Sprint Backlog only contains items that the team agrees it can complete during the sprint, and it becomes a highly visible, real-time picture of the team’s work.

The Incrment in Scrum refers to the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. The increment is a step toward a vision or goal. The increment should be in usable condition regardless of whether the Product Owner decides to release it. It must be 'Done', which means it must be in usable condition and meet the Scrum Team’s definition of 'Done'. An increment is a body of inspectable, done work that supports empirical transparency.

The Sprint Goal is an objective set for the Sprint aimed to provide guidance to the Development Team on why it is building the Increment. It is a short description of what the team plans to achieve during the Sprint. It is created during the Sprint Planning meeting and provides a shared goal that encourages the Development Team to work together rather than on separate initiatives. This goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

The Definition of Done (DoD) in Scrum is a shared understanding of what it means for work to be complete and ensures that everyone has the same understanding of 'done'. Everyone must understand what 'done' means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is paramount when it comes to the increment being transparent.

Burn down Charts are graphical representations of work left to do in a project versus time. The horizontal axis of the burn down chart shows the days in a Sprint, while the vertical axis shows the amount of work remaining. Burn down charts are used to project how quickly the team is working through the Product Backlog, and provide a clear and simple visual about the status of the current sprint.

The Scrum Product Owner is a key role in Scrum that is responsible for maximizing the value of the product resulting from the work of the development team. The Product Owner is the one who maintains the Product Backlog and ensures that everyone in the Scrum Team understands the items on the backlog. He or she is also responsible for prioritizing these items based on the overall strategy and business objectives. The Product Owner works closely with the Scrum Master and the development team to ensure that they understand what needs to be done.

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. The Scrum Team, being self-organizing, chooses how best to accomplish their work, rather than being directed by others outside the team. The team model in Scrum is designed to optimize flexibility, creativity and productivity. The Scrum Team delivers products iteratively and incrementally, maximizing opportunities for feedback.

Scrum User Stories are a description of a software feature from an end-user perspective. It describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement. The team discusses the user story to build a shared understanding of the problem and come up with a collaborative solution. User stories can be used as a part of Scrum Product Backlog to understand what users need from the product.

The Scrum Burndown Chart is a graphical representation of work left to do versus time. It is an effective way of ascertaining at a glance whether the Scrum Team's progress is on track to complete the work. The x-axis represents time, and the y-axis represents tasks. Over time, the chart should trend downwards, reflecting the 'burning down' of tasks as they are completed, hence the name. The Burndown Chart allows real-time adjustment to keep a project on track. It promotes transparency and clarity among Scrum Team members and stakeholders about what has been accomplished and what work remains.

Scrum Daily Standup, also called Daily Scrum, is a short meeting that takes place every working day typically in the morning. It lasts no more than 15 minutes where each team member answers three questions: What did I do yesterday? What will I do today? Are there any impediments in my way? The purpose is to synchronize the activities of team members and identify any issues that need to be addressed to keep the project moving forward. It's critical to the Scrum framework because it helps to ensure that everyone is on the same page and fosters team collaboration and problem solving.

A Burn Down Chart represents the work left to do versus time. It is a graphic representation of the work left to do versus the time. It's a way for the team to manage its progress and respond accordingly. A typical burn down chart contains two axis; the vertical axis represents the amount of work left to do, while the horizontal axis represents time. The burn down chart tracks the progress of the Sprint and provides a simple view about the remaining work that can be used to predict when all the work will be completed.

Scrum Velocity is a metric used in Scrum to calculate the amount of work a team can tackle during a single Sprint. The velocity is calculated at the end of the Sprint by summing up the Estimates of all fully completed User Stories. It is used for predicting how much work can be accomplished in future sprints and is a key tool in release planning. It can be influenced by team changes, system issues, and varying story complexity. Over several sprints, a team's velocity usually stabilizes and can be used to forecast future work.

In Scrum, Tasks define the work that needs to be done to complete a Product Backlog Item (PBI) or a Sprint Backlog Item. During a Sprint Planning meeting, the team selects some product backlog items, breaks them into tasks and estimates effort to complete each task. Each task should be small enough to be comfortably completed within a single day of work. Through Scrum tasks, team remains focused and it allows for better tracking and reporting as it's easier to gauge how close the team is to finishing the entire Product Backlog Item.