Scrum is an agile system for making software. It has a few key events and artefacts that help guide the project and make it easier for the Scrum team to work together. Here are the important events and things that happen in Scrum:
Scrum Events:
Sprint Planning: This is the event that starts a sprint. The work for the next sprint is planned by the Scrum team, which is made up of the Product Owner and the Development Team. They talk about the goal of the sprint, choose the items from the product list that will be worked on, and decide what tasks need to be done to finish those items.
2. Daily Scrum: Also called the “daily stand-up,” this short meeting happens every day and helps the Development Team coordinate their work. Every person of the team talks about what they’ve done since the last daily scrum, what they plan to do next, and any problems they’re having. The focus is on cooperation and figuring out where problems or dependencies might come from.
3. Sprint Review: At the end of each sprint, the Scrum team holds a sprint review to show stakeholders the work that has been done, get feedback, and talk about how the product list might need to be changed. The Product Owner and the Development Team work together to look at the work that has been done so far and decide whether or not to accept it.
4. Sprint Retrospective: After the sprint review, the Scrum team has a retrospective to think about how the sprint went and find ways to make it better. They talk about what went well and what could be improved, and then they take steps to make the next sprint even better. The reflection helps people keep learning and changing.
5. Sprint: A sprint is a set amount of time, usually between one and four weeks, in which the Development Team works to finish the chosen items from the product backlog. At the end of each sprint, the team works together and organises itself to create a piece of the product that could be released.
Artefacts of Scrum:
Product Backlog: The product backlog is a list of all the features, improvements, and bug fixes that people want to see in a product, in order of how important they are. It shows what the Product Owner has written down about the product’s needs and goals. As new information and reviews come in, the product backlog changes and gets better.
Sprint Backlog: The sprint backlog is a subset of the product backlog items chosen for a specific sprint. It shows how much work the Development Team plans to do during the sprint. The team breaks down the things on the product backlog into smaller tasks and estimates how much work it will take to finish each one.
Increment: At the end of each sprint, the Scrum team gives you a piece of the product that could be shipped. The increment is the sum of all the product backlog items that were finished during the sprint and then tested to make sure they met the team’s meaning of “done.” The increase should be able to be used and could be released.
4. Burndown Chart: A burndown chart is a picture of how much work is left in a sprint or project over time. It shows how far along the sprint backlog or the whole project backlog is in being finished. It helps the team and other people involved see if they are on track to reach their goals and makes it easier for them to make decisions.
In Scrum, these events and artefacts provide organisation, transparency, and regular chances to look at and change things. They help people talk to each other, work together, and build things in small steps. This lets the Scrum team give value to stakeholders in a timely and flexible way.
