The goal of pair programming is for each pair to function as a single unit. Tracking what one person does vs the other does not make sense.
The goal of no shared logins is to track each change down to a single unit. Having a generic account for people to use when pairing would not solve that need. If you have a stringent auditor, you would be best served by generating a new account for each pair and shut it down whenever a pair changes. If you have a looser auditor, you can assign each person a "pairing" account for them to use when serving as a pair. This account can be linked to the pairing records to identify which pair accessed the resources. Whoever is running the keyboard at the beginning of a pairing shift will just login with their pairing account. It's not quite as logically clean, but a whole lot more practical. -Josh More On Tue, Jun 12, 2012 at 8:58 AM, Matthew Perry <[email protected]> wrote: > My company is doing paired programming to become more agile in their > development. We would like the devs to login using their personal AD > account when logging into the computer, but they are pushing for a shared > account to allows for easier switching and pair changes. Does anyone have > any experience with this type of environment? > > Do we meet in the middle and give them a shared AD account that can only > login to their teams machines? This way they will still get the group > policy settings vs using a shared local account, which is what they are use > to doing. I know we would lose the accountability of who logged into the > machine, but at least we are getting some of the GP locked down settings. > Any thoughts or ideas are appreciated. > > FYI.....we also have to worry about linux and mac dev machines in our > environment as well. > > > _______________________________________________ > Pauldotcom mailing list > [email protected] > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom > Main Web Site: http://pauldotcom.com _______________________________________________ Pauldotcom mailing list [email protected] http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom Main Web Site: http://pauldotcom.com
