XpdWiki

FrontPage
RecentChanges
XtC
FindPage
PageIndex
XpApprentices

Set your name in
UserPreferences

Referenced by
...nobody




JSPWiki v2.0.52


PairingInAStrictHREnvironment


This is version 1. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]


We have an issue here with pair programming and the company policy of individual responsibility for network usage. The "management information systems" and "human resources" departments have a very strong desire to be able to monitor and audit every user's individual network activity, for use as evidence in any disciplinary scenario that might occur in future.

They have noticed that our XP developers all log on to the development workstations (which are reserved exclusively for pairing on development tasks) using the same ID. They find this unacceptable. Their preferred solution is for the "driver" to be logged in, and then log out to allow the "navigator" to log in each time the keyboard changes hands. We find this unacceptable, for obvious reasons.

In search of a workable compromise, I'm wondering what other teams do as I can't imagine we are the only ones with this issue. So, stories please (and not speculation :) about your experience of this issue. Thanks. --KeithB


In our last project the computers were all owned by a particular developer, and logged in as them. They were responsible for anything that happened on that machine security wise (including virus updates etc). --BenHogan

--- If you're not doing anything dodgy then surely it doesn't matter who's logged in? Maybe you could login in the morning, and your partner could login for the afternoon, just to show you both made it into work that day. Obviously, if you are flirting with the grey areas of "acceptable usage", or you can't trust your partner not to visit porn sites while you're in the loo, then I can see it could be an issue... -- DavidPeterson


More info...   Attach file...
This particular version was published on 18-Feb-2004 23:39:55 GMT by unknown.