2. • Group and client
• Value proposition statement
(in past tense)
• Options to deliver
• Risks
Run fast, tell tale later.
4. LRS Development
Client: Simon Alefesio-Tuck
(Partnerships Ranger, DOC)
Team Members: Lauren Parker
Rickie Kewene
Sam Stewart
5. Value Proposition
• Address the problem of domestic dog
interaction with wildlife on our beaches.
• Reduction in harm to wildlife.
• Increase public awareness with regards to
local wildlife.
• Reduction costs to DOC and local councils.
6. Solutions
• Update current informative materials
– Brochures etc.
• Mobile applications and website.
• Notifications via social media.
7. Risks
Risks Solutions
Scope Creep • Stick as close to the project plan
Public Adoption • Advertising and marketing
• Social Media
Technical Knowledge • Learning the required information
16. Value Proposition
We provided a system that allows a user to control a computer through the use of
eye tracking and speech recognition software for our client’s research towards
making eye tracking a more efficient and convenient computer interface
option.
17. Delivering a Solution
● Speech Recognition
o Google Speech API
o Microsoft Speech Recognition
o Dragon NaturallySpeaking
● Eye Tracking
o Tobii EyeX
o Pupil
o GazePoint
18. Risks
● Distance communication with the client
● Lack of knowledge in human interface design
● Multiple Consultants
● Complex ethical considerations
22. Value Proposition
AbacusBio need up to date status
information on their roaming consultants.
The problem is ubiquitous
AbacusBio wishes to expand on the
solution to service the specific needs of
other organisations
24. Delivering the solution
Create a flexible cross platform
application that addresses the needs of a
range of workplace environments
Digital technology free solutions:
White board system
Card ticketing system
25. Potential Risks
Privacy issues of users
A similar system is brought to market by
another organisation during the course of
the project
Complex liability
28. Value proposition
•This project has helped to address the issue of
road cyclists safety, with how vehicles are
passing cyclists. The system has been in use
since August 2015. During this time the system
has been recording vehicle passing speeds and
distances showing the problem areas where
dangerous incidents have been occurring. The
system has shown that 35% of vehicles are
passing cyclists dangerously.
29. Possible solutions
•Forms and & surveys
•Smart phone app, Micro controller or
embedded system
•Widen all of the Dunedin roads
47. Value Proposition
• PAinT has addressed the idea of rapid
prototyping development through 'Technology
Mediated Community Engagement'.
• This approach was trailed at Otago Polytechnic in
2015 with the goal of raising student’s
awareness of the environment around them and
bringing focus to the 'Living Campus Project'.
• The success has been measured by tracking
interest and attendance of the workshops and by
using a survey to gauge student awareness.
49. Risks
• Scope Creep.
• Lack of Interest in Workshops.
• Lack of Experience.
• Lack of Resources/Funds.
• Direct Stakeholders Failing to Deliver.
• Poor Time Management.
51. Mobile Development by Badger Republic
Team
Members:
Client: Patrik Larsson
Matthew Chipping
Glenn Richards
Chris Wong
52. Initial Value Proposition
● The GaSuCo project has addressed the request of
Patrik Larsson and have successfully replicated the
board game.
● When tested with focus groups, we received the
same or better user experience in comparison to the
board version of the game.
53. Possible Solutions
● Build an App of the GaSuCo game.
○ iOS
○ Android
○ Windows
● Build an electronic device containing a screen with
the digital version of GaSuCo game installed onto it.
54. Risks
● Members in this project are not technically qualified.
○ Upskill our knowledge
● Final product not meeting client’s expectation.
○ Constant communication with the client
● Project scope.
○ Keep project to one platform.
57. InTeraction’s project has addressed the
opportunity of using rapid hardware
prototyping to facilitate playful interaction
design.
We have developed 3 working prototypes in
association with PAinIT’s workshops, to
promote sustainable practices in local
communities.
58. HOW WILL WE ACHIEVE
THIS?
We will be utilizing common prototyping
systems
• littleBits
• Phidgets
• Raspberry Pi & Arduino
to develop hardware that is designed by the
community, for the community.
59. RISKS
Risk Mitigation
We can’t develop a
prototype within time
constraints
Ensure prototypes have a
narrow scope & the
community has reasonable
expectations
Workshops don’t result in
a clear concept to develop
Drive workshop
discussion to a clear
outcome, or liaise with
client to determine
requirements
We don’t have the
resources required to
build the prototype
Liaise with client to
modify the requirements.
60. AND HAPPY BIRTHDAY
we heard it’s Ian’s birthday today
🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂
🎂🎂🎂🎂🎂🎂🎂🎂🎂🎂
(that’s 29 candles)
63. Who we are
● Third Year BIT Students - Project Helios.
● Vaughn - Astronomy Nerd. I build
telescopes.
● Chris (@opetheater) - Geek. Tinkerer.
64. Value Proposition Statement
Our project addresses ways to make
astronomy and space easily approachable to
Dunedin’s citizens and allow people to see their
connection to the world around them.
Why?
● People want to know
● Economic value
● Now is the time
65. Possible Solutions
Think “local weather forecast” for seeing an
aurora in Dunedin
● Magnetometer and all-sky camera
● Citizen science (Crowdsourcing scientific
participation)
66. Risks to success
Risk Management
Client’s deadlines Negotiate with OP
Runaway scope (Our enthusiasm) Manage our own and client’s expectations
(Under promise, over deliver)
We are at an early stage in defining our
relationship with our client and their needs
Iterative approach. Two-way
communication. Be prepared to negotiate.
The unknown (Spanners) Know what we are doing at the time and if
anything comes up we are communicating
with all stakeholders. Seek advice from
experts early and often.
67. Who am I?
Scott Milne
My Client
Lychelle Guyan - Waitaki District Council
68. Value Proposition
The Building Inspection project has addressed the problem of digitizing
building inspections without increasing processing time and allowing access
to previous inspections.
It has been in use by the Waitaki District Council since June 2015, in which
building inspections have noted a decrease in time processing consents.
After deployment administration staff and building inspectors have been able
to process consents faster with all information being accessible on the
computer without looking up the physical property file.
69. Options
• A mobile app with live access to the
database
• A laptop with a connection into the current
system (Civica - Authority)
Authority
Database
70. Risks
Risk Action to avoid/minimize
Users not using the software
Involve the users with the project to ensure
they feel part of it.
New Technologies Research, learn and get help if required
73. Problem
<Objective>
To create a tool that Central Otago RailTrail users can use to
better educate themselves to survive and inform them of
points of interest along the trail.
<Business Objective>
To provide paid advertisements to the user via pin point
prompts.To encourage growth for business in the
Middlemarch community.
75. Project Risks
Risks Solutions
Remote client Arrange meetings around their trips to
Dunedin. Use phone and email.
Mobile platform Make an informed decision on platform -
IOS/Android.
Mobile Service Develop the system around having no mobile
network access. The system will be fully saved
to the device.
Uptake Ensure that we have the right mix between
useful information and adverts.
GPS Experiment with how often we need to check
a location VS how fast the battery will drain.
78. Initial Value Proposition
The Digital Way Finding project has
addressed the opportunity of having
“interactive kiosk” like system,
featuring specialised hardware and
software that will provide access to
the information provided by the
Polytechnic to the end users.
79. Delivering The Solution
CMS(Content Management System)
- Allows Publishing, Editing, and Modifying content,
organizing, deleting as well as maintenance from a
“Central Interface”
Screen with Touch Interface
-Allow users to navigate and extract information the
smart way.
84. Morgan Oliver has the intention to create an
Augmented Reality app for the Olvestion
House. He has created an app but this has not
fulfilled his desire of using it as an AR toy
hunt. He requires an app that will show 3D
models from around the garden and then give
some sort of progress on how many images
you have found.
85. Use the Junaio app to scan QR codes and
connect to our channel.
Create an app using the Junaio SDK that the
user would acquire prior to visit.
Purchase several tablets pre-installed with our
app.
86. Risks Involved Solutions
Cost of SDK Dev licence Continue using free licence and work
around limitations.
Stable tracking images Using hard material that does not
reflect light and will resist corrosion.
Weather & Forestry Place tracking images in sheltered &
stable ground away from possible
overgrowth.
Olveston backing out Variety of potential clients.
89. Value Proposition
Statement
Project ICE has addressed the
problem with a lack of
communication and coordination
tools available during remote disaster
recovery simulations at Motor Trade
Finance. It has been in use since
August 2015 during simulations in
which it has cut recovery time by
50%.
90. Delivering the Solution
A Tablet for every staff member
involved to be used like a digital
checklist.
A Web based application, easily
accessible to everyone with a
browser.
Private Conference calls and
notepads.
91. Risks
Risks Why Solutions
Security
Dealing with
sensitive
information
Hide sensitive
information using
access control
Unrefined
Processes
MTF new to
remote disaster
recovery
Regularly meet
with client to
update
requirements
Training
Switching from
written to digital
Close contact
with users
94. Value Proposition Statement
Our project has addressed the problem of communication
within the Southern District Health Board in the case of
emergencies such as snow days, virus outbreaks…etc. It
has been in use since October 2015, in which time it has
informed SDHB medical staff of emergencies with a 40%
reduction in staff confusion and panic during emergencies.
99. Value
Value Proposition
FeedMe will address the problem of excess food
wastage in the hospitality industry. This system will be
deployed at several events later in the year and will see
a reduction in food waste at these events.
Proof of value
Food waste is reduced.
100. We have to
Implement stronger security server side.
Piece together the currently fragmented front end.
102. Delivery Plan
Seed the database.
Start the server application.
Give the client all information needed to log in to the
server.
Give the client the web address.
105.
The Otago Settlers Museum has addressed the
opportunity to increase the learning and interaction of
their steam locomotive train Josephine that was built in
1872.
Value Proposition
Statement
106.
Functional
Requirements
Basic Operation of a
Steam Locomotive
Adding Coal, Water
and releasing steam
Arduino interaction
with game
Simple LED, Dials,
and buttons working
with flash
112. Value Proposition:
The ThankYou Charitable Trust project has addressed the problem of a lack of
community input into managing the spending of grants that are provided to
community-based projects.
It has been in use by the trust since March, 2015. Over this time it has
increased board meeting efficiency, via increased trustee satisfaction, and a
lower average time spent discussing individual submissions.
113. Progress:
Back-End:
● Server Setup ✓
● Functioning Relational-Database ✓
● Restful API Designed ✓
● Restful API Implemented ✗
Application:
● Network Data Transfers ✓
● Basic User Functionality ✓
o Register, Profile, Message Board, Projects
● Basic Admin Functionality ✗
o Community Creation, User approval
● Advanced User Functionality ✗
o Geolocation View, Personal Notes
● Advanced Admin Functionality ✗
o User Maintenance, Generate Reports
● Increased Security Implemented ✗
● Final Design ✗
114. Development Plan:
Implementation:
● Initial deployment of the app on
Google Play within two weeks.
● Initial testing on trustee members.
● Weekly iterative development to
implement new features and add
functionality.
● Weekly testing on previous
functionality throughout this process.
● Intended robust deployment - 15/05
● Field testing within a real funding
round.
Risks:
● Implementation of features
extending beyond expected
development phases.
● Trustee and test subject co-
operation.
● Still learning Android development -
potential for obsolete code
115. Deployment and Proving Value:
● Initial hand-over of the system to TYCT.
o Database integration.
o Potential hand-over to other charities.
● Satisfaction survey taken of trustee members at meetings.
● Timed average of discussions on individual grant submissions.
Hinweis der Redaktion
Good morning everybody we are BananaByte and our team is comprised of Alex McNeill and myself Daniel Mazur. Our client is Dr. David Rozado who is a new lecturer here at Otago Polytechnic
Currently nearly every way to interface with a computer is physical, we tend to use keyboards, mice, and touch screens to do so. This poses a giant problem for people in situations where they are unable to use their hands. This leaves people with certain disabilities unable to use computers at all, and people in professions that require the full attention their hands unable to easily access computers that could aid them with their jobs.
The three main tools that are becoming viable hands free interfaces options for a computer are eye tracking, voice recognition, and facial recognition.
In the past years Dr. Rozado has been researching eye tracking and trying to find ways to make it a viable interface for a computer. He has researched controlling a computer by using eye gestures, and using eye tracking in conjunction with hand tracking to control a computer. As part of Davids on going research into this he has tasked us with integrating eye tracking with voice recognition to create a system greater than the sum of its parts, that allows a user to look items on their computer screen and give commands verbally to allow hands free control of their computer.
The project aims to fix some of the imperfections of each of these systems on their own. For example eye tracking not being easy to give commands with, and voice commands being difficult to give context to the action you are trying to make. This system will be used by Dr. Rozado to create research material that will add to the Scientific literature on these technologies.
There are existing tools that we can use to develop this system
There are already many speech recognition tools that can be used to develop this project we are looking at Google Speech, Microsoft Speech Recognition and Dragon Naturally Speaking. At the moment we are leaning towards Google’s Speech API due to it being free and reliable.
There are also a few different tools that we can use to get the eye tracking data. A few of the main ones being Tobii EyeX, Pupil and GazePoint. We chose to use Tobii EyeX for this project due to it being affordable, non invasive to users, and having a lot of documentation on it.
This project presents a few risks that will need to be managed in order for a to successfully complete the project. These are:
Distance communication with the client:
Due to our client currently being in Australia until April, we need to ensure that we keep up a constant communication line with him, especially in these early phases of the project. This will ensure that there are no miscommunications on defining elements of the project.
Lack of knowledge in human interface design
Due to Daniel and I having very little knowledge in designing good interfaces we will need to ensure that we consult with people that can advise us in this area.
Multiple Consultants
As you can imagine the system we are developing can be used in many situations and help many different people. To help explore some of these situations we plan to bring some other clients into the project to explore there specific problems so we can develop a system that can be easily modified to provide the solutions they need.
The two main groups of people we would like to bring on as consultants are:
People with experience with dealing with a disability that inhibits the use of arms/hands:
To ensure that this system is usable for people with disabilities we need to bring on a person with either personal experience with disability or expertise in a disability.
Workers in positions that they want but are unable to use a computer
Examples of positions are surgeons and pilots. Both positions keep their hands busy but would benefit from being able to easily access a computer
When working with these two different groups we need to be careful not getting stuck in one point of view and make sure we continue to aim for this system to be a general solution to a problem.
Complex ethical considerations
Due to us needing to test this system on human subjects there are some complex ethical considerations to be made. When we get closer to the point in to project where we need to run these tests we will be seeking help in running these tests and creating the correct documentation needed to run the tests.
Are their any questions?
Questions they might ask:
Are there other solutions that are already in place for this problem?
This is St. Clair. A great place. All of you may know what I want to talk. Before that I want to show you some facts.
This is all documents they have, PDF, Excel (even two formats, .xls, .xlsx), a variety of data sources, and distributed everywhere.
All images, data and chart come from the two documents and the website.
[VAUGHN]
We have been privileged to have had an initial meeting with Ian Griffin (Director of the Otago Museum), whose own enthusiasm for astronomy and the development of a planetarium at the Museum will provide the people of Dunedin the chance to meaningfully connect with the world around them. Our project aims to be a part of this.
Why?
[CHRIS]
People want to know - Anyone who frequents twitter will know that Dunedin people are constantly asking where, when, how they can see an aurora.
Economic value - The council is going to replace the street lighting in the next few years anyway, and they have recognised the opportunity for astro-tourism.
Now is the time - The convergence of technology, sustainable thinking, and economic need means the time is right for these things to happen.
[VAUGHN]
Using equipment such as magnetometer and all-sky camera to feed data and meaningful predictions into social media making this easily accessible
Citizen science (Crowdsourcing scientific participation) eg Your Weather by Metservice or Wunderground.
[CHRIS]
Risks include:
Client Deadlines - Ian has indicated a deadline of ‘sooner rather than later’ - specifically for the magnetometer initiative.
SCOPE!!! - We all know about scope creep. Enough said.
Early Stage - We’ve only had one initial meeting with Ian, so we are still defining our relationship with the Museum and our project.
This is a new idea and isn’t currently being used. The only current process that is happening is Dave hands out paper based booklets when someone hirers a boke from him.
The measurement of success will be the amount of downloads, the amount of people that update and the amount of business that pay to advertise on the system
Remote client, Dave is located in middle march and is only in town on a real bases. He is best contacted via phone.
Mobile, Dave and Pip are IOS users, we learn android, android phones are cheaper If tourists are buying disposable phone, android holds the market share.
No/very limited mobile service along the trail. So all the information needs to be on the phone, no network connectivity.
Uptake. Ensure that we have the right mix of useful information to adds, gps searching will drain battery .
GPS. Ensure that we are triggering the gps often enough that if the user was to be in a tunnel or dense bush the application will still work.
Introduce ourselves
Say who client is and business
Business problem - The Southern District Health Board has a problem with communication with its 4.5k staff in case of emergencies(Snow Days, Virus outbreaks…) Our client Paul McNamara wants a system that easily notifies staff during emergencies to prevent confusion and panic. At the moment the SDHB uses emails to communicate during emergencies but finds this unreliable as a lot of staff don’t check their emails and certain email accounts are unable to be accessed off of hospital grounds due to security and risk of release of confidential information.
Two options: Option 1 - Stand alone smartphone application that pulls information from the SDHB and displays to screen. Would solve issue but wouldn’t set foundations for sending emergency information to different channels in the future. Option 2 - Engine that can be used to send emergency information to multiple channels(i.e. smartphone, email, text, pager). This idea is good because it means many devices will be able to receive notifications not just smartphone.
-We have limited knowledge of android platform as only taking paper this semester
-Scope creep extra features such as meeting modes and notepad style feature may detract from the main concept which is emergency
-Private numbers that should not be released to the public will be included