Um, but Team has been on a ramp that we need to self-organize around some method and what we found and sort of the last prioritization for a release scope is that we have a lot of oversized issues and features, um that Uh, you know honestly need a need a beat or a release, um to go through user research Um, maybe look at the code if they've never seen the code, you know reviewed that piece of code before Or make some recommendations on the best way to solve Um, so I put some thinking around, you know That sort of you know that dual track mindset dual track agile kind of launching off of what user experience has recently updated for dual track agile So feedback on that and then the second piece is that this experiment we're running is we're leveraging a semi-dual track agile approach just to organize our conversation how we open issues, uh for areas that we need a discovery beat versus Presenting an issue that is actually ready for delivery.
嗯,但團隊一直在斜坡上,我們需要圍繞一些方法進行自我組織,我們發現和排序的發佈範圍的最後一個優先級是,我們有很多過大的問題和功能,嗯,你知道誠實地需要一個需要一個節拍或釋放,嗯,通過用戶研究,嗯,也許看看代碼,如果他們從來沒有見過代碼,你知道之前審查的代碼,或提出一些建議的最佳方式來解決嗯、是以,我圍繞雙軌思維進行了一些思考,雙軌敏捷是根據用戶體驗最近對雙軌敏捷的更新而推出的,是以,我對雙軌敏捷進行了反饋,然後第二部分是,我們正在進行的實驗是利用半雙軌敏捷方法來組織我們的對話,我們如何打開問題,嗯,對於我