Project Plan MS Project Example (Optional)

Slides:



Advertisements
Similar presentations
Fall CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Senior Design Lecture 3 Corporate organization Product development.
Advertisements

Chapter 11 - Project Management ME101 Dr. Nhut Tan Ho 1.
Collaborative Report Writing the Proposal. Definition Proposal: a document written to convince your audience to adopt an idea, a product, or a service.
MS Word Template Training General Template Use. 2 Our Contact Information APPLICATION SUPPORT CENTER: Consultation Location: The Hub, Room 224 (132 Temp.)
Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Senior Design Lecture 5 Prototype phase Evaluation phase Production.
EE x12 Technical Reports Writing Lecture 7
1 The Initial Report Preparation Guidelines. 2 The Initial Report u Definition of project scope u Project aims and objectives u Initial project plan.
Lecture for Senior Design Classes By Dr. Pam Estes Brewer Associate Professor, TCO Mercer University School of Engineering Brewer (Adapted from presentation.
Designing Written Reports Presentation for Senior Design Classes by Dr. George Hayhoe Professor, Technical Communication Mercer University School of Engineering.
10/10/2015 IENG 471 Facilities Planning 1 IENG Lecture END Project Report Requirements & Project Presentation Information.
Rev. A MonTueWedThuFri Weekly Pre-approval Weekly FS 0.9 Weekly Picnic Pgm rev Projects Approved Adv/IR Assigned.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
EE/CS 480 Fall September, 2007 University of Portland School of Engineering Project Goldeneye Freshmen Engineering Database for the University of.
Spring CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Senior Design Lecture 1 Fall re-cap Spring pre-view Debugging.
Fall CS-EE 480 Lillevik 480f06-l10 University of Portland School of Engineering Senior Design Lecture 10 Webs Scheduling MS Project (Optional)
Fall CS-EE 480 University of Portland School of Engineering Project Nuthatch 10/29/02 Project Nuthatch The Inverted Pendulum Monthly Program Review.
Senior Design 1 University of Portland School of Engineering.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class project.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
REPORTS Prof. Q. Overview  Audience and Purpose  Elements of Effective Reports  Parts  Progress Reports (Informational)  Periodic Activities Report.
EE/CS 480 Fall November, 2007 University of Portland School of Engineering Project Merlin WOC 60 :Wind Output Converter to 60Hz Team Tammy Okubo.
9/23/2009 NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of.
THE FORMAL REPORT THE FORMAL REPORT. Definition and Purpose Definition: reports formatted in a professional way to emphasize its importance or recommendations.
CS-EE 480 Fall September, 2006 University of Portland School of Engineering Project Title Team Student 1 Student 2 Student 3 Student 4 Advisor Dr.
CS-EE 480 Fall November 2006 University of Portland School of Engineering Project Glide Garage Door Tele-Controller Team Graham Linn Srija Pidaparthy.
CS-EE 481 Spring February, 2007 University of Portland School of Engineering Project ZigZag Team Adam Russell Will French Matt Heye Advisor Dr. Rylander.
Design Report – Fall Semester. Title Page List name of project and team number List date List team members, advisor, sponsor Team logos.
Spring CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Senior Design Lecture 2 Technical staff Prototype phase: DEP, TOP.
CS-EE 481 Spring January, 2007 University of Portland School of Engineering Project Title Team Student 1 Student 2 Student 3 Student 4 Advisor Dr.
CS-EE 481 Spring March, 2007 University of Portland School of Engineering Project ZigZag Team Adam Russell Will French Matt Heye Advisor Dr. Rylander.
Fall CS-EE 480 Lillevik 480f06-l2 University of Portland School of Engineering Senior Design Lecture 2 Expectations/Rumors Calendar/Evaluation Defined.
Fall CS-EE 480 Lillevik 480f06-l6 University of Portland School of Engineering Senior Design Lecture 6 Other development processes Technical documents.
Fall CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Senior Design Lecture 7 Functional specifications Technical meetings.
Fall CS-EE 480 Lillevik 480f06-l4 University of Portland School of Engineering Senior Design Lecture 4 Definition phase Design phase.
Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Senior Design Lecture 9 Project management Project plan Change request.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
Principal Investigator ESTCP Selection Meeting
Information Systems Project Management
Your Name or Team’s Member’s Names Current Date
Introduction to Project Management
Project Glide Garage Door Tele-Controller
Project Glide Garage Door Tele-Controller
Principal Investigator ESTCP Selection Meeting
Project Lost Intelligent Leg Prosthesis
Documenting the Review May 2005 Revision
Project Owyhee Digital Lock
Write less; please more pictures!
Business Plan Template
Project Charter <Project Name>
AIChE Contest Organization
Project Snake Automated Guitar String Tuner
STATUS REPORT.
This template will allow you to easily create an annual calendar without having to change all the dates manually. It has 28 pages because it was put together.
Project Snake Automated Guitar String Tuner
IS&T Project Reviews September 9, 2004.
SWEN 5230 Your Project Title
COMP390/3/4/5 Final Year Project Design
Project Implementation Planning
COMP390/3/4/5 Final Year Project Introduction & Specification
Project Snake Automated Guitar String Tuner
PLANNING ENGINEERING AND PROJECT MANAGEMENT
Principal Investigator ESTCP Selection Meeting
Team Dustin Digmann Philip Johnston Tobias Scherf
Project Molalla Microprocessor-based Charge Controller
Project Overview.
Principal Investigator ESTCP Selection Meeting
Project Grey Wolf Digital CMOS “Memory” Game
Project LocatePortland Team Pistol River Pocket Gopher
Project Owyhee MOSIS Digital Lock
Presentation transcript:

Project Plan MS Project Example (Optional) Senior Design Lecture 11 Project Plan MS Project Example (Optional) Lillevik 480f06-l11 University of Portland School of Engineering

Design phase Milestones/ Approvals Documents We are right here Define Prototype Evaluation Production Milestones/ Approvals Release Documents Project Plan We are right here Lillevik 480f06-l11 University of Portland School of Engineering

October 2006 University of Portland CS-EE 480 Mon Tue Wed Thu Fri 5 6 9 10 11 12 13 16 17 18 19 20 23 24 25 26 27 30 31 1 2 3 4 Weekly FS 1.0 Approv mtg FS 0.95 to IR Weekly Fall Break Starts Fall Break Ends Weekly Plan 0.9 Pgm rev Pgm rev Weekly Lillevik 480f06-l11 University of Portland School of Engineering

November 2006 University of Portland CS-EE 480 Mon Tue Wed Thu Fri 3 6 7 8 9 10 13 14 15 16 17 20 21 22 23 24 27 28 29 30 1 Weekly Plan 1.0 Approv mtg Funding Plan 0.95 to IR Weekly Weekly, Optional Thanksgiving Pgm rev DR info list Pgm rev Weekly Lillevik 480f06-l11 University of Portland School of Engineering

December 2006 University of Portland CS-EE 480 Mon Tue Wed Thu Fri 1 4 5 6 7 8 11 12 13 14 15 18 19 20 21 22 25 26 27 28 29 Weekly Design rel Approv mtg DR info to IR Peer reviews Finals Start Finals End Xmas Starts Lillevik 480f06-l11 University of Portland School of Engineering

Class response in Lecture 4 Why a project plan? Class response in Lecture 4 Team knows what's going on Budget your time Detect/correct a problem Supervisor knows what you’re doing Lillevik 480f06-l11 University of Portland School of Engineering

Instructor response in Lecture 4 Why a project plan? Instructor response in Lecture 4 Determine what has to be done, by when, and by who (schedule) State assumptions, identify dependencies Set the budget Evaluate risks, develop contingency plans Lillevik 480f06-l11 University of Portland School of Engineering

Typical development sequence? Lillevik 480f06-l11 University of Portland School of Engineering

Project plan Front: title page, revision history, TOC, LOF Body Summary Introduction Background Product overview Development process Conclusions Back: appendices Lillevik 480f06-l11 University of Portland School of Engineering

Product overview Purpose Headings Describe what your project does, do not introduce anything new Define your deliverables Headings General description: cut and paste from FS Deliverables Lillevik 480f06-l11 University of Portland School of Engineering

Deliverables Deliverable: measurable result List them in a table Give each a number (1, 2, 3, …) Provide a title, due date In-class and project-specific Describe each in the text Be very specific Lillevik 480f06-l11 University of Portland School of Engineering

Development process Purpose Chapter contains the bulk of the document Describe how you are going to complete the project Clarify the scope of the development Chapter contains the bulk of the document Lillevik 480f06-l11 University of Portland School of Engineering

Dev process headings General approach Assumptions: list and describe Describe the technical and logical sequence Use a figure Assumptions: list and describe Milestones In-class and project specific At least one project specific-per-month Lillevik 480f06-l11 University of Portland School of Engineering

Dev process headings, continued. Risks/Contingencies Use a table Provide severity: H, M, L Describe risk and it’s contingency Schedule Gantt chart format Include an overview and critical path Lillevik 480f06-l11 University of Portland School of Engineering

Dev process headings, continued. Resources Personnel: include responsibilities Budget Equipment Facilities Contingencies: one for each risk Lillevik 480f06-l11 University of Portland School of Engineering

Plan: milestone table Lillevik 480f06-l11 Number Description Date 1 Product Approval 10/04/06 2 Plan Approval 10/25/06 3 Design Release 12/06/06 4 Project specific 5 TOP’s Approval 02/14/07 7 Prototype Release 04/04/07 8 9 10 Founder’s Day 04/07/07 11 Final Report 04/25/07 12 Lillevik 480f06-l11 University of Portland School of Engineering

Program review: milestones Number Description Original 10/28/06 Previous 11/25/06 Present 01/30/07 1 Product Approval 10/04/06 2 Plan Approval 10/25/06 11/01/06 11/01/05 3 Design Release 12/06/05 12/10/06 4 Project specific 5 TOP’s Approval 02/14/07 7 Prototype Release 04/04/07 04/05/07 8 9 10 Founder’s Day 04/07/07 11 Final Report 04/25/07 12 January program review shown Lillevik 480f06-l11 University of Portland School of Engineering

Schedule Use Project to create Print to .mdi file Save as .tif file, rotate with Picture Manager Insert  picture  from file Other approaches to produce a clean figure Lillevik 480f06-l11 University of Portland School of Engineering

.mdi to .tif Project MS Office Doc Imaging Picture Mgr Lillevik 480f06-l11 University of Portland School of Engineering

Review of Plan template Updated template on web (ProjectPlan2.doc) Includes changes to risks/contingencies section Lillevik 480f06-l11 University of Portland School of Engineering

Optional Lecture Material MS Project Example Lillevik 480f06-l11 University of Portland School of Engineering

Lillevik 480f06-l11 University of Portland School of Engineering

Typical development sequence? Model solution and simulate Vary parameters until solution meets requirements Implement (code, circuits, etc.) Debug on small scale (unit testing) Integrate the units into prototype and debug System test prototype Lillevik 480f06-l11 University of Portland School of Engineering