tag:blogger.com,1999:blog-7930876570525471458.post3093806473397721305..comments2023-09-08T07:50:02.120-04:00Comments on Agile & Business: One impediment at a timeJoe Littlehttp://www.blogger.com/profile/13413810050491070483noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-7930876570525471458.post-10929499681532877152009-08-10T07:09:59.072-04:002009-08-10T07:09:59.072-04:00While people may have different views still good t...While people may have different views still good things should always be appreciated. Yours is a nice blog. Liked it!!!Smithhttp://www.rnbresearch.comnoreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-90933311092258702692009-08-02T10:01:35.975-04:002009-08-02T10:01:35.975-04:00Jeff,
Perfect. The "network effects", ...Jeff,<br /><br />Perfect. The "network effects", as I sometimes call them, are so important. I tried in the original to allude to them, but you more usefully hit the nail on the head.<br /><br />Thanks, JoeJoe Littlehttps://www.blogger.com/profile/13413810050491070483noreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-41326714673980680372009-08-01T13:14:25.711-04:002009-08-01T13:14:25.711-04:00This week I worked with Myank Jain at Pegasystems ...This week I worked with Myank Jain at Pegasystems who applied his social network analysis tools used by the CIA and NSA to determine root cause of problems. It can show a simulation based on the time that impediments enter the system and the effect of removing them. You always want to remove the top priority impediment first. This will have a ripple effect on all other impediments. In fact, if you make the right choice it may eliminate most of them. In any case, you can only determine the next high priority impediment after removing the top priority as the network of interactions will change dramatically if you really nail a key impediment.Jeff Sutherlandhttps://www.blogger.com/profile/07761053439034726679noreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-6318500238494723332009-07-29T10:30:24.964-04:002009-07-29T10:30:24.964-04:00Hi Don,
I really agree with your comment.
I do t...Hi Don,<br /><br />I really agree with your comment.<br /><br />I do think it is a little useful to distinguish in some way "building features" from "removing impediments". For example, the related BV is seen in a different way, usually. <br /><br />But, for example, both should be done in "single-piece flow". Which is what you said (and you said more).<br /><br />Thanks, JoeJoe Littlehttps://www.blogger.com/profile/13413810050491070483noreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-3928364634010863292009-07-29T07:32:17.299-04:002009-07-29T07:32:17.299-04:00One important point I would have added is producti...One important point I would have added is productivity loss due to multi-tasking.<br /><br />Also I dont see the need to distinguish impediments from tasks, stories etc. A bunch of things need to be done, do the most important first.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-41923866340619051402009-07-28T17:15:07.001-04:002009-07-28T17:15:07.001-04:00Hi Tim,
Well, no, I meant one.
Perhaps a small e...Hi Tim,<br /><br />Well, no, I meant one.<br /><br />Perhaps a small exaggeration.<br /><br />If one takes the Michael Phelps attitude, nothing we do is perfect, so the list of things to improve is endless/very long. There are always way more impediments to remove than one.<br /><br />Now, are things in reality more complicated than I said? Of course. <br /><br />Could there be one impediment removed per Daily Scrum and one per Sprint Retrospective? Sure. Might they overlap some? Sure.<br /><br />And there are other issues I have no alluded to. Yet.<br /><br />But...in general there is a huge need to move to single-piece flow for impediments.Joe Littlehttps://www.blogger.com/profile/13413810050491070483noreply@blogger.comtag:blogger.com,1999:blog-7930876570525471458.post-87407098988092122222009-07-28T14:51:14.444-04:002009-07-28T14:51:14.444-04:00What's important is to focus on only the impor...What's important is to focus on only the important impediments. Though I agree with the idea to *limit* the number of impediment-removal efforts (or any efforts for that matter), it is not realistic to assume everything is completely sequential. Even in a simple project, it is often not possible to focus on only <b>one</b> impediment, as there may be many things blocking forward progress on a project. The Scrum Master and Scrum Team must recognize that running around trying to solve all blocking problems is not a wise application of time, but I think what you meant to say is that we need to focus on <b>KEY</b> impediments first.Tim Eiler/Digineernoreply@blogger.com