The Perfect SharePoint Team

SharePoint is very complex and to succeed with it, in the enterprise the following would make-up the perfect SharePoint team: 

Business analyst team - who would be responsible for capturing and documenting business requirements for the various sites, Power Platform aspects, custom code, etc.

Build/Development team - who would be responsible for building and updating the sites and application based aspects.

Quality Analyst team - who would be responsible for testing items before they are deployed to production.

Operations team - who would be responsible for building and maintaining infrastructure for the environment.

Security and compliance team - who would be responsible for ensuring that the deployed items follow the defined security and compliance standards.

Application support team - who would be responsible for supporting the built sites, Power Platform, coded items in production.

15 Ways a SharePoint Team Should Work

SharePoint is an intricate platform and to succeed with it, a team should have the following aspects:

1)      Have a process for a project’s intake

2)      Get good detailed specifications for major projects

3)      Before bringing in consultants, have a clear idea what should be obtained

4)      If new requirements come down the pipe, a process should be in place to remedy efficiently

5)      Have support needed for environment tracked with proper metrics

6)      Eliminate double entry of content into systems (example if a team has a project site for tracking as well as a Team Foundation System (TFS))

7)      Have training for team employees

8)      Have process to prioritize what is being worked on

9)      Focus on communication with other teams

10)  Try to eliminate surprises – be proactive, rather then re-active

11)  When sign-off of project or enhancement is done and changes are needed, a intake process needs to be followed

12)  Have core and key documentation – readily available and organized to all team members

13)  Capture changes team makes to system thoroughly

14)  Project portfolio should be reviewed for proper capacity planning

15)  All team members should be on same page