{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/36b3ac59f6404dc69dace8f43bc48947\" frameborder=\"0\" width=\"1300\" height=\"975\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":975,"width":1300,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":975,"thumbnail_width":1300,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/36b3ac59f6404dc69dace8f43bc48947-c31f4bcb01728420.gif","duration":301.728,"title":"Mastering the Dependency Sticky Function in piplanning.io","description":"In this Loom, I explain Dependency Sticky Notes in piPlanning.io and why the Dependency Sticky Function is pretty unique and even magical. I show how it works like metadata so teams can communicate and coordinate dependent work, including what you need, when you need it, why, the linked feature, and who enables it. For example, a dependency requested in Sprint 3 can be resolved by the enabling team through tradeoff decisions, then mirrored to the Art Planning Board, and the red flag removed when resolved. I ask viewers to focus on stickies with red flags since those are not resolved."}