I am an experiential learner, I will try to present in an understandable way the ideas and knowledge I have learned through my experience and learning about the backlog.
Viewing: What is a Backlog
Scrum is a methodology or framework for Agile project management. It is used by more than 70% of software development teams.
Methodology: a system of ways of doing, teaching, or studying something — cambridge.org
Scrum has two types of backlogs: product backlog and sprint backlog.
Product backlog and Sprint backlog in Scrum
Product backlogs are prioritized lists of customer-centric features and functions. It is broken down from the overview into manageable sections of the work, it is called Product Backlog Items (PBIs). PBIs are usually represented by User stories.
See also: What is a comparison – There are several types of comparisons
On the other hand, the sprint backlog is a list of features and tasks that will be performed in the sprint by the development team. Of course, these features and tasks will also have priorities.
What is the difference between the product backlog and the sprint backlog?
The product backlog is based on the features requested by the customer, the person who makes and summarizes these features mostly comes from the Product Owner. The product backlog is constantly updated and clarified. Features can be pulled from the Product backlog to the Sprint backlog and usually follow some of the principles set forth by the Scrum team such as CUTFIT (Consistent — Unambiguous — Testable- Independent — Traceable), etc. The sprints are followed continuously. . While the development team is developing this sprint, the Product Owner, Scrum master must prepare the sprint backlog for the next sprint. And usually before the end of the current sprint, the scrum team will have a Product Backlog Grooming (Backlog Refinement Meeting) meeting to prepare the next sprint backlog. The sprint backlog is the features that will be implemented in the sprint and the product backlog may be available. feature with low precedence or no value will be discarded.
And, the similarities between them:
Both the product backlog and the sprint backlog are pull systems, not push systems. This is also a fairly common mistake often encountered by scrum teams. I would like to take a bit of time to explain this point of view. Agile thinking is about flexibility – and in my opinion, flexibility is the speed of adaptation, not the velocity. That means you have to make quality products, not try to run fast. You have to improve continuously and that only comes when you spend time on continuous improvement, spend time trying new things, trying things your team believes will bring better results. I can’t guarantee you something new will work right away, it’s possible that you and your team need some trial and error to get to a state of maturity that offers more value. Therefore, you have to let the Developer see that the Done feature is done, maybe responsible for that feature, then they need to pull the new feature to continue developing another feature. Besides, you don’t push tasks/tasks, helping the Scrum team always have time to make improvements and test new things. In addition, the point to note is that pulling (pull) features from the product backlog to the sprint backlog will be done when the feature meets the criteria such as clear, unambiguous, estimated, high priority, …Agile’s thought is towards people, autonomous teams, self-organizing activities, limiting hierarchical hierarchy will need a lot of initiative and contribution to the common goal, so whether the product backlog or the sprint goal still needs to be played by the scrum team. contribute.
See also: What Is Nicotine – And 1001 Things To Know About Nicotine
Good management of the product backlog and the sprint backlog is very important in the adoption of Scrum, which leads to the success or failure of the sprints and the adoption of scrum.