Agile Methodologies (Scrum, Kanban, XP)

Scrum is an Agile framework that focuses on delivering value in short iterations, called sprints. It emphasizes collaboration, transparency, and continuous improvement.

Kanban is an Agile methodology that emphasizes visualizing work, limiting work in progress, and continuously improving the workflow.

XP (Extreme Programming) is an Agile methodology that emphasizes pair programming, test-driven development, and continuous refactoring.

The Scrum Master is responsible for managing the project, facilitating ceremonies, and ensuring that the team follows Agile principles and practices.

The primary goal of a sprint in Scrum is to deliver a potentially shippable product increment, which means that the increment should be valuable to the customer and could be released to production.

Swimlanes in Kanban are used to represent different types of work, such as development, testing, or deployment.

XP's test-driven development approach emphasizes writing tests before writing code, ensuring that the code meets the requirements and works as expected.

The recommended length of a sprint in Scrum is 2 weeks, as it allows for enough time to complete meaningful work while maintaining a consistent cadence.

The Product Owner in Scrum is responsible for prioritizing user stories, representing the customer's needs, and ensuring that the team is building the right product.

WIP limits in Kanban are used to limit the amount of work in progress, preventing multitasking and ensuring that the team focuses on completing one task at a time.

Scrum emphasizes customer collaboration and feedback throughout the development process, with regular sprint reviews and retrospectives to gather feedback and make improvements.

The Development Team in Scrum is responsible for developing the software, including designing, implementing, and testing the product.

Pair programming in XP is primarily used to share knowledge and skills among team members, fostering collaboration and improving code quality.

XP emphasizes continuous refactoring and improving the design of the code, ensuring that the code remains maintainable and flexible.

Daily stand-up meetings in Kanban are primarily used to identify roadblocks and dependencies, ensuring that the team can address any issues and keep the workflow moving smoothly.