Scrum - tugosera/tralalero-tralala GitHub Wiki

Scrum is a popular agile framework used to manage and complete complex projects, primarily in software development, though it can be applied in other fields as well. It focuses on delivering small, incremental improvements in a project over a series of cycles called sprints. Scrum is based on the principles of transparency, inspection, and adaptation.

Here are the key components of Scrum:

1. Roles:

   • Product Owner: Responsible for defining the features of the product and ensuring that the team works on the most valuable tasks first.
   • Scrum Master: Acts as a facilitator to ensure that the team follows the Scrum process, removes obstacles, and helps with continuous improvement.
   • Development Team: A cross-functional group of professionals who work together to deliver the product increment.

2. Artifacts:

   • Product Backlog: A prioritized list of tasks or features that need to be completed for the project.
   • Sprint Backlog: A subset of tasks from the Product Backlog that the team commits to completing during the current sprint.
   • Increment: The work completed at the end of each sprint, adding new features or improvements to the product.

3. Events:

   • Sprint: A time-boxed period (usually 2-4 weeks) in which the team works to complete a set of tasks from the Sprint Backlog.
   • Sprint Planning: A meeting at the start of each sprint where the team decides which tasks to work on and how to approach them.
   • Daily Scrum (Standup): A short, daily meeting where team members discuss their progress, what they're working on, and any obstacles they face.
   • Sprint Review: A meeting at the end of the sprint where the team demonstrates the completed work to stakeholders.
   • Sprint Retrospective: A meeting to reflect on the sprint, discussing what went well, what didn’t, and how to improve in the next sprint.

The Scrum framework helps teams be more flexible and responsive to changes, and it encourages continuous improvement and collaboration among team members. It’s particularly popular in dynamic environments where requirements can evolve rapidly.