4 ms·
A related skill is being strategic about what really needs to be done right now. If you hit a roadblock, some people will just stop. Some will ask around and st
by wcarss 9y ago
A related skill is being strategic about what really needs to be done right now. If you hit a roadblock, some people will just stop. Some will ask around and stop if there are no easy answers. Some will persevere until they hit their head so hard against the wall that the wall gives way.
Some people will check if this is really a critical thing to accomplish right now, and just work around it when it makes sense. This can be the difference between 100% done, six weeks late, and 95% done on time, with a small outstanding improvement left to complete. It may even be easier to do when other work is done first.
Sometimes you can't go around it -- then the honey badger does surely take the day! But I've found (and seen) a lot of success in asking yourself / a Product Owner if a feature can be delayed, or even cut.
- Animats 9y agoYup, that's "agile". "Shit early, shit often."
- wcarss 9y agoI don't feel "agile" is the same as being smart about scope cuts, or about shaving yaks that aren't in the way, so I'm left feeling that your comment was ...a bit of a shitty place to drag the discourse. :) In other words then, I'm more inclined to think of what I was saying as that it may be better to hold off on shitting at all if you're having a hard time, than to decisively shit your pants long after you've left the toilet.
- collyw 9y agoI always thought that "agile" was "you're doing it wrong".
- ksk 9y agoWell, its the age old pragmatism versus idealism dichotomy. One isn't better than the other, except sometimes.