Project Plan

Plan your projects and define important tasks and actions

Iniziamo. È gratuito!
o registrati con il tuo indirizzo email
Rocket clouds
Project Plan da Mind Map: Project Plan

1. Resources

1.1. Project Manager

1.2. Team Members

1.3. Budget

1.4. Assets

2. Scope

2.1. What is included

2.2. What is excluded

3. Schedule

3.1. Project Start

3.1.1. Project specifications

3.1.2. End User requirements

3.1.3. Action points sign-off

3.2. Phase 1

3.2.1. Top Priorities

3.2.2. Medium Priorities

3.2.3. Low Priorities

3.3. Phase 2

3.3.1. Top Priorities

3.3.2. Medium Priorities

3.3.3. Low Priorities

3.4. Phase 3

3.4.1. Top Priorities

3.4.2. Medium Priorities

3.4.3. Low Priorities

4. Constraints

4.1. Budget

4.1.1. Materials

4.1.2. Personnel

4.1.3. Services

4.1.4. Duration

4.2. Deadline

4.3. Requirements

5. Overview

5.1. Motivation

5.2. Goals

5.3. Deliverables

6. Project Brainstorming

6.1. Context: - front-end/back-end solution - demoable - something we would actually use - something that shows off our technologies

6.2. Areas of interest

6.2.1. AR Elements ... or something related

6.2.2. RL: AR/VR immersion for K12 = native mobile app with Vuforia

6.2.3. AO: App that shows what tech is and means of communicating data = Native app that is built with Vuforia

6.2.3.1. sensors that communicate and understanding how they work? (e.g. Bluetooth, Wi-fi, LTE, etc.)

6.2.3.2. showing how data types actually work?

6.2.3.3. features:

6.2.3.3.1. have toggles to show/hide items in view

6.2.4. CD: Build anything that communicates into a network with connectivity; something for K12 audience

6.2.5. Group interest: Learn how to build a native Vuforia app that connects with hardware for the K12 space

6.3. What we want to build with (Hardware/Technologies to explore)

6.3.1. Hardware

6.3.1.1. Hololens

6.3.1.2. AR App

6.3.1.2.1. iOS devices (App Store): iPads, iPhones,

6.3.1.2.2. Android (Google Play Store)

6.3.1.2.3. Classroom laptops: Chromebooks

6.3.1.3. RaspberryPi

6.3.1.4. MyRIO

6.3.1.5. Sensors?

6.3.1.5.1. From phone?

6.3.2. Software

6.3.2.1. ThingWorx

6.3.2.2. ThingWorx Studio

6.3.2.3. Reality Editor?!

6.3.2.4. App Stack

6.3.2.4.1. Front-end

6.3.2.4.2. Back-end

6.3.2.5. Speech Recognition

6.3.2.5.1. Amazon Alexa

6.3.2.5.2. Google

6.4. Business pain points to solve

6.5. Possible cool ideas

6.5.1. Actual life-size Mars Rover connected to ThingWorx

6.5.2. Ultimate What is IoT Demo Table using AR pros: - demoable in the C Lab - could be built into Elements as AR primer with cloud-based end-points (e.g. Wunderground) - could make use of current tech (RaspberryPi, EV3, Lego WeDo)

6.5.3. MC: AR app that let's you take a search term and place that into environment

6.5.4. MC: web portal of demos (e.g. AR, Creo, etc.) we could run from a single library

6.5.5. MC: Build it yourself Larry Rover

6.5.6. AO: AR app that locates where you are in a building

6.5.7. Built-into Elements - pre-app tutorial experience 1. in-app, 2. in-person, 3. you don't have hardware and show software twin

7. Timeline 20%< time project

7.1. Brainstorming Feb 1 Milestone: Proposal for 1 or more projects

7.1.1. Refine Feb 7-8 Elements Retreat Milestone: Share out proposal to team

7.1.1.1. Develop Six month with smaller cycles of development

7.1.1.1.1. Deliver TBD