The following are six key aspects a SharePoint architect needs to accommodate:
1) Overview of the architecture
2) Storage
3) Deployment methods
4) Design
5) Sizing considerations
6) Performance tuning
The following are six key aspects a SharePoint architect needs to accommodate:
1) Overview of the architecture
2) Storage
3) Deployment methods
4) Design
5) Sizing considerations
6) Performance tuning
As a SharePoint management consultant, the following are nine key aspects to know about the company whom you will be consulting for:
The following are some good key sites about switching from Google Workspace to SharePoint Online:
Switch to SharePoint Online from Google Sites
Migrate Google Workspace to Microsoft 365 with Migration Manager
https://learn.microsoft.com/en-us/sharepointmigration/mm-google-overview
Migrate from Google Workspace
https://learn.microsoft.com/en-us/sharepointmigration/mm-google-step1-connect?source=recommendations
The following are some good sites which cover Microsoft Pilot AI aspects:
Unleash your Productivity with AI and Microsoft 365 Copilot:
Introducing Microsoft 365 Copilot—A Whole New Way To Work:
Frequently Asked Questions about AI and Microsoft 365 Copilot:
Introducing Microsoft 365 Copilot: Your Copilot for Work:
https://news.microsoft.com/2023/03/16/introducing-microsoft-365-copilot-your-copilot-for-work/
Introducing Microsoft Security Copilot:
https://www.microsoft.com/en-us/security/business/ai-machine-learning/microsoft-security-copilot
Microsoft AI:
The following are several good sites that explain what SharePoint is:
What is SharePoint?
https://support.microsoft.com/en-us/office/what-is-sharepoint-97b915e6-651b-43b2-827d-fb25777f446f
Get Started with SharePoint:
SharePoint - Your Mobile - Intelligent Intranet:
https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration
Create and Use Modern Pages on a SharePoint Site:
SharePoint Help & Learning:
https://support.microsoft.com/en-us/sharepoint
Clarify the following with the relevant stakeholders and team when starting a SharePoint project:
1) Purpose and justification.
2) Measurable objectives.
3) Deliverables.
4) Acceptance criteria.
5) Critical success factors.
6) Constraints and assumptions.
7) Proposed budget and schedule goals.
Real working thought:
It’s important to have a realistic scope in regard to what a SharePoint project will encompass and output. I've been a member of a few projects where the scope was not realistic and on one occasion needed new technology to be built until the proper outcome could be met. This therefore led to potential cost overruns in the budget.
The following are six key aspects about SharePoint that are good:
1. End to end - good platform for distributing content and processes
2. Scale and agility - the platform is updated often and therefore provides a faster deployment strategy as part of it's ecosystem
3. Delivering trust - the system provides a core permission model
4. High availability - the system is made to scale and provides to the enterprise this valuable concept
5. Too integrated to fail - the system provides many out of the box features and functionality as well as allows for customizations
6. Hybrid and multi cloud - the system can be set-up half on-premise and half in the cloud therefore allowing for scalable as needed