The document outlines a plan to deploy Skype for Business across Astaldi Group, an engineering company with over 11,000 employees in 300 sites across 20 countries. The objectives are to reduce costs, improve meetings and information sharing, and increase productivity. Key aspects of the plan include a phased pilot, training strategy, and timeline. Metrics will measure adoption and efficiencies. A project team is identified to lead the implementation.

1. Skype for Business Deployment
Astaldi Group

2. Agenda
1. Astaldi Key Facts
2. Project Objectives and
Benefits
3. Technical Requirements
4. Project Critical Success
Factors
5. Adoption Strategy
6. Training options and
Adoption resources
7. Pilot Goals and Metrics
8. Project Plan and Key
Milestones
9. Work Breakdown
Structure Diagram
10. RAM Matrix
11. Project Team
12. Skype for Business
Resources

3. Astaldi Key Facts
 Geographical sites:
About 300
 Employees: More than
11.000
 Revenue 2016: € 3 bn
 Global Player in EPC with
an Order Portfolio 2016:
More than € 27 bn
 Approximately 100
Projects in over 20
Countries

4. Project Objectives and Benefits
• Reduce idle time
• Reduce travel expenses
• Improve Meeting Management and Information Sharing
• Increase productivity via maximizing Office 365 investments
Benefits
Objective 1
Enable 4.000 potential users with Skype for
Business online
Objective 2
The project will cover all the Astaldi
geographical sites, third party and mobile users.
Objectives

5. Technical Requirements
• Gradually replace Skype with Skype
for Business for Instant Message,
Online Presence, VOIP phone call,
video call and content sharing.
Initially the complete replacement
is not feasible since It’s not possible
to migrate from Skype to Skype for
Business the contact details and
the conversation history.
• Ensure interoperability with
Polycom Video Conference System
for all the main geographical and
site and Office 365 Applications as
Onedrive and Sharepoint.

6. FACTOR DESCRIPTION
Comprehensive user training plan Variety of training options, call to action across targeted user profiles, well
communicated
Enterprise-wide deployment plan Defined roadmap
Accountable project team Focused roles and responsibilities around readiness activities
Formal end-user pilot End-user testing-scenarios, messaging, training in production environment
Identify Key User in different location Key user identify reoccurring issues raised through the helpdesk, drive
actions if needed (user awareness, helpdesk training, etc.)
Help desk/Support strategy Established tiered support approach, agents validated as ready to support
users
Operations plan Formal plan to monitor health and adoption with mitigation plan
Project Critical Success Factors

7. Adoption Strategy
Lifecycle
approach
Plan-Pilot-
Rollout-
Operations
Align with
Critical
Success
Factor
Key User
Overview
Tailored
Training Plan
Direct End-
User Focus
• The focal point of the SfB Adoption Strategy will be to select a local key-users for each
Astaldi geographical site and utilize them as "ambassadors" or ''champion'‘.
• This key users will represent the link between the central team and the end-users and
during the project they will take responsibility for the local verification/testing to ensure
that the sites operation is not endangered by upgrading the software.
• A ‘’Knowledge Hub’’ will established at a Corporate Level for the training and the support
of the Local Key-Users and the IT Professionals.

8. • Remote knowledge workers
• Office knowledge workers
• Executives
• Key Users
• Desk-less workers
Training options and Adoption resources
RESOURCE AUDIENCE
Quick Reference
Cards
Self-learners
Short online videos
Instructor-led
training and Train
the Trainer
Users needing extra support
Fully customized
training
Strategic groups: Executives
Emails
Posters
Intranet site
• Assess the needs of users in workgroups and departments
• Various training options and resources to accommodate all of them

9. Pilot goals and metrics
• A small group will be identified that can benefit from an early
access to the platform (e.g Information System Department or
Key users).
Technical
 Call quality
 Solution
availability
Scenarios
 Usage
 Device
usability
Efficiencies
 Time to
complete
projects
 User
satisfaction
Go/No-go
decision

10. Project Plan and Key Milestones (1/2)
Phase Macroactivity Activities Deliverables Milestones
Plan Planning and
Analysis phase
• Define business
requirements
• Technical deployment and
Resources pianification
• Project CS Fand metrics
definition
• Assemble the accountable
project Team
• Develop Project Plan and
Roll-Out Strategy
• Training session and material
preparation
• Test Technical Deployment
and network architecture
• Detailed Project Plan and Roll-
Out Strategy
• Communication Plan
• Communication plan and
training material in place
• Successful Network
Assessment
• Project Plan
delivery
Pilot Pilot on a specific
group of user
• Conducting Pilot
• Pilot success Verification
• GO-NO GO Decision
• Pilot goals and metric
confirmed
• Completion of
the Pilot

11. Project Plan and Key Milestones (2/2)
Phase Macroactivity Activities Deliverables Milestones
Rollout Enterprise Roll-
out
Roll out for all the
geographical area
User Training Preparation
IT Pro Training
Project CSF and metrics
definition
• Training materials shared through
different channel
• Completed User and IT Pro
workshop
• Skype for Business
Go-Live
Operation Monitoring and
Support
• Project Document
Submission
• Helpdesk track and
reporting
• Project goals and metrics
confirmation
• Project Package and Project Closure
Report
• Customized Report on issues
resolution and Service Level
• Call Quality Dahboard
• Success Metric
Verification
Goals and
Metrics
Pilot
Planning
Awareness
Strategy
Training
Strategy
Support
Planning
Sample
User
Surveys
HyperCare

12. High Level Project Timeline
Plan
Roll-out
Operation
Pilot
January February March April
Skype for Business Go-
Live
Success Metric
VerificationCompletion of
the Pilot
Project Plan
Delivery
May

13. Work Breakdown Structure Diagram
The diagram below shows the WBS of this project developed up to level 3.
The decomposition logic used is by phase (Pilot, Roll-Out and Operation).
Skype for Business
Deployment
Plan
Planning
Define Governance
Review
Develop
Communication Plan
Develop Project Plan
Network Assessment
Test Network
Architecture
Design
Prepare Helpdesk
Strategy
Define Roll-Out
Strategy
Prepare
Training session and
material preparation
Definition of Pilot
goals and metrics
Pilot
Conduct Pilot
Pilot sucess
verification
Go-No Go Decision
Roll-out
Deploy
Implement Network
Requirements
Deploy SfB software
Configure User
accounts
Polycom conference
system set-up for SfB
Adoption Success
Plan
Project CSF and
metrics definition
Trainings
Users Training
Operation
Technical Training
for IT Professionals
Run, Monitor,
Support
Project Goals and
metrics confirmation
Helpdesk track and
reporting
Conduct Post-Project
Review

14. Project Team
Project Organization and resources needed
FTE by role
Resource FY18
Project Manager 23,0
Application Specialist 13,0
Infrastracture Specialist 32,0
Support Service Role 29
Project Sponsor on demand
Key Users 49,0
Local IT 35,0
Service Owner 8,0
Consultant (Training Services) 39,0
Key Stakeholders 4,0
ProjectTeam
KeyStakeholders&
ProjectGovernance
Project Manager
Application Specialist
Infrastructure
Specialist
Support Service Role

15. Visit the Office 365 Training Center for
scenario based training tracks:
- Completemeetingsolution
- Communicateyour way
Skype for Business Adoption Portal
http://aka.ms/skypeadoptionportal
Skype for Business Quick Start Guides
https://docs.com/OfficeTraining/9869/skype-for-
business-quick-start-guides
Skype for Business Adoption Content
Directory
http://aka.ms/sfbrolloutkit
Continue the Conversation in the Community!
http://aka.ms/sfbcommunity
SkypeforBusinessResources