How To Successfully Deliver Your SharePoint Change Project In 10 8 Easy Steps Symon Garfield
Jun 01, 2015
How To Successfully Deliver Your SharePoint Change Project In 10 8 Easy Steps
Symon Garfield
Who Am I?
What Am I Going To Talk About?
1. What are you trying to do?
2. How will you know when you’ve done it?
3. Which technology should you use?
4. How to select your partner
5. How to scope a project
6. How to gather “requirements”
7. How to structure your project
8. User adoption & change management
1. WHAT ARE YOU TRYING TO DO?
“In essence, staff want to work together, to share
knowledge, to work informally, to communicate, to
connect across boundaries, and to innovate. They
want to move from a set of happy families defined by
organisational structure to a networked community”UK Public sector SharePoint RFP 2010
“To create a collaborative and inclusive knowledge management platform
that connects [employees] around the world, no matter if they are sitting
at a desk or based in the field, through strong design, relevant and value
added content, robust tools, training and governance, and reflects
business objectives and best practice community that makes us one [client
name]
UK Private sector SharePoint Intranet RFP 2012
“The development of a global intranet will revolutionise the way
[our] people locate and communicate with one another, and
how they share information, innovation and best practice. It
will be one central hub for people to find, share and contribute
information and it will replace isolated failed ventures… has the
ability to improve employee effectiveness and productivity”Global media organisation Intranet RFP 2012
Information Workplace
1. Seamless
2. Contextual
3. Individualised
4. Visual
5. Multimodal
6. Social
7. Quick
Digital Workplace
“Intranets have lasted quite a
while and may well continue in
some shape or form into the
future. However the IBF believe
that the traditional intranet, no
matter what its power and
functionality is now part of the
Digital Workplace….
… The Digital Workplace includes
the intranet but also other
workplace technologies.”
Services model
2. HOW WILL YOU KNOW WHEN YOU’VE DONE IT?
What is a Business Case?
The justification for a change project What is the current situation?
Why is the change needed?
What is being proposed?
What are the costs?
What are the estimated benefits?
When will the benefits be realised?
Who will do the work?
How will success be monitored and reported?
Why do we need a business case?
1.Gaining funding for a proposed project or
change
2.Understanding of current situation and
opportunities
3.Successful co-ordination & management of
stakeholders
4.Prioritisation and selection of projects
What are the dimensions of a business case?
“Technology provides no benefits of its own; it is the application
of technology to business opportunities that produces ROI”
Robert McDowell, “In Search Of Business Value”
3. WHICH TECHNOLOGY SHOULD YOU USE?
4. HOW TO SELECT YOUR PARTNER
What the client
wants is rarely
what the client
needs
5. HOW TO SCOPE YOUR PROJECT
Project Estimates
Discuss• Based on meetings, calls
or emails• Delivered verbally, in
meetings or presentations
• Rough-Order-of-Magnitude +/- 100%
Scope• Based on 5 or 10 days
project scoping• Includes solution concept
& project plan• Level 0 estimate +/- 20%
Discover• Typically 5 to 20 days of
consultancy• Detailed current state
analysis• Prioritised requirements• High-level design• Level 1 estimate +/- 10%
Design• Follows Discover• Typically 5 to 20 days of
consultancy• Detailed technical design
and build plan• Level 2 estimate +/- 5%
Project Scoping Report
1. Executive summary
2. Vision
3. Costs
4. Benefits
5. Work
6. Deliverables
7. Plan
8. Immediate next steps
6. HOW TO GATHER ‘REQUIREMENTS’
Serious Games
User Centred Design
Strategy: Personas & User Needs
Strategy: Product & Business Needs
Scope: Storyboards & user stories
Structure: Information Architecture
Skeleton: Wire Frame Models
Surface: UX & Design
7. HOW TO STRUCTURE YOUR PROJECT
Iterative Project Delivery
Discover
Design
Plan
Execute
Deliver
8. USER ADOPTION & CHANGE
WHAT HAVE I BEEN TALKING ABOUT?
Key messages
1.Beware of abstract visions!
2.Value is directly correlated to purpose
3.The Microsoft platform is a strategic decision
4.Don’t trust a partner who cant assess your needs within a few
days
5.Go for capped budget not fixed price
Key messages
6. Iterative projects that deliver in 90 days reduce risk
7. Serious games and user centred design are great techniques
8. Adoption = Useful + useable
9. Iterative or gradual change
10. Plan & budget for change and adoption from the start
questions?
HTTP://WWW.SYMONGARFIELD.ME.UK
@SYMON_GARFIELD
thank you.
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS ZAGREB, 10/15/2014 - 10/16/2014