IncreasingProject
EfficiencyusingMicrosoft
TeamsHow to successfully adopt Microsoft Teams
within your Project Management Practices
Haniel Croitoru
April 2 2019
MAIN PILLARS OF PROJECT MANAGEMENT
MAIN PILLARS OF PROJECT
MANAGEMENT
Communication Collaboration Notification & Reporting
FORMS OF COMMUNICATION
80% of Project Manager’s
time is typically spent
communicating
Burn-down/Burn-up Plan
Risk & Issue Log
Action Items
Change Request Log
Status Reports
Meeting Minutes
Decision Log
Communication
IMPACT OF COMMUNICATION ON PROJECTS
Does communication
really matter on project
success?
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
Project Goals Met Project Delivered Within Budget Project Delivered On Time
Effective Ineffective
Source: PMI’s Pulse of the Profession™ In-Depth Report: The Essential Role of Communications
COMMUNICATE AT ALL LEVELS
Communication needs
to be effective at all
levels of the project
team and organization
Senior Leadership
Team
Project Sponsors &
Key Stakeholders
Project
Team
Silent
Stakeholders
Internal
Stakeholders
Internal Project Members
External Stakeholders
n
Collaboration - WORK TOGETHER IN A SMART WAY
Provide the right information
in the right format
to the right person
at the right time
Working together
requires a common
base for content
COLLABORATION REALITY CHECK
• Document duplication
• Poor access control and audit trails
• Finding information is tedious
• Lack of consistency between project
sites
In many organizations,
information is poorly
managed today
• Document duplication
• Poor access control and audit trails
• Finding information is tedious
• Lack of consistency between project sites
NOTIFICATION & REPORTING
A Project Manager
should always know
what is happening
PROJECT MANAGEMENT OVERVIEW
INTRODUCTION TO MICROSOFT TEAMS SCENARIOS:
• PROJECT COMMUNICATION
• PROJECT COLLABORATION
• PROJECT NOTIFICATIONS
LET’S TALK – OPEN Q&A
ed collaboration tool
Microsoft Teams
•Centered around
conversations
•Rich integration with
other systems and
services
•Mobile ready (Android,
iOS)
Chat-based collaboration tool
MICROSOFT TEAMS
What makes up a Team
Async Communications
Enable users to respond when they can
PEER-TO-PEER
Leverage Skype for Business-like instant messaging
TEAM CHANNELS
Each Team can have multiple channels to keep conversations focused
RICH CONTENT
Keep conversations fun and informative through images, links, and memes
MEETING SCHEDULING
Meetings automatically synchronize with Skype for Business
EMAIL CHANNELS
Email conversations can be brought into Team by emailing a channel
REAL-TIME COMMUNICATIONS
Leverage Skype for Business-like instant messaging
AUDIO/VIDEO CHATS
Conduct real-time online conversations with your team members
AUDIO/VIDEO CHATS
Background Blurring and Real-time Translations
USER ACCESS AND SECURITY
Provide access only to those who should have access to the Team
TEAM PRIVACY
Teams can be public to the entire organization or private to specific users
ADDING USERS
Users can be added from another team
DATA LOSS PREVENTION (DLP)
Enables you to identify, monitor, and automatically protect sensitive information
INTEGRATIONS
Enrich your team’s by incorporating external information
ADDING TABS TO CHANNELS
Integrate content form other SaaS services into Teams
ADDING CONNECTORS TO TEAMS, CHANNELS, AND CHATS
Integration with other applications using connectors to automatically feed information into Conversations
INTEGRATION WITH FLOW
Access data and post information to Team and Channels using Flow
BOTS
Bots simplify the FAQ and to do experience
BOT INTEGRATION
Microsoft Teams leverages Bots to educate your users
TEAM ARCHIVING
Keeping the information in an unaltered way
PROJECT MANAGEMENT OVERVIEW
INTRODUCTION TO MICROSOFT TEAMS
SCENARIOS:
•PROJECT COMMUNICATION
•PROJECT COLLABORATION
•PROJECT NOTIFICATIONS
LET’S TALK – OPEN Q&A
CONSOLIDATE CONVERSATIONS
• Leverage Teams and Channels for communication
• Depending on organization and project structure, channels may
represent different entities (departments, functional teams, etc.)
Considerations
Content that may be relevant beyond a project
Should it be in the project Team/Channel or functional one?
Any conversations are easily searched by users from anywhere within
Teams, while respecting security
Keep conversations in Teams. Email is so 2015!
F
CIRCLE OF TRUST
• Should users outside of your organization or project team be able to
read the conversations?
Considerations
Today, once you grant access to a team/channel, users can see the
content it
Keeping conversations to a limited set of individuals
CIRCLE OF TRUST
• You can choose who can email
a channel
• You should create a less cryptic
alias that is easy to remember
Keeping conversations to a limited set of individuals
For organizations with no more than 5,000 users, org-wide teams can be leveraged
ORGANIZATIONAL-WIDE TEAMS
• Only global admins can create
org-wide teams
• All global admins are owners of
org-wide teams
• Allow only owners to post to
General channel
• Turn off @team and @[team
name] mentions
• Automatically favorite important
channels
Leverage teams for small to medium-sized organizations
For organizations with no more than 5,000 users, org-wide teams can be leveraged
C
Considerations
• Microsoft Teams meetings live inside Office 365
• Not associated with any specific group entity
BRING TEAMS CLOSER TOGETHER
Leverage video conferencing
Migrate video conferencing meetings to Microsoft Teams meetings
BRING TEAMS CLOSER TOGETHER
• Review materials discussed during a video chat session
• Work with global teams without worrying about the language barriers
• Up to 250 participants in a meeting
Leverage video conferencing
Considerations
• Automatic transcription and time coding
• Caption reading and full conversation
searches
• Real-time translation
• Blur Surrounding
• Automatic facial recognition to attribute
comments to user
CONVERSATIONS ON THE GO
Participate in conversations anytime from anywhere
• Mobile apps provide rich functionally to stay connected
with project teams
Considerations
• Majority of organizations today have a mobile workforce
FEED THE CONVERSATIONS
Bring in additional information that is relevant to your project
• Incorporate additional content directly to the conversations using connectors
Considerations
• Users get to remain in one app rather than checking multiple locations
• Notifications are real-time
PROJECT MANAGEMENT OVERVIEW
INTRODUCTION TO MICROSOFT TEAMS
SCENARIOS:
•PROJECT COMMUNICATION
•PROJECT COLLABORATION
•PROJECT NOTIFICATIONS
LET’S TALK – OPEN Q&A
STANDARDIZE PROJECT TEAMS
• Create a Team from an Existing one
• Channels, tabs, settings, apps, and members can be copied over
Considerations
• Tabs can be copied over, but will need to be configured
• Content will not be copied
• Sharepoint (Office 365 Group) customizations are not copied
Reduce confusion by following a consistent structure for your teams
TAKING NOTES
• A OneNote is associated with every Team/Channel
• Capture unstructured meeting minutes
Considerations
• Leverage extensive functionality in OneNote for searching content
• Add Meeting details directly into OneNote
Each meeting should be followed by minutes
FILE SHARING
Manage all project artefacts from a single location
• Each Channel has its own folder in the Team’s Office 365 Group Shared Document Library
Considerations
• Ensure everyone is working on the latest version
• For different permissions, need to use different Teams or SharePoint sites
• Integrate storage from other SharePoint, DropBox, Box, or Google Drive sources
• Open directly from mobile device
• Promote documents to their own tabs in a Channel (e.g. SOW)
Async Communications
PROJECT MANAGEMENT OVERVIEW
INTRODUCTION TO MICROSOFT TEAMS
SCENARIOS:
•PROJECT COMMUNICATION
•PROJECT COLLABORATION
•PROJECT NOTIFICATIONS
LET’S TALK – OPEN Q&A
Enable users to respond when they can
GET NOTIFIED OF WHAT MATTERS MOST
Considerations
• Surfacing content inside Teams saves
time and keeps the team informed
• Automate manual tasks through bots
• Share content from a specific account
with the entire project team
• Leverage Flow to further automate
notifications
Keeping up-to-date should be effortless
• Microsoft Teams includes a rich collection of Connectors, Bots, and Tabs to surface information from other systems
TAKE A BREAK… YOU DESERVE IT
When your work is done, there’s no need to be constantly notified
• Microsoft Teams supports Quiet Hours
Considerations
• Set Quiet hours on your mobile device during
off-time
PROJECT MANAGEMENT OVERVIEW
INTRODUCTION TO MICROSOFT TEAMS
SCENARIOS:
•PROJECT COMMUNICATION
•PROJECT COLLABORATION
•PROJECT NOTIFICATIONS
LET’S TALK – OPEN Q&A
THANK YOU
Organizers, Sponsors and
You for making this
possible.
Let’s continue the conversation
• SoHo Dragon LinkedIn Page
• SoHo Dragon Twitter Page
• Hello@SoHoDragon.com
• https://sohodragon.nyc/

Presentation on Microsoft Teams

  • 2.
    IncreasingProject EfficiencyusingMicrosoft TeamsHow to successfullyadopt Microsoft Teams within your Project Management Practices Haniel Croitoru April 2 2019
  • 3.
    MAIN PILLARS OFPROJECT MANAGEMENT MAIN PILLARS OF PROJECT MANAGEMENT Communication Collaboration Notification & Reporting
  • 4.
    FORMS OF COMMUNICATION 80%of Project Manager’s time is typically spent communicating Burn-down/Burn-up Plan Risk & Issue Log Action Items Change Request Log Status Reports Meeting Minutes Decision Log Communication
  • 5.
    IMPACT OF COMMUNICATIONON PROJECTS Does communication really matter on project success? 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% Project Goals Met Project Delivered Within Budget Project Delivered On Time Effective Ineffective Source: PMI’s Pulse of the Profession™ In-Depth Report: The Essential Role of Communications
  • 6.
    COMMUNICATE AT ALLLEVELS Communication needs to be effective at all levels of the project team and organization Senior Leadership Team Project Sponsors & Key Stakeholders Project Team Silent Stakeholders Internal Stakeholders Internal Project Members External Stakeholders
  • 7.
    n Collaboration - WORKTOGETHER IN A SMART WAY Provide the right information in the right format to the right person at the right time Working together requires a common base for content
  • 8.
    COLLABORATION REALITY CHECK •Document duplication • Poor access control and audit trails • Finding information is tedious • Lack of consistency between project sites In many organizations, information is poorly managed today
  • 9.
    • Document duplication •Poor access control and audit trails • Finding information is tedious • Lack of consistency between project sites NOTIFICATION & REPORTING A Project Manager should always know what is happening
  • 10.
    PROJECT MANAGEMENT OVERVIEW INTRODUCTIONTO MICROSOFT TEAMS SCENARIOS: • PROJECT COMMUNICATION • PROJECT COLLABORATION • PROJECT NOTIFICATIONS LET’S TALK – OPEN Q&A
  • 11.
    ed collaboration tool MicrosoftTeams •Centered around conversations •Rich integration with other systems and services •Mobile ready (Android, iOS) Chat-based collaboration tool
  • 12.
  • 13.
    Async Communications Enable usersto respond when they can
  • 14.
    PEER-TO-PEER Leverage Skype forBusiness-like instant messaging
  • 15.
    TEAM CHANNELS Each Teamcan have multiple channels to keep conversations focused
  • 16.
    RICH CONTENT Keep conversationsfun and informative through images, links, and memes
  • 17.
    MEETING SCHEDULING Meetings automaticallysynchronize with Skype for Business
  • 18.
    EMAIL CHANNELS Email conversationscan be brought into Team by emailing a channel
  • 19.
    REAL-TIME COMMUNICATIONS Leverage Skypefor Business-like instant messaging
  • 20.
    AUDIO/VIDEO CHATS Conduct real-timeonline conversations with your team members
  • 21.
    AUDIO/VIDEO CHATS Background Blurringand Real-time Translations
  • 22.
    USER ACCESS ANDSECURITY Provide access only to those who should have access to the Team
  • 23.
    TEAM PRIVACY Teams canbe public to the entire organization or private to specific users
  • 24.
    ADDING USERS Users canbe added from another team
  • 25.
    DATA LOSS PREVENTION(DLP) Enables you to identify, monitor, and automatically protect sensitive information
  • 26.
    INTEGRATIONS Enrich your team’sby incorporating external information
  • 27.
    ADDING TABS TOCHANNELS Integrate content form other SaaS services into Teams
  • 28.
    ADDING CONNECTORS TOTEAMS, CHANNELS, AND CHATS Integration with other applications using connectors to automatically feed information into Conversations
  • 29.
    INTEGRATION WITH FLOW Accessdata and post information to Team and Channels using Flow
  • 30.
    BOTS Bots simplify theFAQ and to do experience
  • 31.
    BOT INTEGRATION Microsoft Teamsleverages Bots to educate your users
  • 32.
    TEAM ARCHIVING Keeping theinformation in an unaltered way
  • 33.
    PROJECT MANAGEMENT OVERVIEW INTRODUCTIONTO MICROSOFT TEAMS SCENARIOS: •PROJECT COMMUNICATION •PROJECT COLLABORATION •PROJECT NOTIFICATIONS LET’S TALK – OPEN Q&A
  • 34.
    CONSOLIDATE CONVERSATIONS • LeverageTeams and Channels for communication • Depending on organization and project structure, channels may represent different entities (departments, functional teams, etc.) Considerations Content that may be relevant beyond a project Should it be in the project Team/Channel or functional one? Any conversations are easily searched by users from anywhere within Teams, while respecting security Keep conversations in Teams. Email is so 2015!
  • 35.
    F CIRCLE OF TRUST •Should users outside of your organization or project team be able to read the conversations? Considerations Today, once you grant access to a team/channel, users can see the content it Keeping conversations to a limited set of individuals
  • 36.
    CIRCLE OF TRUST •You can choose who can email a channel • You should create a less cryptic alias that is easy to remember Keeping conversations to a limited set of individuals
  • 37.
    For organizations withno more than 5,000 users, org-wide teams can be leveraged ORGANIZATIONAL-WIDE TEAMS • Only global admins can create org-wide teams • All global admins are owners of org-wide teams • Allow only owners to post to General channel • Turn off @team and @[team name] mentions • Automatically favorite important channels Leverage teams for small to medium-sized organizations For organizations with no more than 5,000 users, org-wide teams can be leveraged
  • 38.
    C Considerations • Microsoft Teamsmeetings live inside Office 365 • Not associated with any specific group entity BRING TEAMS CLOSER TOGETHER Leverage video conferencing Migrate video conferencing meetings to Microsoft Teams meetings
  • 39.
    BRING TEAMS CLOSERTOGETHER • Review materials discussed during a video chat session • Work with global teams without worrying about the language barriers • Up to 250 participants in a meeting Leverage video conferencing Considerations • Automatic transcription and time coding • Caption reading and full conversation searches • Real-time translation • Blur Surrounding • Automatic facial recognition to attribute comments to user
  • 40.
    CONVERSATIONS ON THEGO Participate in conversations anytime from anywhere • Mobile apps provide rich functionally to stay connected with project teams Considerations • Majority of organizations today have a mobile workforce
  • 41.
    FEED THE CONVERSATIONS Bringin additional information that is relevant to your project • Incorporate additional content directly to the conversations using connectors Considerations • Users get to remain in one app rather than checking multiple locations • Notifications are real-time
  • 42.
    PROJECT MANAGEMENT OVERVIEW INTRODUCTIONTO MICROSOFT TEAMS SCENARIOS: •PROJECT COMMUNICATION •PROJECT COLLABORATION •PROJECT NOTIFICATIONS LET’S TALK – OPEN Q&A
  • 43.
    STANDARDIZE PROJECT TEAMS •Create a Team from an Existing one • Channels, tabs, settings, apps, and members can be copied over Considerations • Tabs can be copied over, but will need to be configured • Content will not be copied • Sharepoint (Office 365 Group) customizations are not copied Reduce confusion by following a consistent structure for your teams
  • 44.
    TAKING NOTES • AOneNote is associated with every Team/Channel • Capture unstructured meeting minutes Considerations • Leverage extensive functionality in OneNote for searching content • Add Meeting details directly into OneNote Each meeting should be followed by minutes
  • 45.
    FILE SHARING Manage allproject artefacts from a single location • Each Channel has its own folder in the Team’s Office 365 Group Shared Document Library Considerations • Ensure everyone is working on the latest version • For different permissions, need to use different Teams or SharePoint sites • Integrate storage from other SharePoint, DropBox, Box, or Google Drive sources • Open directly from mobile device • Promote documents to their own tabs in a Channel (e.g. SOW)
  • 46.
    Async Communications PROJECT MANAGEMENTOVERVIEW INTRODUCTION TO MICROSOFT TEAMS SCENARIOS: •PROJECT COMMUNICATION •PROJECT COLLABORATION •PROJECT NOTIFICATIONS LET’S TALK – OPEN Q&A Enable users to respond when they can
  • 47.
    GET NOTIFIED OFWHAT MATTERS MOST Considerations • Surfacing content inside Teams saves time and keeps the team informed • Automate manual tasks through bots • Share content from a specific account with the entire project team • Leverage Flow to further automate notifications Keeping up-to-date should be effortless • Microsoft Teams includes a rich collection of Connectors, Bots, and Tabs to surface information from other systems
  • 48.
    TAKE A BREAK…YOU DESERVE IT When your work is done, there’s no need to be constantly notified • Microsoft Teams supports Quiet Hours Considerations • Set Quiet hours on your mobile device during off-time
  • 49.
    PROJECT MANAGEMENT OVERVIEW INTRODUCTIONTO MICROSOFT TEAMS SCENARIOS: •PROJECT COMMUNICATION •PROJECT COLLABORATION •PROJECT NOTIFICATIONS LET’S TALK – OPEN Q&A
  • 50.
    THANK YOU Organizers, Sponsorsand You for making this possible. Let’s continue the conversation • SoHo Dragon LinkedIn Page • SoHo Dragon Twitter Page • Hello@SoHoDragon.com • https://sohodragon.nyc/

Editor's Notes

  • #4 Communication and Collaboration involves people Notification & Reporting doesn’t and shouldn’t
  • #5 What varies in communication are the following: Medium Frequency Audience Triggers
  • #6 80% of projects delivered by organizations considered highly effective communicators meet their original goals, versus only 52 percent at their minimally effective counterparts. highly effective communicators are also more likely to deliver projects on time (71 percent versus 37 percent) and within budget (76 percent versus 48 percent).
  • #10 Good communication has to be open and easily accessible
  • #16 You can edit or delete your chat messages during the first 24 hours after they are posted. In the upper-right corner of the chat message, click or tap the More options icon (…), and then choose Edit or Delete.
  • #18 The Meetings icon on the app bar is currently enabled only for users whose mailbox is on Office 365 multi-tenant and a select few dedicated users whose mailbox location can be discovered using Exchange auto discovery.
  • #19 The Meetings icon on the app bar is currently enabled only for users whose mailbox is on Office 365 multi-tenant and a select few dedicated users whose mailbox location can be discovered using Exchange auto discovery.
  • #21 The group email conversation remains in Microsoft Outlook. In Microsoft Teams, Office 365 Group members can use chat to communicate in a separate service within Teams. Microsoft Teams team names appear in the Outlook global address book
  • #22 The group email conversation remains in Microsoft Outlook. In Microsoft Teams, Office 365 Group members can use chat to communicate in a separate service within Teams. Microsoft Teams team names appear in the Outlook global address book
  • #26 You can add email distribution lists and mail-enabled security groups as members of a team. But, if you later add more members to the distribution list or security group, those members are not automatically added to the team. You must add the new members separately or add the distribution list or security group to the team again. (If you add the distribution list again, deduplication makes sure members are added only once.) The team continues to function as-is. All data remains and all existing users can continue to use the team. If the removed user was the only owner of the team, an IT admin can retake control of the team by going through the Office 365 admin center and adding themselves or someone else as the team owner. The team recognizes that change. Any connectors added to the team by the removed user do stop working. Scheduled meetings continue to work because they're on the group calendar. Files and conversations are retained.
  • #27 For the full Microsoft Teams experience, every user should be enabled for Exchange Online, SharePoint Online, and Office 365 Group creation. Users' Exchange mailboxes can be hosted online or on-premises. Users hosted on Exchange Online or Exchange Dedicated vNext can use all the features of Microsoft Teams. They can create and join teams and channels, create and view meetings, modify user profile pictures, add and configure connectors, tabs, and bots, and they can chat and call.
  • #28 https://msdn.microsoft.com/en-us/microsoft-teams/tabs There are Microsoft Teams samples in our GitHub repositories for you to clone or download: 'Maps' tab sample. This is the simple example that is used in this documentation. Simple Todo List tab sample. This Node.js sample shows how easy it is to convert an existing web app into a tab.
  • #29 https://dev.office.com/microsoft-teams
  • #30 https://dev.office.com/microsoft-teams
  • #33 https://msdn.microsoft.com/en-us/microsoft-teams/tabs