Makes sense, right? After all, you don't want the Product Owner deciding that two people in one Sprint can build a house with just a bag of nails. The Developers (not the Product Owner) should size the work because they know best what they can reasonably complete within the Sprint timeframe. Manageable sizing of the highest PBIs is critical to delivering an Increment of value each Sprint, which is the cornerstone of Scrum. They collaborate on the sizing of higher ordered items and brainstorm ideas for what to include in the Product Backlog. The Product Owner and the Developers work together to maximize the product's value. While the Product Owner is accountable for the content and order of the Product Backlog, they must regularly collaborate with the Developers on the Scrum Team. The Product Owner can delegate the creation of individual Product Backlog items but remains accountable for the overall content and order. It can include activities such as upgrading the development environment, bug fixes, adding code comments, code reorganizing or refactoring, and removing workarounds. Technical debt is work required to improve or maintain the quality of the product. The Product Backlog includes a list of new features for development, production bug fixes to resolve, fixes for technical debt for completion, and anything else that the Product Owner believes would add value to the product. It includes an ordered list of all the work the team needs to do to maximize the value of the product resulting from the work of the Developers. The Product Backlog is commonly summarized as the to-do list for the team. Like a folder structure, they are a convenient way to group PBIs into meaningful groups. Epics and features are complementary Scrum practices that some Product Owners use to organize their Product Backlog. Each item on the Product Backlog is a to-do item, and each to-do item is called a Product Backlog item (PBI). A question keeps coming up in my Applying Professional Scrum classes: "What are epics and features, and how do we use them in the Product Backlog?" The Product Backlog is the to-do list for the team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |