How Häme University of Applied Sciences built their intranet on Sharepoint and Yammer and at the same time introduced the whole of O365 to the university.
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
ICT project as an instrument for change - case O365 implementation
1. ICT Project as
an Instrument for Change
- Case O365 Implementation
Lotta Linko,
Häme University
of Applied Sciences
1
2. Agenda
• Changes in the environment &
organisation
• Project management
• Online services for students and staff
• Wins and fails
• Lessons learned
• Developing digital competence
2
3. HAMK University of Applied Sciences
• Located in Southern Finland, 7 campuses
• 7200 students
• 625 teachers and other staff
• 31 degree programs (23 B + 8 M),
professional teacher training, open
university, continuing education
• 4 applied research units
• Medium-sized HEI
3
4. Changes at all levels
• Changes in the global and local
environment: economy, world of work,
technologies (digitalisation)
• Changes in Finnish education: funding,
degree programme structures, national
application system
• Changes at HAMK: programmes, study
modes, management, strategy, IT
infrastructure and technologies
4
6. Supported services for studying and
working
Informative
intranet
- Degree
programme’s
information
- Campus related
info
- Also content for
all students, for
example
educational
guidelines
Completes public
hamk.fi pages and
student’s own page
My Page
- Links provided
by HAMK
- My links (for
example to a
DP’s page)
- Embedded
newsfeeds from
Yammer and
team sites &
followed
persons
- Official bulletins
for all students
- Followed sites,
files and people
- O365 app
launcher
Team sites, Groups
+ OneDrive
- For collaborative
studying and
working (for
example
teamwork)
- Personal cloud
storage
www.hamk.fi
Info on education and programmes, study
practises and services
Peppi
Courses offered,
enrolment for
courses and
modules
Moodle
Studying, course
related contents,
guidance and
communication
Yammer
- Bulletins and
conversations
concerning all
students,
programmes,
campuses, and
anything else
related to
studying &
working
WinhaWille
Enrolment for
implementations
and academic year,
contact info
change, grades
lukkarit.hamk.fi
Schedule service for
groups and courses
oiva.hamk.fi
Mobile service for
groups' timetables,
campus cafeteria
menus, event
calendar and
classrooms
Office Online
- A collection of
MS tools that
can be used
through a web
browser
Delve
Outlook e-mail,
calendar, tasks,
contacts
OneNote
Class Notebook
Staff Notebook
Forms FlowPlanner
O365
video.hamk.fi
Video service
for educational
resources
blog.hamk.fi
Blog service for
students and staff
unlimited.hamk.fi
Publication portal
8. Waterfall vs. agile
Testing Piloting Planning Building Launching Using
8
Testing
Piloting
PlanningBuilding
Launching
Using
Testing
Piloting
PlanningBuilding
Launching
Using
Testing
Piloting
PlanningBuilding
Launching
Using
Testing
Piloting
PlanningBuilding
Launching
Using
Testing
Piloting
PlanningBuilding
Launchin
g
Using
9. HAMK’s intranet project phases
9
20162014 2015
Activate service
4/11/2013
Launch R1.0
8/9/2014
Launch R1.1
23/3/2015
Launch R2.0
22/6/2015
Launch R3.0
21/12/2015
End project
31/12/2015
Start work
7/1/2016
Test
9/12/2013
Pilot
13/1/2014
Plan
24/3/2014
Build
4/8/2014
Use
15/9/2014
Monitor
3/11/2014
Correct
1/12/2014
Develop
5/1/2015
Develop
6/4/2015
Develop
14/9/2015
10. Top 3 factors for success/failure
This we did well
1. Management
commitment
2. Agile development
3. Change mindset
This went less well
1. Change coordination
at HAMK level
2. Change
management at
project level
3. Timing & time
10
11. Organization matters
11
Directors
(HAMK strategy & policies)
Unit managers
(Unit-level goals and resources)
Project team
(Overall planning and joint execution)
• Communication
• Guidelines and instructions
• Online support
• Best practises
• Further development
Campus/program teams
(Local implementation)
• Communication
• Instructions
• Local support
• Field-specific focus
• Program-specific variations
Users
(Everyday studying and working)
12. Don't
• Introduce too many
changes
• Expect rapid change
• Trust things to
happen and people to
act without
management
• Micromanage
• Believe in bells and
whistles
• Think you know best
• Underestimate your
users
• Overestimate your
users
• Be afraid to ask for
help/answers/money
• Wait for the final
product
12
13. Do
• Find the owner
• Work in teams
• Define the use and
keep it simple
• Spell out the benefits
• Change processes
• Manage change
• Prioritize projects and
tasks
• Plan timing realistically
• Communicate & share
• Involve users
• Encourage learning by
example
• Target and measure
• Give up the old
• Grow your digital
competence (open
badges)
13
14. Conclusions
1. It’s not about technology
2. Strategic change needs leadership
3. Digital is not the same for all
4. Agile allows quick and cheap mistakes
5. Choose cloud, choose change
14
15. Next step:
developing digital competence
http://publications.jrc.ec.europa.eu/repository/bitstream/JRC98209/jrc98209_r_digcomporg_final.pdf
15
16. More information
• Lotta Linko,
online communications manager,
lotta.linko@hamk.fi , @viestintalotta
• Ari Kuusio,
chief information officer,
ari.kuusio@hamk.fi
• www.hamk.fi/O365intranet
16
Editor's Notes
There are days when the OMG will spell out ”WTF”.
Office 365 provides tools for collaboration and communication, and it is the case of this presentation. Note that the proportions between different systems as to use or users are not in scale.
HAMK has both waterfall and agile projects. O365 was first bigger agile project although not a ’pure’ one.
The phases are basically the same in both approaches, the scope and speed differ.
The factors that were important to us were product ownerhip, management commitment to decision-making, phased and realistic product versions with clear definitions, task management and assessment in the development periods, procurement in the form of mini competitive tendering via framework agreements, a rapid pace of development, and broad-based team work across unit boundaries.
We have been satisfied with the following elements of the new operating model: We are able to prioritise targets and assignments in a better way, and we can complete sub-entities fairly rapidly by dividing our work into phases. The feedback received on completed work allows us to change plans and make corrections quickly, and it is easy to add content and functionality to existing context. We have also noticed that end users understand a 'finished' product better than abstract plans, although their expectations of the 'finished' product can also be very different!
’Develop’ consists of Plan-Do-Check-Act.
The task include:
Recruiting pilot users, starting test&pilot use, defining the intranet concept, making the action plan, activating staff rights, appointing campus user teams, introducing the new concept to all staff, starting site building, granting students user rights, starting online training, visiting campuses, briefing management, student union, degree heads, tutors, study councellers, providing online help and training, launching the new intranet for all staff and students, discontinuing the old intranets, following user stats, planning open badges for O365, meeting management, commissioning a thesis on the success of project’s change management, piloting a questionnaire on communications practices, making a plan for unifying school communications practices – taking a deep breath and continuing the work
On the plus side:
HAMK management were committed to the change at school right from the start: this was seen as a strategic development project, and staff & time resources were allocated accordingly. (At a personal level, there’s room for improvement.)
Applying agile methodology allowed us to build demand-based and prioritised releases; get visible results, and perform corrective actions rapidly or change minor plans, even.
Choosing cloud meant choosing change, and this could only be done by a team of open-minded experts from different units.
The minuses:
There were too many simultaneous big changes taking place both outside and within the organisation, lead by different units/functions - and unsufficiently coordinated. As resources were limited, projects sometimes ”competed” for the same staff hours.
We should have succeeded better in user involvement at all levels and throughout the project. This would have lead to a more thorough change in the ways of working instead of learning the use of new tools.
Had the circumstances been other, we should have reconcidered the timing of the project: too many changes at the same time is too much to adopt profoundly. Also, as the avant-garde project team we were too optimistic about the total time a change of this calibre will take. Eri vaiheiden eri vauhti.
Some of the lines are dotted and some of the arrowheads are missing – something should have been done in those blank spots.
Regardless of the project implementation model, a new generation tool is a major challenge to an old school organisation - technically, at the concept level, and in terms of operating culture and management. Since many users want to retain old operating methods, induction, training and support are essential elements when initiating a change and achieving the necessary competence and desire. In the same manner, the gap between pioneers and other users must be closed by means of management. Changing an operating culture is much more challenging than technical implementation – but also more rewarding.
In our case a technology project very soon became a development project dealing with the tools and working methods, as well as attitudes in regard to collaboration and the culture of communication. ’IT’ can be seen as the enabler here, and the focus is on people and their ways of working. All this is part of our change journey, inspired by our strategy and dictated by the environment.
Commitment means putting your money where your mouth at all levels of the organisation. In addition to leadership, management and follow-up are a must.
Know your organisation and start where it’s easy in order to get the ball rolling. We have units where the use of O365 is business as usual - and we have people still send e-mail attachments to groups of people and try and schedule meetings with a paper calendar. We also have functions where digital is irrelevant (very few) or the appropriate applications are different.
Agile methodology will let you make prototypes and tests much more safely and quickly than the traditional waterfall. You will fail sooner, learn sooner, and succeed sooner.
We believe that the world and the world of work has changed permanently and will keep on doing so. As a service provider to our internal and external customers, we have to adapt our services and service capability constantly, cost-efficiently, and responsibly to the benefit of all our stakeholders.
Our next step is to take a more holistic view on the digital competence of the organisation. We will use the European Commission’s report ”Promoting Effective Digital-Age Learning. A European Framework for Digitally-Competent Educational Organisations.” as our framework. We have translated the document in Finnish and will apply the relevant sectors in our organization according to an action plan.