Meizhuo Zhou, Wendy Kung, Morya Breland

INFO481
Project Management Final
Scooter Website: http://students.washington.edu/sijiay/scooter/
Problem Statement:
Carbon dioxide is the primary greenhouse gas emitted through human activities. So why is
carbon emission something to worry about? Carbon dioxide traps heat into the atmosphere and alters local
climate temperatures. This affects forests, crop yields, and water supplies. The number of miles traveled
by passenger cars has increased by 35% from 1990-2012. Since transportation now accounts for 32% of
total US emissions and each gallon of gas produces 19.4 pounds of carbon dioxide, we wanted to create a
web application to help people become more aware of their carbon emission and what we can do to
reduce it. Our app, Scooter, will ultimately help reduce our carbon footprint by commuting more ecofriendly! We want people to understand how they are contributing to this global issue and why it is
important to be mindful of their carbon footprint. We will also provide other options near you, like
carpooling and bus transportation to make your commute more eco-friendly!
Logical Framework
Objective:
To create a website that tracks an individuals carbon dioxide emission from transportation. The
website will help the user track their daily commuting activities and give a week overview on how much
carbon their transportation method emitted and alternatives that could have reduced their carbon footprint.
Success Measures:
1. Reduced carbon footprint
2. Increased the visibility of the website.
3. Scooter functions as promised and successfully completes all calculations (Distance traveled, Carbon
emission, weight...etc.)
4. The website is user-friendly.
Verification:

Assumptions:

The user interest groups tested admit once they started using the app their carbon
footprint dropped.
Server confirms 3000 visits a week for the website.
In functionality testing all of the algorithms return correct values within error.
Over 80% of members of user interest groups confirm that site is easy to use.

1) The community cares about reducing their carbon footprint.

2) The right IT expertise are available to implement the project.
3) All users
Conclusion/Value statement:
In conclusion, our app aims to increase the awareness of environmental pollution and global
warming caused by car emission for college students. The app calculates and compares the amount of
carbon dioxide emission from different modes of transportation such as walking, biking, by bus and by
cars, so it allows an individual to know what is the most environmentally friendly way to get to their
destination and how much carbon dioxide will they produce. Our app also provides weekly overview of
how much carbon dioxide an individuals transportation emitted, so it motivates the individual more to
use a eco-friendly transportation way. In the end, we want more college students to know about the
transportation pollution and choose a eco-friendly transportation way to go to school.
Working Agreement:

Forms of acceptable communication are: Email, Google Docs, Text Messaging(GroupMe) possibly,
Facebook Group Contact
If any person is going to be absent from a group meeting, the group member should as a courtesy let the
other group members know 24 hours prior to the meeting. Also during the absence the group member
should be completing some part of the deliverable, if possible, otherwise buy all other group members
coffee or some sort of food item.
For independent labs our meeting place should be somewhere on the Ave, decided by a different group
member every time. Meetings should start before 9 a.m. on Friday, if lab is not already completed, so that
all deliverables can be turned in before lab is over.
Delegation of work should be done by the entire team. Any part of the project should be worked on by an
individual or subsection of the team and then it can be checked by the rest of the group.
Make the project fun, encourage each other, and complete the project on time
Company/Organization:
Company Name: Lucens - Start-up consulting firm advocating for climate change
Lucens Mission Statement
The mission for Team Lucens is to facilitate a greener world through building awareness with
enterprise applications. We strive to remain within budget and ensure customer satisfaction by integrating
stakeholders throughout the entire design process.
Scooter Mission Statement

The mission for our application Scooter is to target UW Seattle students and their commute to
school. We would calculate their carbon footprint and offer better, eco-friendly modes of transportation to
reduce carbon dioxide emission in our daily commutes.
Problem Statement
Carbon dioxide is the primary greenhouse gas emitted through human activities. So why is
carbon emission something to worry about? Carbon dioxide traps heat into the atmosphere and alters local
climate temperatures. This affects forests, crop yields, and water supplies. The number of miles traveled
by passenger cars has increased by 35% from 1990-2012. Since transportation now accounts for 32% of
total US emissions and each gallon of gas produces 19.4 pounds of carbon dioxide, we wanted to create a
web application to help people become more aware of their carbon emission and what we can do to
reduce it. Our app, Scooter, will ultimately help reduce our carbon footprint by commuting more ecofriendly! We want people to understand how they are contributing to this global issue and why it is
important to be mindful of their carbon footprint. We will also provide other options near you, like
carpooling and bus transportation to make your commute more eco-friendly!
Risks:
1. Security: a website with weak security opens your network to attack and makes data loss more likely.
2. A coding failure in a project that results in content entries not being recorded correctly.
3. A critical third-party API being unavailable could result in core feature of your application (login, etc) not
functioning, which could result in lost customers or bad press.
4. An overly complex application or system architecture could mean that when something goes wrong, its
incredibly difficult to diagnose.
5. The server crashing.

Schedule Targets
Phase I

Phase II

Phase III

Phase IV

Phase V

Phase VI

Gathering
Requirements:
*Interviews
*application
specs

Design
Process:
UX team
will design
the
websites
interface.

Development:
The
development
team will
implement the
design and
troubleshoot
any problems
that arises

Testing:
This is a time
for the team to
test the product
and make sure
that it operates
properly and the
specs are
followed.

Checking:
The team will
meet with the
stakeholders and
present the
product. This an
opportunity to
make sure that
the product
meets the
stakeholders
requirements.

Launching
and Support:
The final
phase is to
launch the
website and
routinely
support the
website for
updates and
glitches.

Duration:
This process
should take
about 5 weeks

Duration:
This
process
should
take 4
weeks

Duration:
This process
should take
about 2
months*

Duration:
This will phase
should take
about 2 weeks*

Duration:
This will take
about a week

Duration:
Launch: 3
weeks.
Support:
recurring

*could take longer or less.

Budget Targets
Total project budget: $450,000

Web Developers: $90,000

Marketing: $150,000
EPA Research and Backing: $56,800
Copyright/ Patent Fee: $400.00
Operating Cost: $7,000 / Month (Specifically Building cost)
Dedicated Server Cost: $400.00 / Month
Laptops: $9,000
Professional Clothing: $5,000
Corporate partners: $50,000
Resources Required

Servers: Our team will need a database to track carpooling services. This will allow us to achieve a point-

based system to encourage more carpooling.

Mobile Work Phones: Our team will need mobile platforms to test the applications functionality on all

devices. These would include all types of phones (iOS, Android)

Apple Laptops: Our team will need workstations to code in both iOS and Android application. XCode

works best on Apple Laptops, which includes the capability to use the Android SDK.
Samsung ATIV Book 9 Plus: Our team wants to ensure that the application works seamlessly on all
Operating Systems.

Development Software: Our team will need certain software to develop the application itself.
Google Maps Access: We need to utilize Googles location services to calculate distances for each
commute. In order to have a successful carpooling service, we also need to be able to locate carpooling

options nearby.
Carbon Footprint Data: We need to research and determine how to calculate carbon footprint for each
commute.
Project People

Web Developers: Web developers is responsible to develop the front end and back end of the website.
They will work closely with UX designer to implement her design into website by using HTML, CSS,
Javascript etc. (They can decide what languages to use depending on what functions our website needs).
They are also responsible to design algorithm and build efficient web pages. They need to debug and fix
if encounter any problems. They need to create a secure place to store customer data and maintain the
running of the website. Web developers also need to make sure the website is working on multiple web

browsers as well as mobile. Since we are a start-up, we will start with two web developers.
UX Designer: UX designer is responsible to design the website flow and user interface by brainstorming,
researching, sketching, prototyping and creating mockups for our website. UX designer need to make sure
the website is clean and easy for user to navigate. They need to communicate efficiently with other team
members like web developers to ensure their design is accepted by everyone and be delivered. We will

have one designer to design for the website.

Project manager: Project manager is responsible to plan, direct, supervise and control the execution of the
business, technical functions of the project. Project manager needs to communicate amongst group
members and keep up to date with everyones work and schedule. Project manager should act as our startups representative with stakeholders and vendors during project execution. Project manager also needs to
handle all the financial report(handle financial transition and manage the budget) and marketing(decide
on how to promote and communicate with stakeholders) since we dont have a financial or marketing

manager for now. We will have one project manager to manage the project.
Stakeholders: Our stakeholders will be US environmental protection agency and other environmental
supporting programs like cap-and-trade and Environmental Sustainability program. Those programs are
dedicated to support start-ups that help improve the environment. We will try hard to discover and attract
more institutions and programs to fund our project.
Misc. notes from the project manager (if any)
The project charter will be updated when/if any changes occur.

Theme: Increase functionalities of the web application - Scooter

1.

Improve texting feature

Priority

User story/Narrative

Tasks

As a user I want to be able to use

any mobile device to get

personalized carbon footprint
information so that I don't have
to use the web application to
track this information.

Make sure the texting feature

works for all mobile devices
with texting capabilities - Test
the texting feature on multiple
devices

As a user I want to be able to

recieve personalized carbon
footprint information promptly
so that I can get this information
before traveling or heading out
the door.

Create the texting feature

capability
Test that the responses are being
sent in a timely manner

As a user I would like to get

personalized carbon footprint
information by entering the

minimal amount of information

so that I don't have to spend
much time to get the information
I want.

Create clear prompts and

instructions
Make use of labels and
placeholders
Make the format of input as
simple as possible

Resources needed:

2.

Texting feature - Twilio

A variety of mobile devices for testing
Form validations so that they know if they are inputing the correct information with the appropriate
format
Supporting account feature (Login)
Priority

User story/Narrative

Tasks

1.

As a Tech Saavy Evironmentally

Conscious user I want an

account so that I can track my
daily carbon footprint and so
that my friends can see my
progress in reducing my carbon
footprint. Also I would like my
account to give me suggestions
as to how to lower my carbon
footprint for my specific

Make equation or borrow

equation for carbon footprint
and Use Google Maps Api to
track user location for an
account. Also implement social
features for each account

Location.
2.

As a user I want to be able to log

into my account and see a

summary of my carbon footprint
weekly or monthly so I know
how much carbon I produced in
a month or week broken down
by mode of transport

Create user account feature and

add summary reports to each
user account

As a non Habitual User I want to

be able use scooter one time

without having to make an
account so that I do not need to
submit all of my information to
the site

Maintain single use feature for

Users who prefer privacy but
also still track carbon footprint

Resources needed:

3.

Providing transportation suggestions

Priority

User story/Narrative

Tasks

As a user I would like the app to

detect my location without
typing in myself and give me
suggestion to which
transportation way to use

Backend to read users current

location
Collect data and calculate for
which transporation are
avaliable at which place

As a user I would like the app to

remember my favorite way of
transporting

Create file to store data for each

registered user
Giving suggestion base on their
favorite way to transport

As a user I would like to see

suggestion with a few steps as
possible so I get to my
destination quickly

Build front end to create

suggestion that is easy to get and
read
Build backend that is efficient
and responds quickly

As a user I would like a login

page and user profile

Ui design to make sure the front

end is clean and has good user
experience
Secure backend to remember
each users information
Efficient code to reduce
response time

Main
Features

Login/Acco
unt

User testing so user can get

suggestion without issues

Sprint 1 Sprint 2
Sprint 3
Sprint 4
Sprint 5
(Duratio (Duratio
(Duration: 4 (Duration: (Duration:
n: 2
n: 3
Weeks)
2 Weeks) 7 Weeks)
Week) Weeks)
Form
Login
Social Media Password
Validatio
Screen
Integration Recovery
n

Route
Tracking

User Suggestion
Box

Google
Map
Integrati
on
Route
Database
Design

Route
Suggestions

Sprint 7
(Duration: 2
Weeks)

Database/
Cache of
Reward System
previous
for avid users
user
locations

SSL
Basic
Encrypti User
on
Database
Map

Sprint 6
(Duration: 2
Weeks)

Route
Visualizati
on
Route
Database
Implementati
on

Advanced
Sorting
and
Filtering

Create
equation for
carbon
footprint

Route
Visual Display
Suggestion
of Suggestions
Database

Database
backup and
restoration

Route
Recommendatio
Suggestion
ns List
Algorithm

Texting

Gettint
to know
texting
function

Risk mapping

Input
Format
Prompt
Creation
Instruction
with
s
Placeholde
rs

Feature
Integration Twilio

Testing on
Multiple
Devices for
Responsivene
ss

Assumptions

Risks

Users have the necessary technology to run the

application

Users are conscious of the environment

Low amount of competition

Application is not compatible with users devices.

Users are too busy with everyday life to bother
themselves with caring about the environment
Large amount of competition marginalizes user
base

Team has necessary skills/knowledge

Team has time/resources it needs
Team is focused on this project
No affiliation to users

Team could lose time to learning how to use the

tools
Team lacks the experience to deliver the desired
results.
Skews user satisfaction ratings

The project team is capable of planning (without

hiring consultants)
The project team is capable of working well

together
The migration is separated in phases

The project team would lose money if they had to

hire a consultant
The project team would suffer from
disagreements, which could lead to the loss of
team members
The project team can lose time and business value
if there are too many tasks to be completed in a
certain phase

The sponsor understands our product and the

benefits of it.

The sponsor is willing to provide enough

technology support and budget to our product
Nondisclosure agreement covers 99% of content

Project doesnt have enough budget

Project doesnt have technology support. (We are
using sponsors plug-ins)
Our own algorithm and statistics got disclosed to
public
Change in agreement affects due dates and costs
Agreement does not cover as much of the
intellectual property as we thought and
competition gets inside details on us

Risk Register
Risk
Application is not
compatible with users
devices
Large amount of
competition
marginalizes user base

Probability

Impact

Medium

High

MediumHigh

Extremely

High

Countermeasures

Owner/Date

test the application on

several devices to determine
compatibility.

Dev Team/
Jan 01

Doing proper
research/scouting
competition
Maybe focusing on a
smaller group of users

Marketing
Team/
Jan 01

Team could lose time to

learning how to use the
tools

High

High

Team lacks the

experience to deliver the
desired results.

Medium

High

Providing a training phase

before the project for the
development team.

Project
Manager/
Dec 15

Select team members with

the required experience to
finish this project.

Project
Manager/
Dec 15

Users are too busy with

everyday life to bother
themselves with caring
about the environment

MediumHigh

High

use marketing tactics i.e

associating environment
with cool/enthralling
aspects or associating it
with everyday life

Marketing
Team/
Dec 15

Skews user satisfaction

ratings

Low-Medium Low

Ask that people in our lives

to rate it honestly or using
test groups to get accurate
results on ratings

Research
Team/
Jan 01

The project team would

lose money if they had
to hire a consultant

Low-Medium Medium

The project team would

suffer from
disagreements, which
could lead to the loss of
team members

Medium

High

Make proper planning

arrangements early on
Consult outside parties, if
necessary

Project
Manager/
Dec 15

Select team members that

not only have the necessary
skills, but also the
personality that fits with the
company
Make sure they work well
with the team before hiring

HR/ December
20

The project team can

lose time and business
value if there are too
many tasks to be
completed in a certain
phase

MediumHigh

High

Phases are made with

respect to implementation
time and the difficulty of
the tasks that need to be
achieved.

Project
Manager/ Jan
15

Project doesnt have

enough budget

Medium

High

Negotiate with sponsor

before starting the project
and make sure to sign
contracts
Make sure every expense is
nnecessary

Project
Manager/ Dec
15

Communicate with

Software

Project doesnt have

Low

Medium

technology support.

Our own algorithm and

Medium
statistics got disclosed to
public

High

technology sponsor and sign engineers/ Dec

contracts
15
Always look out for open
source API and Plug-ins
Sign contracts with inside
members as well as
sponsors on non-disclosure
agreement
Secure working computers,
code and files

Software
Engineers/
Dec 25

Change in agreement
affects due dates and
costs

Low

Medium

Make non- changeable

agreement

Project
Manager/
Dec 15

Agreement does not

cover as much of the
intellectual property as
we thought and
competition gets inside
details on us

Medium

High

Make sure the agreement

cover all intellectual
property law
If necessary, hire
lawyer/consultant on
agreement

Project
Manager/
Feb 20

Project Monitoring and Reporting Plan

We want to use a more informal approach because our team isnt very large and will be working
close together in the same office. The main document for monitoring and reporting would be a Microsoft
Excel document. This will act as the formal document for setting team deadlines. All employees will have
an electronic copy of this document and it will be their responsibility to reference the document in order
to meet these deadlines. Since we are collectively working on one project, we assume it would be most
beneficial to use a visual dashboard to monitor the teams progress. The dashboard will include our time
schedule and project management plan. On a daily basis, the team will be able to reference the visual
dashboard as an informal method to monitor progress. Our plan also includes weekly meetings and
standups at the end of stages to monitor progress and make sure we are meeting our deadlines. The
weekly meetings will be the formal method of communicating verbally with team members about the
current progress as well as expressing any concerns and issues that people may need help with.
The metrics by which we will measure the projects success at these meetings are bugs,
functionality implementations, team morale, and team performance/ satisfaction. These will all be kept in
the reference frame of time, budget, and scope of our project. We will be asking our team members in the
formal weekly meeting for status updates on functionality, bugs fixed, and basically how the team feels

about how the project is going. Also due to the fact that these meetings are formal they will include
stakeholders i.e the CEO and key investors we will also receive input on what should be done next, on the
development front, and if any of our triple constraints are changing. During the meetings team members
will write down progress with development and morale so that it does not affect the responses of other
team members. In the major end of stage meetings we will discuss the new working functionality in the
product, the plan for the next part of the project, strategy going forward, and as always team morale.
These meeting will include all stakeholders and team members.
These weekly formal meetings will keep the team on-track but will also allow them to express
problems with the system and keep them from being micro-managed. The lack of digitized progress
tracking and the implementation of a physical will foster a more personal working environment where all
team members feel equal in their ability to share issues ideas and tasks. A personal environment will keep
team morale high and thus team performance will remain high. We care about our team.

Team Retrospective

As a team we should stop:

Being Late
Discontinue missing meetings
Being unproductive during meetings

As a team we should start:

Being more punctual, focused, and responsible
Keep our project requirements (mission statement) in mind
Encouraging each other more
Making the budget more realistic
Being more serious but not serious

As a team we should continue:

Documenting work in the Google doc
Having weekly meeting for project plan
Collaborating on building the website
Securing all files and code on Github
Consulting with professional consultant on website or project plan
Working interactively and collect feedback from customer and stakeholders

Action items/Owners:
Respecting Time in all team meetings/ entire team
Being more serious but still being encouraging/entire team
Build up a secure place to store data/ entire team
Communicate with customers and stakeholders/ Project Manager