Microsoft Teams is your hub for teamwork, which brings together everything a team needs: chat and threaded conversations, meetings & video conferencing, calling, content collaboration with the power of Microsoft 365 applications, and the ability to create and integrate apps and workflows that your business relies on.
Microsoft Teams has become the new way to work for over 115 million daily users who come together every day to meet, call, chat, and collaborate. It comes as no surprise that Microsoft has been recognised by Gartner as a Leader for both Meeting Solutions and Unified Communications as a Service in their latest Magic Quadrants.
SMART Teamwork enables groups of people to securely work together and collaborate through a common workspace. Based on Microsoft Teams as part of the Office 365 application suite, it is the hub for team collaboration in that integrates the people, content, and tools your teams needs to be more engaged and effective.
It is both a proven design process for your organisations information architecture, governance templates for Microsoft Team sites, together with a library of previously developed software components for common business scenarios not natively available in Microsoft Teams.
SMART Teamwork is a design methodology for your organisations Information Architecture. The methodology leverages Microsoft best practice, global research and our own experience with a wide range of customers. It provides sample end user look and feel design templates.
SMART Teamwork is also a governance template from Spanish Point for your organisation Microsoft Team sites.
The Spanish Point SMART Teamwork, Provisioning Engine creates Teams and their initial content based on the agreed design.
Individual Teams can be provisioned according to your organisation template using our Provisioning Engine. This makes sure that your collaboration workspaces are created in a consistent manner with control over the features, permissions and metadata.
Read SMART Teamwork Benefits below.
There are some standards patterns and styles to follow when creating a Team site. For example, a Project template may include a Project Initiation Word document, a Risk Register list and a Planner project plan.
A request and approval process to improve governance in the creation of Team sites.
Use your own business practices to improve governance across multiple sites. For example, a Team can be made read-only to archive it, this way it cannot be changed without approval.
The provisioning engine supports the new Microsoft recommended best practice architecture of Hub sites for aggregation across a flat architecture.
