Organizational Operations Document

1. Mota Project Management Operations Document
2007 Plan
Project Teams & Role Definition
Overview
The following mota internal, external roles (and the individuals presently assigned to them) are listed in
here.
Project Roles
Employee Role Definition
Gregory Weiss Lead Mota Development Project Manager, MIMS Programming Lead, Mota
Associate Programmer, Documentation Lead, QA/Test Planning, Solution
Release Planning, MOAB Member
Mark Liu Lead Information Architect, Lead Web/Platform Designer, Content Strategist,
QA/Testing, MotaExchange.Net Product Manager, MOAB Member
John Shiple Mota Lead Solutions Architect, MIT Technical Lead, QA/Test Planning,
Deployment Management, MOAB Member
Jason Stagliano Business Process(s) Owner, Mota Operations Manager, Project Management
Advisor, Business Development, Marketing, QA/Testing, Deployment
Management, MOAB Member
Reza Bundy Chairman, Financial Manager, Business Development Lead, Marketing, MOAB
Member
Stuart Angert (External) Business Development
Kurt Brown (External) Technical Development/MIT and Pricing Engine
Robinson Collins (External) Branding and Marketing Consultant
Ken Murer (External) APC Operations Manager
Mario Stagliano (External) Database Architecture and Management Advisor
(TBD) (External) Front End Technologist
(TBD) (External) Outsource Development Resources/Special Projects
(TBD) (External) IT Architecture & Infrastructure Planning and Management
Date Last Modified: 9/7/2014 1 of 8

2. Mota Project Management Operations Document
2007 Plan
Internal Project Groups
Team Members Purpose
MOAB
(Mota Approval Board)
Jason Stagliano
John Shiple
Gregory Weiss
Mark Liu
Reza Bundy
Internal Group with the specific goal of providing
final sign-off/approval for all Business
Process/Development Priority/Timeline Decisions. It
is understood they have been presented with an
issue to review and decide upon before hand.
Meeting will consist of a simple overview of the issue
to decide at hand, a quorum of votes, and further
discussion for action if issue is rejected.
Mota Technical
Development Team
John Shiple
Gregory Weiss
Mark Liu
Kurt Brown
Mota Business
Development Team
Reza Bundy
Jason Stagliano
Stuart Angert
Robinson Collins
Mota Operations
Management Team
Jason Stagliano
Ken Murer/APC
Team
Mota Integration Task
Force
John Shiple,
Gregory Weiss
APC Team
Date Last Modified: 9/7/2014 2 of 8

3. Mota Project Management Operations Document
2007 Plan
Project Tracking Documentation
Overview
Mota will utilize and maintain the following project tracking tools/documents to manage the status and
meet the implementation goals and delivery dates of all its on-going development activities. These
documents will be managed and updated by Gregory Weiss and will be reviewed in the scheduled weekly
meetings and on an on-going basis. Archiving/Wiki of these documents will be handled also by Greg on
an as needed basis.
Tracking Documents
Master Project Plan – This MS Project Plan will be maintained by Gregory Weiss and will be a
consolidated summary review of ALL ongoing development (and possibly other) Mota activities. The
purpose of this plan will be to provide a “real-time” snapshot of all projects, delivery dates, resource
allocation, and development costs for development/operation decision review during weekly meetings
Individual Development Project Plans – These MS Project Plans will provide more detailed project
plans. These plans will include step by step development tasks and resources required for completion.
As of this document date, the following plans will be maintained:
 MIMS Development Project Plan
 FSBO Micro-Site Development Plan
 MIT Development Plan
 Internal/External Project Plans (Special Projects??)
Global Project Status – This running list will include a summary indicator of all ongoing development
projects and their status (using Green/Yellow/Red Light) status to indicate health of project, progress in
relation to delivery dates, and indicators that the project is continuing or being held up by an open issue.
Daily Issue Lists/Action Items – This running list will include all issues (broken down by project, and
associated with responsible personnel), that require immediate resolution or that are impeding the
progress of any project(s) currently under development. Additionally, System Implementation or Existing
System affecting issues (specific operation risks, not ongoing go/no go project decision risks) will be
indicated here. Each issue will have a date issue needs to be resolved and a notice if any action has
been taken or scheduled.
Financial Budgeting and Resource Cost Tracking - Financial Tracking and Financial Resource
Budgets and Expenditures will be added, incorporated, or postulated into on-going project planning
activities. This will be a loosely aggregated and monitored list that will be incorporated in a greater
manner from 2007 Q2 forward as our production business activities are ramping up.
Date Last Modified: 9/7/2014 3 of 8

4. Mota Project Management Operations Document
2007 Plan
Mota Daily/Weekly Meetings/Planning Sessions
Overview
Mota will conduct the following 2007 Daily/Weekly/As Needed Meetings and planning sessions during the
course of the 2007 operational year. Regular meetings, as defined, will be held each week, regardless of
needed attendees. Gregory Weiss will prepare agendas and notes for all meetings he attends and a
representative will take on that role for any other meetings he does not attend.
All meetings will have an invite sent out with required/requested participants, an agenda, a list of
meeting roles, meeting duration, and a list of items to be resolved and work products to be produced or
information to be determined for the production of these work products.
Meeting List
Meeting Attendee(s) Definition/Purpose
Weekly
Operational
Review Meeting
Mota Staff Weekly meeting to discuss on-going operational activities,
present future plans, milestones achieved, action issues for
resolution
Weekly
Development
Status Meeting
John Shiple
Gregory Weiss
Mark Liu
Kurt Brown (*)
Weekly meeting to discuss on-going development activities,
resolve or highlight development issues, identify milestones
achieved and review and amend development plans,
schedules and goals
Daily PM 5er Jason Stagliano
Gregory Weiss
Daily 5-15 minute Project Planning Review Meeting to discuss
progress, highlight issues, set/reset priorities, schedule
planning or sign-off meetings
Daily Tech 5er John Shiple
Gregory Weiss
Mark Liu
Daily 5-15 minute Tech Development Review Meeting to
discuss progress, review outstanding dev issues, determine
actionable items, review completed items for MOAB sign-off
scheduling.
Ad Hoc PM/Tech
JAD Sessions
As required Risk, Problem Solving, Process Mapping, Project Management
Resolution, or other important immediately resolved issues to
be discussed
MOAB Sign-Off
Sessions
MOAB Team Meeting to accept/reject sign-off on completed Mota Project
items and allow them to move into next phase or to schedule
review for revision, correction
Date Last Modified: 9/7/2014 4 of 8

5. Mota Project Management Operations Document
2007 Plan
Required Documentation, Operation Plans, Forms
Overview
The following plans need to be authored on a basic (and modified for specific per project use) for all
2007 projects
Deployment Plan
QA/Test Plan
QoS Plan/Product Support and Escalation Plan
Development Outsourcing Contracts and Documentation
External Development Resource Requisition Planning
Technical Functional Specification Documents
Technical Business Process Workflow Documents/Diagrams
Technical State Diagrams
Technical USE-Case Diagrams
Budgetary Requirements Documents
Date Last Modified: 9/7/2014 5 of 8

6. Mota Project Management Operations Document
2007 Plan
2007 Quarterly Summary Priority List
Q1 Priority Summary List
Project Task List Timeframe
MIMS
1. MIMS v2.0 Baseline Functionality (Feb 2nd)
Workflow
a. EBAY API Rollout
b. Stage 3 Development
c. V1.0 Preview/QA Functionality
2. Workflow Matrix Management Panel
3. FSBO v1.0 Rollout
4. MIMS Account Management Module v1.0
5. FSBO Notification System v1.0
6. MIMS Notification System v1.0 (TBD)
 NOTE: MIMS Contingencies – MIT/John. Work will require phased MIT
development plan to free John for some Q1 MIMS/FSBO Development
Work
Jan 1st – Feb
15th
MIMS
Workflow
1. Workflow Configuration Module
a. Identify and spec all potential workflows and stored defaults by
client type
b. Implement business logic module to set configured flows and
Source ID options in MIMS
2. Workflow Automation Service (Spooler)
3. Ebay Auto-List/Re-List Service
4. MIMS Workflow Stage 4 Base Implementation
5. MIMS Preview/QA Functionality v2.0
6. MIMS Account Management Module v2.0
a. Define Admin/User Roles
b. Define/Spec Web Panel Management
c. Define/Spec System Integration and Access Controls
d. Define Spec Other User Role Functions (Lost Login, change
password, etc.)
7. MIMS Notification System v2.0
8. MIMS CRM v1.0 Definition/Spec
a. Prelim Data Capture
b. Bidder communications module to aggregate email and call activity
by VIN
c. Lead generation tracking and referral functionality
9. Stages 3 and 4: Spec/Develop Wireframes
End Q1
(March 30th)
MIMS
Design
1. Matrix Panel
2. v2.0 MIMS Baseline Production Release Plan
a. www.motaexchange.net
b. General v1.0 Look/Feel for Production site
3. Preview Screens (v1.0, vX.X, Final Version)
Q1
Date Last Modified: 9/7/2014 6 of 8

7. Mota Project Management Operations Document
2007 Plan
4. FSBO Web Module/Panel Page Design
5. Email, other notifications (copy and design)
a. V1.0, vX.X, Final design plans
6. Account Management and Configuration Panel
a. Wireframes/Screenshots
b. Versioned to meet development schedule
7. Workflow Management / Configuration Panel
a. Wireframes/Screenshots
FSBO
Micro-
Site
1. Develop specs, wireframing and design
2. Develop functional micro-site pages
3. Messaging, design and customer experience (Robinson)
4. Ecommerce functionality (integrate payment gateway)
5. IVR implementation
a. Analyze vendors and feasibility
b. Personal audio clip from seller acquired via calling IVR
system
c. IVR menu programming
d. Integration with MIMS and eBay listing
e. Alteration of the flash gallery to incorporate new intro/lead-in
trailer video followed by streamed voice clip of seller.
6. FSBO customer personal status dashboard
a. Design, spec and implement
7. Click2Call call bridging functionality with APC
a. Evaluate vendors and feasibility
8. Click2Chat functionality with a Sales Rep (IM only – no VoIP)
a. Evaluate Vendors and Feasibility
MIT
Developm
ent
1. New Client Analysis Tools
a. Objective: MIT portfolio analysis for new clients and existing
clients
b. Deliverable: Standard report template(s)
c. Deliverable: Automation to populate standard Mota executive
report template(s)
2. MIT Coefficient Engine
a. Objective: Complete version one of the engine
b. Deliverable: Set of generic coefficients
c. Deliverable: Set of class-based coefficients
d. Deliverable: Set of eBay-based merchandising coefficients
e. Deliverable: Validation plan
3. Trim Wizard
a. Objective: Stabilize our current trim decoding process
b. Task: Help root out the problems in the current system
c. Deliverable: Develop a plan for an Options Wizard based on VIS’
data
d. Task: Help us move to a different trim decoder (or help us create
our own)
Other 1. Implement and deploy tabbed inspection report
Date Last Modified: 9/7/2014 7 of 8

8. Mota Project Management Operations Document
2007 Plan
a. Sign-off on "Inspection" tab and turnover to John for
Implementation (Mark)
2. Mota.net redesign specs and prelim design work
3. Finalize ISoldIt flows and specs
4. Switch away from Edmunds (toward end of Q1)
a. NADA integration
Biz Dev &
Marketin
g
1. Roll out preliminary FSBO customer acquisition: APC mailers
2. Planning around FSBO grassroots initiative
3. Continue to develop enterprise partnerships
4. Explore affinity partner relationships to drive traffic to FSBO micro-site
Q2 Priority Summary List
Project Task List Timeframe
MIMS Workflow 1. Enterprise Self Service MIMS UI development
a. Finish specs and wireframes - implement
2. Stage 3 evolution - implement
3. Stage 4: spec and develop wireframes
a. Aggregate all sales data into single database
b. Automated digital sales paperwork generation and
outbound emailing to buyers
Jan 1st – Feb
28th
Other 1. SEO for hosted Mota.net inventory
2. Mota.net redesign deployed
3. Mota.net inventory site for all live inventory
4. Integrate new inspection partner: AIS?
5. Integrate automated title/lien check and vehicle registration
vendor: CVR?
Biz Dev &
Marketing
1. FSBO customer acquisition begins in earnest
2. Preliminary web banner ad campaign initiated to drive traffic
to FSBO micro-site
3. Integrate new bank partners
4. ISoldIt micro-site: deploy revision of the FSBO flow, tuned
for this audience
Date Last Modified: 9/7/2014 8 of 8