Perfect Web
Project?

WiFi: Exove Visitors / visitinternet

Welcome!

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

Perfect web projects.

Do they exist?

Absolutely.

Today we tell you how to
create one.

About us

Exove is a leading Northern European
company specialising in open source
web services design and development.

We enable companies to conduct
better business on the Internet
through best-of-breed personnel
and solutions

Our Approach
Understanding
your business

Our Approach
Understanding
your business
Our expertise

Our Approach
Understanding
your business
Our expertise
Power of open
source

Results
Beautiful, fu
nctional &
business-
driven
services

70 people, over 175 customers,
5.0 MEUR revenue 2013, profitable,
offices in Helsinki, London, Oulu & Tallinn

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

Buying a web
renewal project
North Patrol Oy 2014 / 2014-05-13 / Helsinki18
Perttu Tolvanen, Web & CMS
Expert, @perttutolvanen

© 2014 North Patrol Oy19
Advisor in web renewal
- Helps clients in choosing
partners, selecting
technologies and competitive
bidding
- Independent of digital
agencies and systems suppliers
- Helsinki-based, but most
clients operate in Northern
Europe / Scandinavia / Russia

Agenda
North Patrol Oy 201420
Buyer's
pains
Fix the concept
through a
prototype
Version 1.0 of
the service
quickly live
Two different approaches to a renewal project
A B

Buyer's pains
• Between a rock and a hard place…
– Own management wants results at a fixed price, quickly and with high quality…
– Project manager worries about resource sufficiency…
– Yet partners only talk about agility and the hell of fixed pricing…
• Everyone agrees design and implementation must not be separated…
– But where are partners both Marketing and IT can accept?
• Development of the web has again placed digital agencies into focus…
– But where are the digital agencies that can successfully implement large projects
and even have competencies for the technologies they choose?
– … and if only someone else were using those technologies in this country…
North Patrol Oy 201421

The world has become clearer…
North Patrol Oy 201422
Web service
Web forms, small
apps etc.
"Extranet"
services
("anything that
requires login")
- … but still, many times even
the web service is something
special and the basic functions
of a CMS are not enough.
- For example, communities and
large online stores are typically
challenging.
- Sometimes, extranet services
require a CMS as their
platform.
These are usually two
separate worlds. One is on a
CMS, the other more or less
a customized entity.
+ online store

Two different starting points
• "We are building something totally new and magnificent.“
• "We require top-class design, something awesome!“
• "We want to test with users, and commit our organization to the project."
North Patrol Oy 201423
• "We know pretty well what we want."
• "We want to go live quickly, then use feedback for improvement."
• "We want to buy design and implementation from the same supplier."
Big expect-
ations for
the design
phase
Expect-
ations
focus on
results
A
B

Two different projects
• Concept along "the long road", up to an HTML prototype. Two bidding rounds, two
partners.
North Patrol Oy 201424
• Lightweight concept and project requirements definition. One bidding round, one
partner.
Preparation:
renewal ideas,
goals, restrictions
Concept design: results
in an HTML prototype
Implementation with
model suggested by
selected partner
Big expect-
ations for
the design
phase
Expect-
ations
focus on
results
Preparation: preliminary
concept, goals, restrictions,
functional requirements,
technology selection
Implementation with model suggested by
selected partner
A
B

Technology selection milestones
• Concept along "the long road", up to an HTML prototype. Two bidding rounds, two
partners.
North Patrol Oy 201425
• Lightweight concept and project requirements definition. One bidding round, one
partner.
Preparation:
renewal ideas,
goals, restrictions
Concept design: results
in an HTML prototype
Implementation with
model suggested by
selected partner
Big expect-
ations for
the design
phase
Expect-
ations
focus on
results
Preparation: preliminary
concept, goals, restrictions, fun
ctional
requirements, technology
selection
Implementation with model suggested by
selected partner
A
B

Summary
1. Forget layouts and long wireframe documents
2. Make the design phase properly long, or really short
3. Big choice: Do you first want an HTML prototype for collecting feedback
from users and your organization, OR, do you want to go live quickly with a
1.0 version (in Minimum Viable Product spirit)?
4. If you opt for long design, you can buy the first-phase implementation even
at a fixed price—but don't dictate the implementation model
5. Short design inspires goal-based buying, for which agile methods are
philosophically a good fit
6. Plan the incentive/control system for a goal-based model according to your
own participation resources
– The 50/50/50 model is a good starting point, but there are other viable models
North Patrol Oy 201426

North Patrol Oy 2014 / www.northpatrol.com27
Thank you.

Contact information
NorthPatrol Oy28
Perttu Tolvanen
Web & CMS Expert, Partner
North Patrol Oy
+358 50 368 5199
perttu.tolvanen@northpatrol.com
@perttutolvanen
www.northpatrol.com

Advisor in buying web projects
North Patrol Oy29
We’ll find you a web project
solution that fits your needs
- not something that’s
convenient for a vendor to
build.
More information:
www.northpatrol.com
Our main focus is at the
critical stages of project
planning, defining
requirements and selecting
the best partners.
Additionally we support the
implementation and assess
the results.
North Patrol is your expert in
selecting the best vendors and
technologies for your next web
project.
We are an independent
consulting company without
ties to system vendors, and
can help select the best
implementation plan and
vendor to save you
headaches in the long run.

North Patrol Oy30
BUYER´S GUIDE TO WEB
PROJECTS
www.northpatrol.com/blog

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

„Все вые мьи жи друг на
га, ждая вая
ва - ему.‟
Анна Каренина
Лев Николаевич Толстой

Wireframes
Site map
3 versions of
layouts
Choose best
and develop
further

LEAN
AGILE
SCRUM
CMS
DRUPAL
WORDPRESS
UX
UI
INTERACTION
DESIGN
VISUAL
DESIGN
CONCEPT DESIGN
SERVICE DESIGN
USABILITY
TESTING

CONSUMER
JOURNEY
MAP
FOCUS GROUP
USABILITY TEST
UX
BUSINESS
MODEL
CANVAS
PROTOTYPING
USER STORIES
PERSONAS
USE CASES
SCENARIOS
CARD SORTING
EYETRACKING
A/B TESTING

UI and
UX
BUSINESS
Content
Collaborative
design
Prototyping
UI / UX
testing
Continuous
development
& design

Principles for success
 Collaboration
 Collaborative design – shared understanding
 Design & development
 Lean
 Learn, build, measure
 Avoid waste
 MVP
 Prototyping
 Speed and release
 Continuous discovery and development
 Usability and UX
 Style guide - Device independent
 Test, test, test - GOOB

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

Rebuilding working cultures

PHOTO CREDITS
-ROSS2085-CCATTRIBUTIONHTTP://WWW.FLICKR.COM/PHOTOS/9610484@N05
-BEATPLUSMELODY-CCATTRIBUTION-NONCOMMERCIALHTTP://WWW.FLICKR.COM/PHOTOS/9574497@N07
-SILLYDOG-CCATTRIBUTION-NONCOMMERCIAL-SHAREALIKE
HTTP://WWW.FLICKR.COM/PHOTOS/26084283@N00
-INSOMNIC-CCATTRIBUTION-NONCOMMERCIALHTTP://WWW.FLICKR.COM/PHOTOS/40996284@N00
-THEBARROWBOY-CCATTRIBUTIONHTTP://WWW.FLICKR.COM/PHOTOS/48778414@N04
-JAMESWHEELER-CCATTRIBUTION-NONCOMMERCIAL-SHAREALIKE
HTTP://WWW.FLICKR.COM/PHOTOS/24128704@N08
-MOHAMMADALI-CCATTRIBUTION-NONCOMMERCIAL-SHAREALIKE
Created with Haiku Deck

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

Choose the right tool for
the task
 Different platforms have different pros and cons
 No single platform is the best one for all projects

Platforms (examples)
 CMS
 Drupal
 Wordpress
 Liferay
 Framework
 YII
 Django
 Symfony
 Express.JS

Right tool for the task
 Features
 Extensibility
 Performance
 Support for user-generated content
 Budget
 Others are support for modern server software, size
of the community, availability of vendors on
market, etc.

FEATURES

Features
 Usually the platform offers a selection of features
out-of-the-box
 These can be extended with commercial or free
extensions

Features
 Extension is not the same thing as a core
feature
 Compatibility of different extensions
 Building on extensions is limited

EXTENSIBILITY

Extensibility
 Extensibility offers the possibility for
 unique features for competitive edge
 personalization
 integrations to rare/unique systems
 Extensibility is based on theAPI built on the
platform and the documentation of it
 Frequency ofAPI changes and policy changes

Extensibility
 The best extensibility can be found in
frameworks
 No out-of-the-box features, only libraries for building
 Budget limits, including maintenance
 Extensibility is a key feature and all platforms
claim to offer it
 Check that it‟s actually true

PERFORMANCE

Performance
 If the traffic is anonymous (non-logged in users)
and content updates can lag a couple of
minutes
 Not essential requirement
 Most platforms can be “fixed” with a reverse proxy
 For logged in users, totally different situation
 Commerce is always „logged in‟, even if the users
could shop without logging in

Performance
 Fully user-customized service, like electronic
services, should be either implemented with
some hard-core optimizations to a CMS, or with
a framework
 Scaling with hardware

SUPPORT FOR
USER-GENERATED
CONTENT

Support for user-
generated content
 User-generated content
 Comments
 Forums
 Blogs
 Pictures, video, audio
 Reviews
 Personalization

Support for user-
generated content
 Support for this varies a lot between different
platforms
 In some cases, usage of frameworks is justified
 User groups, user privilege levels, moderation
features etc.

BUDGET

Budget
 Budget can choose the platform for you
 Building on existing platforms varies a lot
 The cheapest and the most expensive platform can
switch places when dealing with different projects
and requirements

Budget
 Anything buildable with a CMS is practically
always more expensive to build on a framework
 Remember, it‟s not just the project, but also the
support and maintenance

Recap
 Choose the right tool for the task
 Accept the limitations of the platform, or switch
platforms
 Choose a platform that executes your key features
natively (as natively as possible)
 Take further development into account
 Control the budget with requirements, not by
platform selection

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

Things to consider
 Support response times
 Security
 Changing technology
 Accidents happen and sites break
 Business changes
 Third party changes
 Application monitoring
 Hosting

What we do?
 Bug fixes
 Small scale development
 Support and maintenance

SCRUM
Why SCRUM doesn‟t work for support?
 Support tasks are unpredictable
 Priorities change all the time
 Sprints are too slow

Kanban to rescue
Better solution for support!
 Makes sure tasks are finished
 Critical issues can be prioritized
 No sprint planning. No waiting

Support hand over
 Documentation will be done
 Backlog should be cleaned
 All the support tickets at one place
 Passwords, git etc. up to date
 Project team can move to the next project

Continuous improvement
 Maintain or increase the value of the site
 Listen to your customers
 Customers know what they want
 Concentrate on the core use cases
 Take small steps
 Iterate and branch from there

How can we help
 We can collect knowledge about the site
 Install tools to follow site performance
 Pinpoint usability and performance issues
 Find solutions to common admin problems
 Help to find out what end users want
 Update systems
 Package larger task for project teams

Agenda
14.00 Opening words Janne Kalliola
14.10 Various ways to approach big
web service renewal
Perttu Tolvanen
14.30 What concept? Saku Sairanen
14.50 Improving your company culture Anu Rautanen, Jussi Markula
15.10 Break
15.20 Possibilities and limitations of
the technical platform
Kalle Varisvirta
15.40 What happens after the project? Janne Patrikainen
16.00 Wrap-up Janne Kalliola
Discussion

Know what you / your
business / your customers
want.

Serve the users.

Get the right vendors and
manage them properly.

Manage also your own
people, processes and
thinking.

Pay close attention to concept
and visual design.

Implement the system using
the right platform.

Remember that your
business starts after the
project ends – prepare for it.

Design. Implement.Analyse. Fix.
Design. Implement.Analyse. Fix.
Design. Implement.Analyse. Fix.
Design. Implement.Analyse. Fix.
Design. Implement.Analyse. Fix.
Design. Implement.Analyse. Fix.

When in doubt, ask
professionals for help.