2 ms·

How would you approach customizing the process to the individual or to a given circumstance? For example, I had a situation where I had a story to write functi

How would you approach customizing the process to the individual or to a given circumstance? For example, I had a situation where I had a story to write functional tests for a piece of our software. The story's scope had creeped (there turned out to be disagreement between different levels of leadership over what the tests should cover), but I had reached a point where I had implemented roughly 80% of the tests that we needed. I submitted a pull request for the progress that I had made so that it could be "locked in" and I could get it out of my mental overhead. However, the person who reviewed the PR refused to merge it because we apparently had a policy that each story could only have one PR. Ultimately, the overhead of trying to get everything in all at once resulted in the story not being successful. Although maybe that example illustrates your point about the importance of process, because I had been asking for weeks for us to actually have sprint planning so that I could break up the story, but it kept getting canceled because people felt that they were too busy.

SpicyLemonZest 7y ago
When people follow policies strictly to the exclusion of work getting done, that's not something to be solved with another policy. In a well-functioning environment, people are very willing (too willing, if you ask most security teams!) to ignore or override annoying policies that stop things from getting done. If people are working to rule, that's almost always a protest action, and the only real solution is resolving the protesters' frustration.
cushychicken 7y ago
>How would you approach customizing the process to the individual or to a given circumstance? Ideally, you don't. The heart of a good process starts with asking up front: "Is this situation generic enough that we need a procedure for it?" If yes, write process. If no, handle as a one off. I'm not sure how your example applies.

SpicyLemonZest 7y ago

When people follow policies strictly to the exclusion of work getting done, that's not something to be solved with another policy. In a well-functioning environment, people are very willing (too willing, if you ask most security teams!) to ignore or override annoying policies that stop things from getting done. If people are working to rule, that's almost always a protest action, and the only real solution is resolving the protesters' frustration.

cushychicken 7y ago

>How would you approach customizing the process to the individual or to a given circumstance? Ideally, you don't. The heart of a good process starts with asking up front: "Is this situation generic enough that we need a procedure for it?" If yes, write process. If no, handle as a one off. I'm not sure how your example applies.