Guide To FinishLine

Change Requests

1. Navigate to the Projects tab, which is located on the left side of your screen

Open

1. Click on your project

   1. If your project is not already in the Dashboard, then enter the WBS number manually into the CR form, found in the Change Requests page

2. Click on “Actions” in the top right corner if you are requesting a change for the project as a whole

   1. if you want to request a change for a work package, click on the specific work package and continue following the guide

Open

1. Select “Request Change” in the drop down menu

   1. You’ll then be navigated to the CR form, with the project/WP WBS number already filled in

2. Select the type of Change Request it is

   1. Issue = something went wrong in the process of completing said Project/WP

   2. Definition Change = you need to change how the project/WP is defined (i.e. the initial parameters of the Project/WP has changed)

3. Fill out the What section

   1. Describe the Change Request and briefly explain what it’s purpose is

4. Fill out the Why section

   1. Select the reason in the drop-down menu that best explains WHY you need to create a change request

   2. If there are multiple reasons as to why the change is being requested, create multiple Why bullets

   3. Expand on the label you assigned; if it’s a design issue that is the motivator behind the change request, explain why the design is causing issues

      1. e.g. The design of the Brakes in NER17D causes air bubbles to form in the brake lines, which leads to an exceedingly long (~4 hours) brake bleeding process

5. Scope Impact

   1. What effect will this Change Request have on the scope of the project/work package? Will it change what the project/work package sets out to do?

6. Timeline Impact

   1. Will this change request delay the project/work package? By how many weeks?

7. Budget Impact

   1. Will this change request increase/decrease the budget? By how much?

8. Submit your change request and reach out to your head/chief to get it approved! (automated Slack messages coming soon!)

*TIP* Make sure it’s SUPER clear what prompted the CR and why the “what” needs to be changed.

Implementing Change Requests

Now that your CR has been (hopefully) approved, you can implement it!

1. Choose your own Adventure!

   1. Edit a Project/Work Package

   2. Create a new Project

   3. Create a new Work Package

Edit a Project/WP

1. Navigate to the right Project/WP

2. Press “Edit” in the top right corner

3. Fill out the CR ID# you want to implement from

4. Edit the Project/WP as needed

5. Press save!

Projects

1. Once your change request has been approved, you can click on it and press “implement.”

2. Select create new project

1. Enter the Project name; make sure to include Car ID number in the title

   1. e.g. write “Brakes 17D” instead of just Brakes

2. Enter the car number the project is for, 1 for NER17D, 2 for NER22A

3. Enter the change request # you implemented the new project from

4. Fill out the Project Summary Question

   1. Outline what the project is and what it will set out to do. No need to explain the specific goals and deliverables, but make sure it is clear what is involved in the project

   2. If you have created the PM Overview document already, the “Statement of Work” section will look very similar to the Project Summary you are entering here

   3. For an example, the Vehicle Dynamometer project (WBS# 0.1.0) has a good summary to model from

5. Press create, which will take you to the newly created Project page, then press Actions in the top right, then press edit

1. Fill in who the Project Lead and Project Manager are

2. Link the slide deck, BOM list, etc. from the Google Drive (create those docs if you haven’t already)

3. Goals

   1. If you’ve already created the PM Overview document, great! You can take those goals and put those in bullet by bullet

   2. If not, go make one, what are you doing here rn???

4. Features

   1. If you’ve already created the PM Overview document, great! You can take those features and put those in bullet by bullet

   2. If not, why? Go do that.

5. Other constraints

   1. If there are any prerequisites or corequisites that have been identified, write them in this section

      1. e.g. if new knuckles are purchased, then new calipers must be purchased

      2. Also other projects that your project is dependent on (ask a PM coordinator if you’re confused about this)

6. Add in any rules that your project leads and heads should keep in mind while executing the project

Work Packages

1. Get your change request approved, press implement, and create a new work package

1. Enter the Work Package name

2. Enter the projects WBS#

   1. Make sure you enter X.XX.0, since the last number will be automatically created by the system

3. Enter the Change Request # you implemented the WP from

4. Enter the date and how long the WP will take to complete

5. Dependencies

   1. Write the WBS #’s of any projects you’ve identified as being important to the completion of your project

6. Expected Activities

   1. What are you expecting to get done during the course of this WP? Be specific and detailed.

7. Deliverables

   1. What will the finished product look like?

      1. Examples of deliverables are:

         1. Slide decks

         2. Physical Parts

   2. Something tangible that marks that the work has been completed

8. Press create to finish the completion of your work package!

9. Edit the WP like you did in the project and assign the lead/PM

1. Also edit the progress throughout the life of the WP

   1. Mark 25% if you’re between 0-50% of work completed

   2. Mark 50% if you are half-way through the WP

   3. Mark 75% if you are between 50-100% of work completed

   4. Mark 100% whe the WP is completed

2. Remember to save!