You will find everything that you need to know about product backlog in Scrum Development If you have any additional queries, do leave a comment and I would be happy to clarify Want a quick Intro to Agile under 5 minutes? Watch this video https://youtu.be/N2hDKpgzdIE Want a quick Intro to Scrum under 5 minutes? Watch this video https://youtu.be/G-MVC6EO86A Twitter: @_KrishnaR_ Blogger: goo.gl/fyRYgn
Views: 12959 Krishna R
Visit http://www.collaborativeleadershipteam.com to learn more Dee Rhoda answers the question: What is a PBI? (Product Backlog Item) In this video (https://youtu.be/pS7KQbUWp_k) Dee Rhoda answers the question: What is a PBI (Product Backlog Item)? in regard to Scrum and Agile. [Rough Transcript] Dee: Hi there! Dee Rhoda here from Collaborative Leadership Team. I would like to check in with you on the question of, what is a product backlog item? Or, as I like to call it the PBI. This is not to be confused with the PBL. We all know that the PBL is the Peanut Butter and Liverwurst sandwich we all enjoy for lunch! No, really – the PBL is the Product backlog and that is where you find the ordered list of Product Backlog Items or PBIs. PBIs are simply work that needs to be completed for a product or service in order to provide business value. For example, specifications, requirements, enhancements, fixes, and user stories are all considered Product Backlog Items. Who can create a PBI? Anyone! A Product Owner, Team member, business partner, or stakeholder can add items to the backlog at any time. For example; the Team may add additional work that they discover during planning or sprinting. The customer may add requests for enhancements. The end user may see a need for a bug fix. The Product Owner can add their work too – they might add work for getting communication or training material created. The key is to have good PBIs AND to make sure that the Product Owner is aware of them. Why? Because the Product Owner owns the backlog and they are ultimately responsible for the success of the product or service. What makes a good PBI? Well, here I refer to Bill Wake’s INVEST concept as a starting point. A good PBI should be: Independent Negotiable Valuable Estimable Small and Testable Although the INVEST concept is a good one, don’t forget that the most important action that comes from a PBI is the CONVERSATION it generates between the business and the development team. That’s agile principle #4: Business people and developers must work together daily throughout the project. Ultimately - What is a Product Backlog item?, it’s a reminder to have a conversation about what to work on, in what order, to deliver the most value to our end users and customers. To learn more about this topic and others, please visit our web site: http://www.collaborativeleadershipteam.com [End Rough Transcript] Please watch our other videos in this series on doing work differently with Scrum and agile: First Attempt in Learning | F.A.I.L. | Christian Antoine https://youtu.be/r_vWncgZ3xo Definition of Done | Scrum and Agile | Dean Gabbert https://youtu.be/ABsYE8rn9dg What is a PBI | Dee Rhoda https://youtu.be/pS7KQbUWp_k Scrum Master as Active Facilitator | Angela Johnson https://youtu.be/xawfLrOjjnU "My team…” vs “The team " Role of Scrum Master | Dean Gabbert https://youtu.be/6dPHUe9N65A High Risk, High Reward:Fail Fast, Learn Fast | Christian Antoine https://youtu.be/MkwhukCuYoQ The Power of the Retro | Dean Gabbert https://youtu.be/CiL40HrgiR8 Role of Product Owner The Lunch Test | Dean Gabbert https://youtu.be/oYThNvBp0bo Scrum and Golf | Dee Rhoda https://youtu.be/xyQDBcZsgSo Scrum Master The People Chip | Angela Johnson https://youtu.be/DWpcbz1lDY4 Scrum Master Effectiveness Survey | Dean Gabbert https://youtu.be/89jwzKWXKY8 Sprint Zero | Angela Johnson https://youtu.be/c-2QX_5_8rM Don't Wait Just Start | Dean Gabbert https://youtu.be/9doaZ4108pI Perfection vs Consistency | Agile Planning | Christian Antoine https://youtu.be/k_8rJpdF3NU Five Words to Help Leadership and Teams work Together https://youtu.be/QIttXdOvYuM Scrum Framework: Let it Work for You https://youtu.be/LHEfY51-byU Where's the Project Manager in Scrum? with Angela Johnson and Dee Rhoda https://youtu.be/EcfaMBYmni4 Product Backlog Refinement PBR | Christian Antoine, Dee Rhoda | Scrum and Agile https://youtu.be/o5nuz0BCLek T Shaped Skills - Dee Rhoda and Christian Antoine https://youtu.be/hvmcc1mjw3k Sprint Review | Christian Dee | Scrum and Agile https://youtu.be/AbiOgX9BtIY Daily Scrum | Christian, Dee, Angela, Dean | Scrum and Agile https://youtu.be/KxPnnSMO1KY VIDEO BY: Rosa Media Productions http://rosamediaproductions.com/ Produced by: Cliff Rosa Edited by: Carlo Balinget VL3v5 Dee Rhoda takes on the question: What is a PBI (Product Backlog Items)? for practitioners of Scrum and Agile
Views: 647 Collaborative Leadership Team
Tommy Norman demonstrates how to create a product backlog. This lesson is an excerpt from the video course "Scrum Product Owner LiveLessons". Purchase the 4+ hour video course at 50% off using the code YOUTUBE from informit.com/YouTube Safari Subscribers - watch the video course at https://www.safaribooksonline.com/library/view/scrum-product-owner/9780134840451/
Views: 25289 LiveLessons
I.N.V.E.S.T. is a great starting point for your team’s Definition of Ready. In this brief video, you’ll learn what the mnemonic means and gain insight into a frequently required but often overlooked addition. Video by Agile Coach Chris Gagné: https://chrisgagne.com/ Learn to code for free and get a developer job: https://www.freecodecamp.com Read hundreds of articles on programming: https://medium.freecodecamp.com And subscribe for new videos on technology every day: https://youtube.com/subscription_center?add_user=freecodecamp
Views: 4911 freeCodeCamp.org
This video teaches how to Prioritize Product Backlogs. Prioritizing product backlogs in a logical and methodical manner is a critical skills for Product Owners and Product Managers because it is critical that you focus your engineering team on deliver valuable new features for your product in a rapid manner. Whether you are doing Agile and use sprint product backlogs to create your plan or you are doing waterfall/phase-gate and writing market requirements, the technique covered in this video will give you a logical, quick and simple way to do so. Here are the three steps for prioritizing product backlogs: - Create a four quadrant prioritization matrix and label the axes from low to high - Put each feature/product backlog entry into the appropriate quadrant - Choose items based on the following criteria: o The quadrant that is low cost to develop and high value has the backlog items that go first o Then comes the quadrant with high cost, high value o Then take features from the low cost, low value quadrant (if needed for competitive parity or other reasons) o And last but not least, if there are any features in the high cost and low value quadrant forget about them For more information or how to prioritize Product Backlogs check out the following links: Optimal Product Management and Product Marketing Training Course http://280.gr/2ztJgIS Agile Excellence for Product Managers and Product Owners Training Course and Certification http://280.gr/2zsMegz Resources to download that include this technique to prioritize: - 280 group Product Management resource library, including the four quadrant prioritization matrix used in the video http://280.gr/2hSR5Ae - Feature Prioritization Toolkit, which includes additional techniques for prioritizing product backlogs and feature requests. http://280.gr/2hl8d4C
Views: 7308 280 Group
Watch the full-length video for FREE at http://businessanalysisexperts.com/product/requirements-prioritization-two-simple-techniques/ In this KnowledgeKnugget™ (KK) you will learn two techniques to prioritize your user stories or IT requirements. To view more IT requirements training, visit the Business Analysis Learning Store at http://businessanalysisexperts.com/business-analysis-training-store/. Prioritizing User Stories, or User Requirements Is Essential to Focusing Your Limited Resources on the Most Important Items First. This KnowledgeKnugget™ answers questions like: 1. How can you prioritize requirements based on business needs? 2. How can you apply the MoSCoW prioritization technique?
Views: 23715 BA-EXPERTS
Product Backlog in Scrum is one of the three Artifacts. In this video, we will be telling you- What is Product Backlog? How does it work? How to create Product Backlog? Who creates Product Backlog? How is Product Backlog useful? What are Scrum Artifacts? Watch the video for a full explanation of Product Backlog. Visit our website for more than 200 professional courses- https://www.knowledgehut.com/ Our CSM Course- https://www.knowledgehut.com/agile-management/csm-certification-training Our CSPO course- https://www.knowledgehut.com/agile-management/cspo-certification-training
Views: 213 KnowledgeHut
This module covers the hidden fifth meeting that's essential to success at Scrum and other Agile approaches. Subtopics include how to recognize well-formed Product Backlog Items (PBIs), a team effort estimation game, decomposition of large PBIs (e.g. "epics") into smaller ones (e.g. "user stories"), acceptance criteria, definition of done, Product Backlog prioritization, and team self organization. This is an interactive, scenario based module. The learner observes a simulated team and is prompted to help them as they face various challenges. See the entire series! http://www.collab.net/ScrumTrainingSeries INVEST by Bill Wake http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/ Definition of Done http://blogs.collab.net/agile/2008/10/14/suggested-topics-for-definition-of-d... Agile Manifesto http://AgileManifesto.org For the full quality, interactive version of this video, see: http://www.collab.net/ScrumTrainingSeries Find a Scrum class in your city: http://www.collab.net/services/training/agile Scrum Reference Card: http://www.collab.net/sites/default/files/uploads/CollabNet_scrumreferencecard.pdf Example ScrumMaster's Checklist: http://www.collab.net/sites/default/files/uploads/ScrumMaster_Checklist.pdf
Views: 250654 CollabNet VersionOne
An excerpt from the "Scrum Repair Guide" by Mike Cohn: https://www.frontrowagile.com/courses/scrum-repair-guide ... This chapter of Mike Cohn's eLearning video training course, "Scrum Repair Guide," discusses how to understand problems with the product backlog, from how detailed items should be to what types of items belong on a backlog and to what backlog grooming is and when to do it. Earn four PDUs, SEUs and a certificate of completion after successfully completing the full course. Course may be downloaded or streamed at FrontRowAgile.com
Views: 32348 Front Row Agile
Ever feel like your Scrum team's product backlog is a bit of a mess? Maybe there are some unclean cards - or projects that need to be broken down a little further? We can help you with that. In this video, Certified Scrum Trainer, Chris Li, walks you through simple, effective method for getting your backlog back in shape.
Views: 108 Beyond20LLC
I recently joined an established company with an existing product, customers, team members, and a well-defined growth plan to deliver a large-scale version of the product in 5 months. Although there was a clear vision on what to build, the actual knowledge was spread across different documents, excel files, notes, and team members. There was no common understanding. In other words, no product backlog to guide the team to a successful delivery. In this talk we will overview techniques that you can adapt to your own needs to populate, estimate and prioritize a backlog for a large-scale product. We will not focus on the theory behind creating backlogs. Instead, we will take a close look into a real-case scenario where known and existing methods were adapted and integrated to build a backlog in less than a week. Autor: Frederico Figueiredo
Views: 5927 Agile Spain
http://tv.ssw.com/what-is-a-product-owner The 2013 Scrum Guide definition of the 'Product Owner', in video form! http://rules.ssw.com.au/Management/RulesToBetterProductOwners/Pages/default.aspx (from the 2013 Scrum Guide:) The Product Owner The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: Clearly expressing Product Backlog items; Ordering the items in the Product Backlog to best achieve goals and missions; Ensuring the value of the work the Development Team performs; Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, Ensuring the Development Team understands items in the Product Backlog to the level needed. The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable. The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a backlog item's priority must convince the Product Owner. For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner's decisions are visible in the content and ordering of the Product Backlog. No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn't allowed to act on what anyone else says.
Views: 63690 SSW TV | Videos for developers, by developers
On 23th July 2016 we conducted an agile awareness session in Gurgaon, this was a one-day long session for professionals who are new to agile. This video was made from the live classroom interactions and it covers interesting questions around detailing of Product Backlog items. To know more about our upcoming workshops on agile please visit www.izenbridge.com
Views: 757 iZenBridge Consultancy Pvt Ltd
We're looking at Scrum in detail. Today it's the turn of the SPRINT BACKLOG. Grab your FREE Scrum Cheat Sheet: https://www.developmentthatpays.com/cheatsheets/scrum → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe ------------------- 133. Sprint Backlog - [Scrum Basics 2019] + FREE Cheat Sheet The Sprint Backlog is the list of things that the Development Team that the development team will work on during the sprint. It is created once for every Sprint. And Sprint Planning is the Scrum Event where it is created. The Product Backlog - the “master list” of things to do - provides the input. Simply put - and I’m quoting directly from the Scrum Guide here - “The Sprint Backlog is the set of Product Backlog items selected for the Sprint” Two properties of the Product Backlog and its contents are important/relevant/helpful when it comes to making the selection. It is a prioritied list - the most valuable items are at the top. And the items - at least those towards the top of the list - are “sized”. It’s common practice to size with Story Points - though You won’t find them mentioned in the Scrum Guide. And if the Team has a few Sprints under its belt. It will have some idea of its CAPACITY The number of Story Points it can handle - process - during the course of a Sprint. Could it be that Sprint Planning is as simple as Taking items one at time from the top of the Product backlog …. Until the total number of Story Points selected…. equals the Capacity. Perhaps with a bit of jiggling at the end to fill the last space. If it were that simple, there’s be a button for it in Jira. // And perhaps there is. I’ve no idea!! Let’s take half a step back and begin with the end in mind By the END of the Sprint, the Development Team’s job is to develop/produce/create an Increment. To give it its Sunday Name: a potentially releasable increment. So - as far as it is possible - it make sense that the selected Product Backlog Items are complementary. Coherent. All - in some way - pulling in the same direction. Towards…. an agreed Sprint Goal. The Scrum Guide ties these the things together nicely: “The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.” https://www.youtube.com/watch?v=epTynaqy00Y&list=PLngnoZX8cAn9dlulsZMtqNh-5a1lGGkLS
Views: 1955 Development That Pays
We're looking at Scrum in detail. Today it's the turn of the PRODUCT BACKLOG. Grab your FREE Scrum Cheat Sheet: https://www.developmentthatpays.com/cheatsheets/scrum → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe ------------------- 134. Product Backlog - [Scrum Basics 2019] + FREE Cheat Sheet The Product Backlog is an ordered list of everything that is known to be needed in the product. That’s how the Scrum Guide describes it…. And the Scrum Guide goes on to dedicate a fair few column inches to it. The Product Backlog is one of the three Scrum Artefacts - along with the Sprint Backlog and the increment. The Product Backlog sits here - outside of the Sprint “process”... but a key input to it. Without the Product Backlog, there’d be nothing to talk about in Sprint Planning… and nothing to put in to the Sprint Backlog. If I zoom out further to the overall agile flow We see than the Product Backlog is the “vessel” the collection point for feedback received from the the customer - as well as from Stakeholders and from the Development Team. Worth mentioning here that … just as this flow is not unique to Scrum… the Product Backlog is not a “construct” that’s unique to Scrum - it forms part of every Agile Framework I’m aware of. We have a well-defined way of getting items out of the Product Backlog - that the (ritual - the event) of Sprint Planning. Getting things into the Product Backlog is less well-defined But at least it does have an owner - the Product Owner. We talk much more about the Product Owner in another episode, but when it comes to the relationship between Product Owner and Product backlog…. The Scrum guide could hardly be more clear: The Product Owner is the sole person responsible for managing the Product Backlog. https://www.youtube.com/watch?v=zEHHjNEiCtI&list=PLngnoZX8cAn9dlulsZMtqNh-5a1lGGkLS
Views: 1763 Development That Pays
How to create a project and product backlog in Team Foundation Server - Visual Studio Online Other links that provide background to this video: Create a Product Backlog : http://webgate.ltd.uk/create-a-product-backlog/ Create a VSO account in three mins or less : https://www.youtube.com?v=LCXK0v6c998
Views: 6865 Webgate
This short video you will teach you on how to prioritise your product backlog using Weighted Shortest Job First method If you like it, do not forget to Share, Like & Subscribe to my channel Twitter: @_KrishnaR_ Blogger: goo.gl/fyRYgn
Views: 14228 Krishna R
The product backlog is for business problems, user needs and wants, features and functionality. The product backlog should not contain technical items. Instead, the Scrum Team takes care of technical issues, problems, solutions and techniques. This is fundamental to the division of responsibilities in Scrum.
Views: 1586 BERTEIG - Kanban, Scrum, Real Agility
In this Scrum Tapas video, Professional Scrum Trainer Rich Visotcky describes the Product Backlog and the need to ensure that it is transparent to the entire Scrum Team. Rich talks about why everyone on the Scrum Team needs to understand what it is comprised of, the order or priority of Product Backlog Items and how they fit into the product vision.
Views: 5075 Scrum.org
From Mike Cohn's online training course, Agile Estimating and Planning. For more information or to stream and download, go to Front Row Agile: https://www.frontrowagile.com/courses/agile-estimating-and-planning In this video, Mike begins to introduce the ideas of estimating a product backlog by drawing analogies to estimating two real-world activities. You can earn four PDUs, SEUs and a certificate of completion after successfully completing the full online course.
Views: 4522 Front Row Agile
NEWSLETTER — join 18,000 peers: https://age-of-product.com/subscribe/?ref=youtube There is no shortage of Scrum product backlog anti-patterns: From out-dated and oversized tickets to the part-time proxy product owner– answering to the product committee — and his or her repository of 623 ideas. Learn more about the numerous product backlog anti-patterns that can manifest themselves when you create value for your customers. Moreover, learn how to prevent them in the first place. HOST: Stefan Wolpers BLOG: https://age-of-product.com/webinar-product-backlog/
Views: 1246 Age of Product
The technical members of a Scrum Team are responsible for implementing Product Backlog Items every Sprint... shouldn't they decide what the best order of implementation is? In Scrum, this is not the job of the team... it's the job of the Product Owner. Find out why this is critical for the success of Scrum!
Views: 1370 BERTEIG - Kanban, Scrum, Real Agility
Backlog Prioritization for Agile Software Development its Benefits, Techniques and example. Visit the link for details on backlog prioritization, with many graphical representation https://agiledigest.com/agile-digest-tutorial/backlog-prioritization,
Views: 4310 Agile Digest
In this video we'll show you how Agile tools in Visual Studio Team Services (VSTS) can make planning your next project easier then ever. We'll go over features such as backlog management (Tasks, bugs, features, etc.), Kanban boards, powerful queries using our query language and delivery plans. For more details see our documentation: https://docs.microsoft.com/en-us/vsts/?view=vsts#pivot=services&panel=agile Speaker: Donovan Brown
Views: 11747 Microsoft Developer
On 23th July 2016 we conducted an agile awareness session in Gurgaon, this was a one-day long session for professionals who are new to agile. This video was made from the live classroom interactions. To know more about our upcoming workshops on agile please visit www.izenbridge.com
Views: 1287 iZenBridge Consultancy Pvt Ltd
This video shows the new option group that was added to the Project chart on the 'Projects' page
Views: 27 Scrum Commitments
The Sprint Planning Meeting is held with the objective of selecting the set of Product Backlog items which are to be delivered during the current Sprint. It is attended by the Product Owner, the Scrum Master, and the entire Scrum Team. It is one of the four ceremonies conducted in Scrum. In this video, we are going to explain you the Sprint Planning Meeting in detail. Watch the video to understand the concept and feel free to ask doubts in the comment section. Visit our website https://www.knowledgehut.com/ to chose from more than 200 professional courses, including CSM, PSM, CSPO and many more.
Views: 4151 KnowledgeHut
Jira tutorial for beginners. Topics covered in the Session are Deleting a Jira Project, jira scrum tutorial, Creating a scrum project in jira, Creating a User Story and Epic, Creating a Backlog in jira, Creating a sprint in jira, starting a sprint in jira. To Learn or Teach Linux visit www.theskillpedia.com, A Marketplace for Learners and Trainers. To know about me visit my profile at www.rnsangwan.com. I deliver online training on Business Analysis, Linux, Unix, MySQL, Sybase, SQL Server, Perl, Python, R Data Analysis, Scala etc. The Complete JIRA Training Course is Available at http://www.theskillpedia.com/ For the Course Contents Visit http://www.theskillpedia.com/jira-training/
Views: 53625 TheSkillPedia
Product Backlog Scrum kennt zwei wichtige Listen: das Product Backlog und das Sprint Backlog. In diesem Video stellen wir das Product Backlog vor. Das Product Backlog ist eine geordnete Liste von allen möglichen Anforderungen die es an ein Produkt geben kann. Die einzelnen Anforderungen werden Backlog-items genannt und werden vom Product Owner erstellt. Die Backlog-items kann es zum Beispiel in von Form von User Stories geben. Ein gutes Product Backlog zeichnet sich durch die folgenden vier Elemente aus, deren erste Buchstaben das Wort "DEEP" bilden: [DEEP] -Detailed (angemessen detailliert): Die Backlog items mit der höchsten Priorität werden in detaillierter Form vorgehalten -Emergent (sich entwickelnd): Ein Product Backlog hat keinen definierten Plan, sondern das Product Backlog wird ständig angepasst und weiterentwickelt. -Estimated (beschätzt): Der Arbeitsaufwand, der mit jedem Backlog-Item einhergeht, wird geschätzt, so dass das Team klar erkennen kann, wie viel Arbeit noch übrig ist. -Prioritised (priorisiert): Der Product owner ist für die Reihenfolge der Einträge und deren Priorisierung verantwortlich. Ein Scrum-Team kann sich dafür entscheiden, ein Backlog Refinement Meeting wahrzunehmen. Das Backlog Refinement Meeting dient in erster Linie dazu, dass der Product Owner dem Team die neuesten User Stories erläutert. Durch eine gemeinsame Diskussion werden die User Stories hinterfragt und ausgearbeitet. Möchten Sie mehr wissen? https://scrumguide.de/product-backlog/
Views: 15 Agile Scrum Group
The process of getting "stories" or Product Backlog items ready for the next sprint is called Backlog Refinement. The Product Backlog Iceberg is a widely used metaphor to explain the process. Peter Stevens explains his take on the process, including an explanation of the mysterious terms, TFB and NFC!
Views: 579 Peter Stevens
Most Product Backlog Items (PBIs) initially need refinement because they are too large and poorly understood. Teams have found it useful to take a little time out of Sprint Execution — every Sprint — to help prepare the Product Backlog for the next Sprint Planning Meeting. For more information about scrum please visit: http://dcmlearning.ie/courses/psm%E2%84%A2-certified-professional-scrummaster-course/ In the Backlog Refinement Meeting, the team estimates the amount of effort they would expend to complete items in the Product Backlog and provides other technical information to help the Product Owner prioritize them. (The team should collaborate together to produce one jointly-owned estimate for an item.) Large vague items are split and clarified, considering both business and technical concerns. Sometimes a subset of the team, in conjunction with the Product Owner and other stakeholders, will compose and split Product Backlog Items before involving the entire team in estimation. A skilled Scrum Master can help the team identify thin vertical slices of work that still have business value, while promoting a rigorous definition of “done” that includes proper testing and refactoring. It is common to write Product Backlog Items in User Story form. In this approach, oversized PBIs are called epics. Traditional development breaks features into horizontal tasks (resembling waterfall phases) that cannot be prioritized independently and lack business value from the customer’s perspective. This habit is hard to break. Agility requires learning to split large epics into user stories representing very small product features. For example, in a medical records application the epic “display the entire contents of a patient’s allergy records to a doctor” yielded the story “display whether or not any allergy records exist.” While the engineers anticipated significant technical challenges in parsing the internal aspects of the allergy records, the presence or absence of any allergy was the most important thing the doctors needed to know. Collaboration between business people and technical people to split this epic yielded a story representing 80% of the business value for 20% of the effort of the original epic. Since most customers don’t use most features of most products, it’s wise to split epics to deliver the most valuable stories first. While delivering lower-value features later is likely to involve some rework, rework is better than no work. The Backlog Refinement Meeting lacks an official name and has also been called “Backlog Grooming,” “Backlog Maintenance,” or “Story Time.”
Views: 9454 Patrick Byrne
This Video describes the usage of Themes to group the items so that the Product Backlog can be partitioned for use across multiple teams. One product always has one product backlog and multiple teams will work using themes to partition the product backlog and work on them so that correct prioritization is ensured. For More Information, Follow the Links below - Website - http://www.worldofagile.com/ Facebook - https://www.facebook.com/Fascinating.World.Of.Agile/ Twitter - https://twitter.com/WorldOfAgile LinkedIn - https://www.linkedin.com/company/world-of-agile/
Views: 27 World Of Agile
Anyone who has worked on a software project knows that there are issues to track, manage and prioritize. Azure Boards has all the features your team needs to successfully manage your work. Visualize work with Kanban boards, execute in sprints, manage your backlog, and use queries to find work and visualize results. In this video we will show you how to get started with and introduce you to the basic aspects of Azure Boards. Speaker: Ali Tai - Getting Started: https://azure.microsoft.com/services/devops/boards/ - Documentation: https://docs.microsoft.com/azure/devops/boards/index
Views: 19370 Microsoft Visual Studio
The Product Owner has often been considered a bottleneck when creating a Product Backlog, as he was deciding which items would be included. Nowadays, new practices have been introduced to ensure that the Product Backlog is defined more efficiently. Curious to find out how it’s done? Join me in my how-to video! https://www.borisgloger.com
Views: 99 borisgloger consulting GmbH
NEWSLETTER — join 18,000 peers: https://age-of-product.com/subscribe/?ref=youtube If you are working as a product owner, there is — very likely — room for improvement. I curated the most common product owner anti-patterns to help you up your game. If you like to improve on those anti-patterns that you recognize why don’t you ask the scrum master and the team for support? The product owner anti-patterns list is a good starting point for a mutually beneficial retrospective. According to the Scrum Guide, the product owner is sole and accountable person optimizing the work of the engineers. In other words, the product owner has ideas or identifies ideas, or at least he or she curates suitable ideas from wherever and validates them whether those ideas are “product backlog worthy” or not. In my experience, this approach turns the product owner into the Achilles heel — or bottleneck by design — of the whole process. If you "remove" the PO as an independent and respected role, for example, by sticking with your organizations' stage-gate process, Scrum easily mutates into a Waterfall 2.0 process. This Hands-on Agile webinar addresses 12 familiar product owner anti-patterns interfering with the concept of the Scrum product owner role. Learn how to improve your professional performance by avoiding the typical product owner mistakes: from oversized product backlogs and prioritization by proxy, to be absent during the sprint, and outing yourself as a loner during the sprint review. HOST: Stefan Wolpers NEWSLETTER: Learn about new webinars in advance: https://age-of-product.com/subscribe/?ref=youtube BLOG: “Product Owner Anti-Patterns”: https://age-of-product.com/product-owner-anti-patterns/ SLIDEDECK: https://www.slideshare.net/wolpers1/handson-agile-webinar-6-product-owner-antipatterns CONTENT: (1) The first anti-pattern covers the oversized product backlog: The product backlog contains more items than the scrum team can deliver within three to four sprints. This way the product owner creates waste by hoarding issues that might never materialize. The product owner is probably using the product backlog as a repository of ideas and requirements. (This practice is clogging the product backlog, may lead to a cognitive overload and makes alignment with the ‘big picture’ at portfolio management and roadmap planning level very tough.) (2) The second anti-pattern covers creating the product backlog in the wrong way: The product owner treats product backlog items not as a token for discussion to build a shared understanding of the why, how, and what with the team, but as deliverables. Often, the PO creates product backlog items upfront by copying from requirement documents without including other members of the scrum team. (3) The third anti-pattern covers the weak product owner: The PO has not learned to say no to stakeholders demanding new requests. Trying to being everybody’s darling creates mediocre products that do not scale, though. It also defies the product owner’s most important duty: protecting the product backlog from tasks with little or no value. (4) The fourth anti-pattern covers prioritization by proxy: A single stakeholder or a committee of stakeholder prioritizes the product backlog — not the product owner. (The strength of Scrum is building on the strong position of the product owner. The product owner is the only person to decide what tasks become product backlog items. Hence, the product owner also decides on the priority. Take away that empowerment, and Scrum turns into a pretty robust waterfall 2.0 process.) (5) The fifth anti-pattern covers the omniscient product owner: The PO does not involve stakeholders or subject matter experts in the refinement process, and probably not even the Scrum team. (6) The sixth episode covers the lack of a sprint goal: The product owner cannot provide a sprint goal, or the chosen sprint goal is flawed. (7) The seventh anti-pattern covers the pushy PO: The product owner pushes the development team to take on more tasks than it could realistically handle. Probably, the product owner is referring to former team metrics such as velocity to support his or her desire. (8) The eighth anti-pattern covers how the product owner might be toying with the definition of ready. The PO tries to squeeze in some last-minute user stories that do not meet the definition of ready. (9) The ninth anti-pattern covers the absent product owner. If the PO is not available for immediate clarification, he or she will create artificial queues that probably will put the scrum team’s sprint goal at risk. (10) The tenth anti-pattern covers the product owner who cannot let go product backlog items once they become sprint backlog items. (11) The eleventh anti-pattern covers the selfish product owner, presenting “his or her” accomplishments to the stakeholders. (12) The twelveth anti-pattern covers the unapproachable, the broadcasting product owner.
Views: 1148 Age of Product
Welcome to the Scrum Training by KnowledgeHut. In this video of our Scrum Training Course, our trainer Mr. Vishal Prasad will give you a brief introduction to the Scrum Artifacts. He will cover all the Scrum Artifacts namely, the Product Backlog, the Sprint Backlog, and the Product Increment The various sub-topics covered in this video are- Simple, Complicated and Complex problems. 03:41 Product Backlog What is Product Backlog? Product Backlog Items Product Backlog example 06:28 Sprint Backlog What is Sprint Backlog? How to use Sprint Backlog How to create Sprint Backlog 07:38 The Increment What is an Increment? What is a done Increment? The transparency of Scrum Artifacts How to achieve transparency in Scrum? In a series of videos, we will try to train you with all the concepts of Agile and Scrum. Watch this Scrum Tutorial series for the complete understanding of all the Scrum concepts. For complete e-learning and classroom training in all the scrum related courses, visit our website https://www.knowledgehut.com/ Visit our CSM course- https://www.knowledgehut.com/agile-management/csm-certification-training Don't forget to watch all the videos of our Scrum Training Series Scrum Training Part 1- https://youtu.be/jikSon6mIzc Scrum Training Part 2- https://youtu.be/esxnA6A2ajE Scrum Training Part 3- https://youtu.be/e_EI0yZVVx0 Scrum Training Part 4- https://youtu.be/vt3ARg9QY2w Scrum Training Part 5- https://youtu.be/OvZDjJoUods Scrum Training Part 6- https://youtu.be/RYBITAovpWg Scrum Training Part 7- https://youtu.be/zIn6mEaCGJ0 Scrum Training Part 8- https://youtu.be/_I5awQ8hrNY
Views: 473 KnowledgeHut
(Re-upload with fixed audio) Ever manage a backlog with more than 200 tasks that include feature requests, bugs, technical debts, external requirements, etc? Yeah, we do too! So, which one would you pick first? Who should pick? How do you decide on which task gets prioritized over other items in your backlog? Whether you are a Product Manager, a Development Manager or a Team Lead, if you manage backlogs day-to-day, this talk's for you. Carlos Khatchikian, Jira Mobile Team Lead, will share tips and tricks on how to keep your backlog sane. Using Jira Software backlog functionality and techniques such as relative sizing and sprints for categorization, you'll be able to keep your backlog as healthy as a stylish neat beard.
Views: 5993 Atlassian
Scrum Made Easy 50% Discount go to http://jebriordan.com Before I dive into the details, I want to give you a high level overview of a typical scrum process. So that you will better understand the roles, the events and the artifacts that I will be showing you in the next sections of the course The process flow, It’s all on one slide and here it is… The process starts when the product owner creates the product backlog, that is A list of all the features and functions and requirements that might be needed in the final product of the project. It’s a prioritized list. The items with the highest business value have high priority. Low value, add-on functionality has low priority. The scrum team get together in a sprint planning meeting and decide what items in the product backlog they can work on and complete during the next time period. This list of items is called the sprint backlog. The development team immediately set to work completing the items in the sprint backlog in a set time frame called a sprint. Every day during the sprint the development team and the scrum master meet in a short 15 minute stand up meeting, called the daily scrum, to discuss their individual progress, synchronize their activities, identify any issues that will stop them from working; and plan for the work to be completed in the next 24 hours Towards the end of the sprint, the development team demonstrate to the product owner and other stakeholders, the output of the work they’ve done during the current sprint and all previous sprints. They demonstrate the latest increment of the product. And this latest increment is a potentially shippable product. And all the while the product owner supported by the scrum master reviews the latest product increment and the potential business value and refine the product backlog in preparation for the next iteration or sprint. And the process begins again Now Looking at the process in another way, in the form of a bar chart for you traditionalists out there And again only one slide It starts with the product backlog And the scrum team decide what Product Backlog Items can be delivered in the next time-boxed sprint This list of Product Backlog Items is frozen in a sprint backlog The sprint begins and the development team meet every day at the same time, same place to plan for the next 24 hours At the end of the sprint the development team demonstrate to the product owner and other stakeholders what they’ve done so far. That is In this current sprint plus all previous sprints. This is called an increment and is a potentially shippable product After the sprint review the scrum team get together and discuss what went well and what didn’t go so well in the last few weeks and make plans to include process improvements in the next sprint And while all the work is in progress, the product owner is reviewing, adding to, subtracting from and fine tuning the remainder of the product backlog This product backlog grooming is kind of stopped while the planning meeting for the next sprint takes place And the cycle continues. So there you have it a typical scrum process that’s iterative, cyclical and another word that’s coming soon “emprical” In the next section I’ll start the discussion on the critical roles needed in a scrum team, the product owner, the scrum master and the development team I’ll see you in the next lecture…
Views: 1411 Jeb Riordan
The answer may shock you --- or not. Sign up to be the first to know when our ENTIRE 40-Day QA course comes out (and make an avg of $50,000/yr): http://eepurl.com/cquSlT Our 40-Day QA course will show you EXACTLY HOW you can learn how to become a Software Tester (aka 'QA Analyst'), in just 40 days. Change your career. Change your life! Facebook: https://www.facebook.com/40dayqa
Views: 12 40-Day QA
Use Visual Studio Online to plan your iterations and break down the tasks that are required to complete your user stories. Specify your team capacity and use the tool to determine the amount of work that can be brought in to every sprint.
Views: 36219 EstebanFG
One of the critical factors of being a Great Product Owner is deciding what not to do. A Product Owner is responsible for maximizing the value of product for all stakeholders(users, buyers and sponsors). There are many ways to prioritize product backlog. Opportunity Matrix balances the need of users and opportunity for building business by solving the problem. Listen to Satisha Venkataramaiah [https://www.linkedin.com/in/satishakv/] to understand what is Opportunity Matrix. PlayScrum is an online platform for learning Product Ownership. Join our courses on https://playscrum.com/ to learn Product Ownership at your own place and own pace. You can also join in-person Certified Scrum Product Owner workshop offered by Leanpitch (https://leanpitch.com/)
Views: 305 Play Scrum