The Scrum Master is responsible for ensuring the team follows Agile principles, removing impediments, and facilitating effective communication.

The Product Owner is responsible for defining and prioritizing user stories, representing the customer's needs.

The Product Owner owns and manages the product backlog, prioritizing and refining user stories.

A visual board in Kanban helps visualize the workflow, track the progress of tasks, and identify bottlenecks.

The Scrum Master facilitates sprint retrospectives, where the team reflects on the sprint, identifies areas for improvement, and plans for the next sprint.

The goal of a sprint is to deliver a potentially shippable product increment that provides value to the customer.

In Scrum, the recommended sprint duration is typically 2 to 4 weeks, although it can vary based on the team and project.

The Development Team collectively estimates the effort and complexity of user stories during sprint planning.

The daily stand-up meeting is a short meeting where team members share their progress, challenges, and plans for the day.

The Scrum Master is responsible for ensuring that the team follows Agile principles and practices, removing impediments, and facilitating effective communication.

The sprint backlog contains the list of tasks and activities that the Development Team commits to completing during the current sprint.

Swimlanes in Kanban represent different stages or phases of the workflow, allowing for easy visualization of the progress of tasks through the process.

The Product Owner is responsible for accepting or rejecting user stories during sprint planning, ensuring that they align with the product vision and goals.

A burndown chart is a graphical representation that shows the amount of work remaining in a sprint over time.

The Development Team is responsible for developing and delivering potentially shippable product increments at the end of each sprint.