Scrum Framework
Last updated
Last updated
Scrum is an agile project management framework that uses a set of values, principles, and practices to assist teams in organizing and managing their work. Scrum enables individuals and teams to collaboratively and incrementally deliver value. The Scrum framework is made up of a Scrum Team, which includes a Product Owner, a Scrum Master, and Developers, each of whom has a specific set of responsibilities. There will be more explanation of scrum framework in the next sub-pages Scrum Concept and Scrum Roles.
Scrum artifacts are crucial sets of information that the scrum team uses to define the product and the work that needs to be done to achieve it. The product backlog, the sprint backlog, and the increment with your definition of "done" are the three artifacts in scrum.
Product Backlog: It is the major task list that has to be completed and is kept up to date by the product manager or owner. The input for the sprint backlog is this dynamic collection of features, requirements, improvements, and fixes.
Sprint Backlog: It is the selection by the development team of the items, user stories, or bug fixes to be implemented within the current sprint cycle. The team selects the product backlog items, which they will work on, at the sprint planning meeting that takes place prior to each sprint.
Increment (sprint goal): It is the final product of a sprint that may be used. The term "increment" is used frequently in the outside world and may be used to describe a milestone, a sprint objective, a full version, or even a deployed epic. Just how you establish your sprint goals and how your team defines "Done" will make a difference.
The scrum framework consists of rituals, meetings, and activities that scrum teams regularly engage in.
Organize the Product backlog: The product owner is in charge of this activity, also known as backlog grooming. To assist prioritize and keep the list organized and prepared for work at any moment, he or she updates it utilizing input from users and the development team.
Sprint Planning: The whole development team plans the work that will be done (scope) for the current sprint at this meeting. The team agrees on the sprint objective at this meeting, which is enabled by the scrum master. The product backlog is then used to add specific user stories to the sprint.
Daily Scrum: To make things easy, this daily meeting takes place at the same time and location. Many teams attempt to finish the meeting in 15 minutes; however it is only a recommendation. The daily scrum's objectives are for the team as a whole to be on the same page, focused on the sprint goal, and to develop a strategy for the upcoming 24 hours.
Sprint review: The team meets informally to see a demo of or check the increment at the conclusion of the sprint. The development team asks stakeholders and coworkers for input on the backlog items that are now marked as "Done."
Sprint retrospective: The retrospective is the time when the team gets together to reflect on and document what went well and poorly during a sprint, a project, with certain individuals or relationships, with tools, or even with particular ceremonies. The purpose is to establish a place where the team can concentrate on what worked and what needs to be improved for the upcoming task.
