Where can I find the information on how to write specifications for my Sharepoint team? And lets assume I've never written any sort of project document and don't know for sure officially the right ways to do things in Sharepoint and that all I know comes from poking around.

Where can I find that info?

closed as too broad by Waqas Sarwar MVP May 31 '17 at 20:57

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Could you please review? I think "where can I find the info" is less opinion based. – methodOverload May 31 '17 at 14:58
  • Functional or technical specifications? Anyway: either case, the only good way is to know/have experience on the subject... That's true for any technical area, but it's particularly important for SharePoint, as there's so many approaches/concurrent concepts/traps/dead-ends/. So maybe you'd need to hire someone who knows a bit SharePoint, or considering a good and intensive training. Would you ask where you can find information on how to do surgery (because you can't afford to hire a surgeon/go to a medical school for 10 years)? – Evariste May 31 '17 at 15:14
  • Believe me I know. We can't afford Sharepoint Devs and myself and my boss are too far removed from anybody who can do anything about it. Good for me I guess because I wouldn't have gotten this job otherwise. Bad for me because I hate this and I don't want to do it and I'm also not any good at it. I want to write something that passes for acceptable and get back to dev work. So what you're telling me is to just give up and don't do it? Because I don't have years to gain the experience I'm missing and there's no other option. – methodOverload May 31 '17 at 15:27
  • Also, I don't know the difference between functional and technical specifications. I assume functional? Its supposed to tell our own team and other Sharepoint using units how we would prefer that they use Sharepoint. – methodOverload May 31 '17 at 15:37
  • So you want to coach the German (they always win) Soccer team but don't have a clue what a soccer ball looks like? SharePoint is a beast, a good SP team has about as many members as a soccer team. To coach them you need to understand all positions, roles and plays. You don't have to master them yourself... but if you don't know the distinction between Functional and Technical... I fear you don't even know what ball is. (sorry to be harsh.. better break your dreams now than later) – Danny '365CSI' Engelman May 31 '17 at 16:02

Try thinking about this in a different way:

Who is going to be reading this document? What do they expect to see in it? Ask them. And then ask for feedback when your first draft is completed.

Tech design documents vary widely in structure and form, between organizations and even within them. Take your best guess, spend a couple hours writing up a very rough draft, then ask your colleagues to tell you what's missing or what's redundant, or what needs more or less detail. Then iterate and make it better.

It sounds like your organization doesn't have a lot of experience with formalized procedures for software design. You have a golden opportunity here to establish yourself as the expert.

  • It would be a golden opportunity for someone who wants to be that expert (I didn't want this assignment and don't want others like it and thats hurting me as much as my inexperience with this type of task, I want to code one of these days). But thank you, this was very helpful and constructive. Having principles and method like this is probably better for me than pointing me to a 1500 page book I'm not likely to retain. I do better figuring things out. And you just linked this project to my coding experience. – methodOverload Jun 1 '17 at 0:18
  • Who is going to be reading this? New people on my team and Sharepoint power users in other groups who want to create and manage their own sites (my team is the core Sharepoint support team, we used to be able to afford actual experts). What do they expect to see? You're right I should ask. I expect they would want a complete tutorial but we can point them to that. What I'm supposed to provide is how WE want them to approach things. – methodOverload Jun 1 '17 at 0:28

Not the answer you're looking for? Browse other questions tagged or ask your own question.