tag:blogger.com,1999:blog-5885446522213101047.post6448013134635838911..comments2023-10-21T09:29:48.297-07:00Comments on Agile 102: Weighted Shortest Job First / WSJF - a bit of the SAFe Framework (Scaled Agile Framework)Unknownnoreply@blogger.comBlogger7125tag:blogger.com,1999:blog-5885446522213101047.post-35078012746106519692019-05-01T04:23:24.493-07:002019-05-01T04:23:24.493-07:00Job training programs are advantageous for each pa...Job training programs are advantageous for each part of your work and in this way it is significant that you be dependably watchful for different job-training programs. <a href="https://www.australianapprenticeships.gov.au/aasn/apprenticeship-community" rel="nofollow">find here</a><br />Sjadenhttps://www.blogger.com/profile/10434750061328639664noreply@blogger.comtag:blogger.com,1999:blog-5885446522213101047.post-46242460296151698232016-09-03T01:15:16.748-07:002016-09-03T01:15:16.748-07:00Agreed Bruce, I think it helps if people understan...Agreed Bruce, I think it helps if people understand the cone of uncertainty and where they are within it when making any sort of "estimate" at a point in time. Detailed estimates can often slow processes down, and not actually add any more value.Matt Hhttps://www.blogger.com/profile/03997569995627437731noreply@blogger.comtag:blogger.com,1999:blog-5885446522213101047.post-50376728628920422182015-05-31T10:57:48.397-07:002015-05-31T10:57:48.397-07:00What I like best about this approach is it leverag...What I like best about this approach is it leverages the core idea of comparing the ROI (return on investment) of various tasks as a way of prioritizing. The thing that brings the most value for the least effort should be done first.<br /><br />I also like some of the specifics above about calculating value and the emphasis on NOT getting detailed estimates up front. It's not that estimates have no use, it's that it's a waste of time to do (detailed) estimates on things you haven't yet prioritized. <br /><br />I have a whole presentation these core concepts that was very popular at ProductCamp Boston a couple of years ago: http://www.slideshare.net/bmmccarthy/prioritization-301Bruce McCarthyhttps://www.blogger.com/profile/14119251307146236943noreply@blogger.comtag:blogger.com,1999:blog-5885446522213101047.post-75011552195913814732014-09-29T02:32:38.041-07:002014-09-29T02:32:38.041-07:00Your central point seems to be that WSJF works fin...Your central point seems to be that WSJF works fine without "detailed estimates". I'd agree with that.<br /><br />The problem I see though is that we seem to have focused entirely on estimating the cost and time, but almost nothing on the value side of the equation – being mostly driven by the HiPPO.<br /><br />We need to be careful though not to throw the baby (estimates of value and rough size) out with the bathwater (inaccurate and wasteful predictions of dates or cost).<br /><br />Estimates are hard, but worthwhile doing:<br />http://blackswanfarming.com/why-making-value-estimates-is-hard-but-worthwhile/<br /><br />I've also noticed that the people who are most afraid of estimates are those who have been on the receiving end of their abuse. The reaction is understandable, but that doesn't make it right:<br />http://blackswanfarming.com/why-are-people-afraid-of-estimating-value/Anonymoushttps://www.blogger.com/profile/02183090838552964272noreply@blogger.comtag:blogger.com,1999:blog-5885446522213101047.post-3626520117250666902014-09-29T02:25:58.632-07:002014-09-29T02:25:58.632-07:00This comment has been removed by a blog administrator.Anonymoushttps://www.blogger.com/profile/02183090838552964272noreply@blogger.comtag:blogger.com,1999:blog-5885446522213101047.post-61239283580488364272014-09-29T02:22:57.148-07:002014-09-29T02:22:57.148-07:00Good post. Thanks for sharing.
I do think we need...Good post. Thanks for sharing.<br /><br />I do think we need to distinguish between the SAFe interpretation of WSJF and what Don actually recommends. In my view these are quite different and the SAFe interpretation has a few challenges, and misses out of much of the value to be gained by quanitfying Cost of DelayAnonymoushttps://www.blogger.com/profile/02183090838552964272noreply@blogger.comtag:blogger.com,1999:blog-5885446522213101047.post-33204141244851251722014-02-25T04:03:37.919-08:002014-02-25T04:03:37.919-08:00The basic idea behind WSJF is to come out with a p...The basic idea behind WSJF is to come out with a prioritization process WITHOUT incurring the costs of "detailed estimates".<br /><br />Companies have started realizing that detailed estimates is what cost them most and that their prioritization process is mostly based on this sort of variable.<br /><br />The problem with that is that they de facto initiate work in the continuous flow of delivery, work that interrupts "already prioritized work". It is not only very costly in the forthcoming projects but also costly in the running projects (via work interruptions). On top of that, it simply increases the Project Lead-Time.<br /><br />Companies needed to find another way to start working and they have done that via a simple and arithmetic formula to weight projects against each other (Portfolio Engagement Rules "IN").Pat Boenshttps://www.blogger.com/profile/06068285203547322936noreply@blogger.com