PairingInAStrictHREnvironment
|
|
Your trail: |
Difference between version 12 and version 11:
Line 37 was replaced by line 37 |
- * Musing on this Story * |
+ * Musing on this Story |
Line 43 was replaced by line 43 |
- The trick is to bring the concerns together. Rather than see the HR policy and it's abandonment as sinister or inconsistent, why not simply see it as everyone doing their job. If it's free, HR & MIS have a perfectly legitimate concern to meet with the one-login policy. And why would they consider groups of people sharing a keyboard as dynamically as in pair programming? That's not what they are used to seeing. The development team also has a perfectly legitimate concern to assert about the policy, specifically: "This isn't free." So now someone has to make a tradeoff decision. |
+ The trick is to bring the concerns together. Rather than see the HR policy and it's abandonment as sinister or inconsistent, why not simply see it as everyone doing their job, perhaps with some ignorance? If it's free, HR & MIS have a perfectly legitimate concern to meet with the one-login policy. And why would they consider groups of people sharing a keyboard as dynamically as in pair programming? That's not what they are used to seeing. The development team also has a perfectly legitimate concern to assert about the policy, specifically: "This isn't free." So now someone has to make a tradeoff decision. |
Back to PairingInAStrictHREnvironment, or to the Page History.
|