3. • Customer: Osakeyhtiö Hallman
• Known for Harald restaurants and
Trube buns
• Washer premises in Kuopio
• Only little experience in software
projects
Case
&Wednesday, April 10, 13
4. • To minimize the risk in a software project:
• Agile development methods
• Short iterations
• Continuous delivery
• Proof of concept and piloting
• Don’t be afraid of failing, next time you will do
better
What can you learn from this...
Wednesday, April 10, 13
6. • To build a new modern platform,
web, mobile, etc.
• Changing an age old industry with a
car wash service that has:
• Monthly subscriptions
• License plate recognition
The Vision
Wednesday, April 10, 13
7. • Less than one month of work
• The most simple of web UI’s
• Third party software to solve the core problem:
license plate recognition
• Simple production environment
• Simple integration to existing washer controller
system
• ~90 pilot customers
The first version: proof of concept
Wednesday, April 10, 13
10. • The good
• Customers like the simplicity of monthly
subscription
• Certain WOW factor with license plate
recognition
• The bad
• Recognition is a bit slow and people don’t read
instructions
• More sophisticated admin UI is needed
• Network issues are hard to identify
• Washer controller system clearly isn’t designed
for this
Lessons learned vol 1
Wednesday, April 10, 13
12. • A few months of work
• New production environment in the cloud
• Full blown admin UI
• Statistics & logs
• Invoicing
• Responsive web UI for customers
• Marketing and credibility
• Registration and account management for
customers
• Wash history
Next step
Wednesday, April 10, 13
14. • The good
• Able to grow customer base by 400%
• Steady income shows potential in the
business model
• The bad
• Issues still exist with slow recognition and
washer controller software
Lessons learned vol 2
Wednesday, April 10, 13
16. • Get rid of all legacy systems
• Own implementation of the license plate
recognition
• About two months of work
• Only Finnish plates supported at first
• Own implementation of the washer controller
software
• About four months of work
• Works offline as well
Next step
Wednesday, April 10, 13
20. • The good
• Reliability issues solved
• Blazing fast recognition
• Platform finally ready for multiplication!
• The bad
• -
Lessons learned vol 3
Wednesday, April 10, 13
25. • A year of development
• Three different versions and architectures
• Over 20 two week iterations
• About 700 Git commits
• Over 100 production software updates
• Satisfied customer
• Satisfied end users
Summary
Wednesday, April 10, 13