SharePoint Admin and Developer Roles [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 6 years ago.

Currently in our organization we have a three man SharePoint development team where we do everything other than SharePoint admin.

Our organization has development, test, and production servers.

We, the development team, have the ability to deploy web parts to the dev server but not to test or production.

This has become quite a nuisance having to wait for the admin to get around to deploying our web parts to test and then to production.

Does anyone else have a similar experience or is our organization setup wrong?

Do developers normally have access to deploy web parts to test and production?

Answer 1

Do developers normally have access? It depends on the company and it depends on the project. I've worked on projects where I deploy all the way up to production, and I've worked on projects where my involvement ends when an admin deploys to test.

Do developers want access? Naturally.

Do admins want developers to have access? Not typically.

Is your organization set up wrong? Ask your boss?

Admins are gate keepers, it's what they do. Is it annoying for developers? Yeah, but admins need to feel important somehow.

Is there a reason admins block developers from dropping code on their servers all willy-nilly? Yeah, because a lot of bad developers think they're good developers.

There's two sides to the coin.

Answer 2

I would say that developers normally have access to at least test. I am a SharePoint Consultant-Developer and at most of my clients we have some access to a test server. Of course it matters the importance of test and the size of the org. Our big clients it is hard to get on test, or we have to make new test servers for each project. At smaller clients usually there is some access. It sounds like they do not trust developer, which seems normal with SP devs as well. I would say find out the reason.

Is it the admins being paranoid or is test really that volatile?

I can see how it would slow you down and it would piss me off too.

Answer 3

That's typical. Admins are normally responsible for keeping the servers and applications running up and available. If they aren't the ones deploying the solutions, you cut them out of the loop and they then have difficulty supporting their servers and applications.

They are the ones getting called initially when applications and servers aren't beahving normally. If they don't know what is being developed installed and deployed, it makes things more difficult for them.