Scrum
The framework is named after a rugby formation and is frequently used in Agile software development. Everyone has a part to play. Product owner, Scrum Master, and Scrum development team are all Scrum roles in product development.
Product owner: This team member acts as a point of contact between the development team and the company's clients. The product owner is in charge of ensuring that the finished product's expectations have been conveyed and agreed upon.
Scrum master: This team member facilitates the scrum process. The Scrum Master is in charge of ensuring that Scrum best practices are followed and that the project progresses.
The Scrum development team is a collection of people that collaborate to create and test incremental releases of the final product.
The Scrum process
Scrum pushes practitioners to work with what they have and to evaluate what is and is not working on a regular basis. Meetings, referred to as Events, are used to communicate, which is a key element of the process. Scrum events include the following:
Daily Scrum - The Daily Scrum is a short stand-up meeting that takes place every day at the same time and place. The team analyzes work from the previous day and plans what work will be done in the next 24 hours at each meeting. This is the time for team members to raise any issues that may hinder the project from being completed.
Sprint Planning Meeting - The time range in which work must be finished is referred to as a Sprint, and it is typically 30 days. Everyone contributes to the goal-setting process, and at the end of the process, at least one increment (a useful piece of software) should be generated.
Sprint Review - This is the time to show off the increment.
Sprint Retrospective - After a Sprint, a meeting called a Sprint Retrospective is held. Everyone in this meeting reflects on the Sprint process. A team-building activity could also be included. Continuous improvement is a crucial goal of a Sprint Retrospective.
Scrum artifacts
An artifact is a piece of historical significance that deserves to be examined again. Artifacts are used in Scrum product development to track what has been completed and what is left on the to-do list. In Sprint Planning Meetings, Scrum artifacts like the product backlog, sprint backlog, product increment, and burn-down might be useful.
Product backlog - This refers to the items on the "to be done" list that have yet to be completed. The development team collaborates with the company owner during a product backlog grooming session to prioritize work that has been backlogged. During a process known as backlog refining, the product backlog can be fine-tuned.
Sprint backlog - Before selected product backlog items may be delivered, this is a list of tasks that must be done. These are broken down into user stories based on time
Product increment - This refers to everything that was completed during a Sprint, including all of the product backlog items, as well as everything that was developed in earlier Sprints. The product increment indicates how far the project has progressed
Burn-down - The burn-down is a visual indication of how much work is still left to be done. There is a Y-axis (work) and an X-axis (time) on a burn-down chart (time). The chart should ideally show a declining trend as the quantity of work left to perform decreases over time until it reaches zero.
Comments
Post a Comment