Derive Systems

Derive Systems

Derive Systems

Derive

Project Title

 

 

 

Team Project Part One

Deliverable 1

Learning Objectives

Due: June 18, 2018

 

 

Team #x:

Printed name:                Signed Name:

 

 

 

Outside editor: Writing Lab ISU Name of person

 

 

Table of Contents

1.0 Introduction/Background…………………………………………………………………………………………. 1

1.1 SOW (Statement of Work)……………………………………………………………………………………. 1

1.2 WBS (Work Breakdown Structure)……………………………………………………………………….. 1

1.3 OBS (Organized Breakdown Structure)…………………………………………………………………. 1

1.4 WBS/OBS………………………………………………………………………………………………………….. 1

2.0 Project Documents………………………………………………………………………………………………….. 1

2.1. WBS with Coding………………………………………………………………………………………………. 1

2.2 OBS with Coding………………………………………………………………………………………………… 2

2.3 Project Dictionary……………………………………………………………………………………………….. 2

2.4 Priority Matrix……………………………………………………………………………………………………. 2

2.5 Ms Project WBS with Coding……………………………………………………………………………….. 2

 

List of Figures

Figure 1: WBS with Coding……………………………………………………………………………………………… 5

Figure 2:OBS with Coding……………………………………………………………………………………………….. 6

 

List of Tables

Table 1: Project Dictionary………………………………………………………………………………………………. 7

Table 2: Priority Matrix…………………………………………………………………………………………………… 8

Table 3: MsProject WBS with Coding……………………………………………………………………………….. 9

 

1.0 Introduction/Background

Team 1 will start this project by using course notes and textbook examples. By using major characteristics of the project like, derive system is developed by in four different faces which consists of the statement of work(SOW), work break down structure(WBS), the organization breakdown structure (OBS) and an intersection of both the WBS and the OBS. Below is a description of the four parts. In class the team worked on some companies like Ford, which gave the team an example to break down a project and start it the right way. By using all of this it will will provides direction, coordination, and integration to the team.

 

  • SOW (Statement of Work)

It gives the details and the major deliverables for the project. If for instance the project involves a market research survey, the major deliverables can be design, data collection, data analysis, and providing recommendations by November 5th, 2019, for a cost of $350000.Deliverables in the early design phase could be a technical manual and software coding. The other phase could be testing for the prototype while the final stage could be final tests and the approved software.

1.2 WBS (Work Breakdown Structure)

A WBS is a representation of the project where the project is broken down to the lowest manageable deliverable and subsequent work packages. It is a map for the project. The work is broken down until one can do an estimate that is accurate enough for his purposes. The WBS should conform to how you are going to schedule your work. For instance, if assignments are made in terms of days, the tasks should be limited as best as possible to one or more to complete. It helps to assure project managers that all the products and work elements are identified, to integrate the project with current organization, and to establish a basis for control. Basically, the WBS is an outline of the project with different levels of detail according to the book.

  • OBS (Organized Breakdown Structure)

It is the outcome of the WBS. It depicts the how the firm has organized to discharge work responsibility. Its purpose is to provide a framework to summarize organization unit work performance, identify organization units responsible for work packages, and tie the organizational unit to cost control accounts. It defines the organization sub deliverables in a hierarchical pattern in successively smaller and smaller units. Regularly, the traditional organizational structure can be used. It is necessary to break down the team structure for assigning responsibility for budgets, time, and technical performance. The OBS assigns the lowest organizational unit the responsibility for work packages within a cost account.

 

1.4 WBS/OBS

The intersection of work packages and the organizational unit creates a project control point (cost account) that integrates work and responsibility. The intersection of the WBS and OBS represents the set of work packages necessary to complete the sub deliverable located immediately above and the organizational unit on the left responsible for accomplishing the packages at the intersection.

2.0 Project Documents 

This are very integral part of the project, they include they WBS with coding, OBS with coding, project dictionary, priority matrix and Ms Project with coding. In WBS with coding you break down the work until you can do an estimate that is accurate enough for your purposes. The OBS with coding draws the organization as a hierarchy and the organization department and teams are defined. The project dictionary contains a list of terms together with matching definitions, The Ms. project WBS with coding entails identifying all objectives of the project together with the deliverable s that are required to meet the objectives. The priority matrix helps the project to identify which criterion is constrained, which should be enhanced, and accepted.

 

2.1. WBS with Coding

Break down the work until you can do an estimate that is accurate enough for your purposes. If you are doing a ballpark estimate to see if the project is worthy of serious consideration, you probably do not need to break it down beyond major deliverables. On the other hand, if you are pricing a project to submit a competitive bid, then you are likely to go down to the work package level. The WBS should conform to how you are going to schedule work. Conversely, if hours are the smallest unit for scheduling, then work can be broken down to one hour increments. Final activities should have clearly defined start/end events. Take it down to the next level in which deliverables/ outcomes are more clearly defined. Instead of ending with market analysis include items such as identify market share, list user requirements, or write a problem statement. If accountability and control are important, then break the work down so that one individual is clearly responsible for the work.

Figure 1 on page 5 is an organized pyramid structure

2.2 OBS with Coding

To create an organization work breakdown structure one starts with drawing the entire organization as a hierarchy. Secondly, all the departments are defined together with the project team. Thirdly, you specify the functional and approval groups for every user.

 

Figure 2 on page 6 shows a stem graph of the organized breakdown structure

2.3 Project Dictionary

The project dictionary contains a list of terms created by Adrien with their matching definitions. To create a project dictionary, you have to come up with a list of terms from and come up with definitions for the same.

Table 1 on page 7 is a dictionary of all the words

2.4 Priority Matrix

A priority matrix for helps the project to identify which criterion is constrained, which should be enhanced, and which can be accepted the project must meet the completion date, specifications and scope of the project, or budget. Given the scope of the project, which criterion should be optimized. in the case of time and cost, this usually means taking advantage of opportunities to either reduce costs or shorten the schedule. Conversely, with regard to performance, enhancing means adding value to the project.

 

Table 2 on page 8 is a matrix that ranks the importance and priority

 

 

2.5 Ms Project WBS with Coding

When creating a Ms project WBS with coding one has to identify the final objective. Secondly, the final deliverables that need to be created to achieve the objectives identified in step one are evaluated Thirdly, the final deliverables are decomposed into activities and continue the exercise till a level is reached where you can control and monitor the individual tasks. Fourthly, the entire WBS is re-evaluated after a thorough brainstorming session with the project team and key stake holders.

 

Table 3 on page 9 is a chart from the MsProject explaining the work breakdown structure

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 1: WBS with Coding

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 2: OBS with coding

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Table 1: Project Dictionary

Terms Definitions
Release Public announcement of the product at SEMA and first product ships to customer.
Prototype Complete First articles or prototype devices in house and tested.
Supporting Software All software needed to support the product. Production software, updating software and custom tuning software. These will all need to be updated to support the new device.
Beta A process of getting prototype devices out to customer to test. This increases our ability to test new products and gets early feedback to allow us to make any changes needed before release.
OBDII On Board Diagnostics. In relation to this project this will mostly refer to the diagnostics port found underneath the dash on a vehicle.
Design The planning stages of the project. This will include design documents that the device can be built from.
Real Time Clock Having a clock on the device to keep track of time. For this product this will not be possible as there is no battery.
Protocol Used in relation to the communication types that different OEMs use. This is a standard for the messages that are sent to the vehicles computers.
OEM Original Equipment Manufacturer. For this project we are focused on Ford, FCA, GM, Toyota and Nissan.
Enthusiast A person that has an above average interest in something. In this case automotive enthusiasts are those that love vehicles and likely consider cars and trucks to be their hobby.

 

 

Table 2: Priority Matrix