Fall 2006 1 CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Senior Design Lecture 9 Project management Project plan Change request.

Slides:



Advertisements
Similar presentations
Project management Information systems for management1 Project Management.
Advertisements

Fall CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Senior Design Lecture 3 Corporate organization Product development.
Ensure Vendor/Engineer of Choice Product Quality
Module 11 Session 11.2 Visual 1 Module 11 Executing and Controlling the Work Session 11. 2: Managing Contracts.
Computer Engineering 203 R Smith Project Tracking 12/ Project Tracking Why do we want to track a project? What is the projects MOV? – Why is tracking.
Chapter 6 Systems Development.
Fundamentals of Information Systems, Second Edition
Pre-Project Planning Lessons from the Construction Industry Institute Construction Industry Institute Michael Davis, P. Eng, PMP Ontario Power Generation.
Don Cole Risk Assessment and Mitigation Project Management for ARA Engineers and Scientists.
Copyright © 2009 T.L. Martin & Associates Inc. Chapter 3 Requirements of a realistic CPM schedule.
Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Senior Design Lecture 5 Prototype phase Evaluation phase Production.
Software Project Management
Software Project Management Introduction to Project Management.
Software Project Planning CS470. What is Planning? Phases of a project can be mostly predicted Planning is the process of estimating the time and resources.
Software Quality Assurance Activities
Department of Industrial Engineering 1 Project Management Kim LaScola Needy, Ph.D., P.E., CFPIM University of Pittsburgh 1041 Benedum Hall Pittsburgh,
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Risk Management in the Built Environment Qualitative and Quantitative Risk Management By Professor Simon Burtonshaw-Gunn – licensed under the Creative.
Distributed Software Development
Rev. A MonTueWedThuFri Weekly Pre-approval Weekly FS 0.9 Weekly Picnic Pgm rev Projects Approved Adv/IR Assigned.
VCU Information Systems Institute Advanced Delivery Methodology Courtesy of Data Management That Works.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Fall CS-EE 480 Lillevik 480f06-l12 University of Portland School of Engineering Senior Design Lecture 12 Change control, Funding Design Review Milestone.
Project management Dr. Khaled Bubshait 1 Dr. Khaled A. Bubshait Project Management.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
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.
Lecture 3 Title: Information Technology Project Methodology By: Mr Hashem Alaidaros MIS 434.
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
© 2014 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected by Copyright and written permission should be obtained.
Chapter 13 Project Management. Objectives After reading the chapter and reviewing the materials presented the students will be able to: Define and give.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Project & Risk Management
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Project management Topic 7 Controls. What is a control? Decision making activities – Planning – Monitor progress – Compare achievement with plan – Detect.
Project Management Inspections and Reviews 1 February.
XLIX Engineering Design Firm © 2010 ENGR/ETGR Definition of Project 1 A project is “…a combination of human and non-human resources pulled together.
Project Management Organization Scheduling 31 January.
Software Engineering Lecture # 1.
1 Chapter 3: Project Management Chapter 22 & 23 in Software Engineering Book.
Fall CS-EE 480 Lillevik 480f06-l1 University of Portland School of Engineering Senior Design Lecture 1 Introductions Course objectives What is design?
Project Management “Project Planning & Scheduling” Lecture 07 Resource Person: M. Adeel Anjum.
Spring CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Senior Design Lecture 2 Technical staff Prototype phase: DEP, TOP.
Fall CS-EE 480 Lillevik480f06-a1 University of Portland School of Engineering CS-EE 480 Quiz 1 October 5, 2006 Instructions 1.Print your name, student.
CLAIMS MANAGEMENT. PRESENTATION OUTLINE INTRODUCTION TYPICAL CLAIMS AGAINST OWNER TYPICAL CLAIMS AGAINST CONTRACTOR CRITICAL PATH METHODS UTILIZATION.
Engineering Economics Lecture 18 Project Management 6 January 2010.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CS 350, slide set 4 M. Overstreet Old Dominion University Spring 2005.
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.
Supplier Management Can’t live with them, Can’t live without them!
Fall CS-EE 480 Lillevik 480f06-l4 University of Portland School of Engineering Senior Design Lecture 4 Definition phase Design phase.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
Copyright All Rights Reserved by
Systems Analysis and Design in a Changing World, 4th Edition
Project Management Processes
Project Controls: As-Built S-Curves
Project Management Processes
Defining project management
Project Plan MS Project Example (Optional)
Project Overview.
CEM 515 Done by: Abdulkarim Sulais
TOTAL COST CONTROL ON CONSTRUCTION PROJECTS
Presentation transcript:

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Senior Design Lecture 9 Project management Project plan Change request

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Picnic Re-cap Very good presentations Not easy to do: peers, faculty, dean, industry reps (an intimidating audience!) Public commitment Excellent dialog with team, faculty, and industry reps

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering October 2006 CS-EE 480 University of Portland Pgm rev Weekly FS 1.0 Approv mtg Weekly Fall Break Starts Weekly Plan 0.9 MonTueWedThuFri FS 0.95 to IR Fall Break Ends Weekly Quiz

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Preparing for our quiz Quiz: multiple choice, closed book Pass-Fail Review handouts

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Product Development Cycle Define Design Prototype Evaluation Production Milestones/ Approvals Product Approval Design Release Prototype Release Beta Release Product Release Documents Functional Specifications Project Plan Debug & Evaluation Plan Theory of Operations Qualification Report Not in class Manufacturing Report EOL Final Report

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Definition Phase Define Design Prototype Evaluation Production Milestones/ Approvals Product Approval Documents Functional Specifications We are right here

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Design Phase Define Design Prototype Evaluation Production Milestones/ Approvals Design Release Documents Project Plan Last document this semester

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

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Purpose of a project plan Determine what has to be done, by when, and by who (schedule) State assumptions, identify dependencies Set the budget Evaluate risks, develop contingency plans

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Project management Project progress must be monitored Start On Track Re-Plan Project Plan 1.0 Monitor Progress Done OK Issue

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Monitoring tools? Deadlines Project plan Calendar Weeklies FS Open and honest feedback Program reviews

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Plan topics Assumptions –Events that set (initialize) the environment –Usually a major impact if not correct –Single largest factor to problems Success indicators –Measure project completion –Must be quantifiable

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Assumptions for building a house? Won’t be done on time Its expensive Building to code You are allowed to build it You or someone can do it Get the materials you need Within budget

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Indicators for building a house Actual expenses within 5% of budget Schedule within 5% of plan Final walk through with zero defects Indicators must be quantifiable and measurable

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Other plan topics Schedule Milestones Resources –People –Budget –Equipment –Facilities

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Other plan topics, continued. Risk Assessment –Identify activities with high probability of error –Often less-understood activities –Monitor carefully Contingencies (back up) –Describe alternate plans for risky activities –Typically scales back features, budget, schedule –Can keep project on track

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Risks for building a house? Out of budget Not built to code No access to materials Sub screws up Miss your schedule

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Contingencies for house? Ditch some features Fire contractors, hire new one Locate alternate materials Tight contract, line up replacements Pad your schedule

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Re-plan Problem: project predicted to miss feature, budget, or schedule (may be unavoidable) Solution: formal change in plan Typical impact –Features dropped –Schedule slips –Budget increased Usually something fixed

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Re-plan process Identify problem exists Propose a change: change request form Assess the impact: requirements, schedule, budget Approve the change Document the change Communicate the change

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Change request form Date Title of Request Description (What is it you want to change?) Reason (Why is it you want to make a change?) Impact (What is affected by the proposed change and how?)

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Monitoring tools? Weeklies Project Meetings Schedule Milestones Program Reviews

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Assumptions for building a house? No land clearing (logging, stumps) No drain field No change orders No failed inspections No subcontractor or material shortages No re-work

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Risks for building a house? Foundation on sloped lot Poor drain field soil New materials and installation techniques Bad weather Vandalism Rising interest rates

Fall CS-EE 480 Lillevik 480f06-l9 University of Portland School of Engineering Contingencies for house? Engineered soil Alternate drain field site Use traditional materials and installation Accelerate or delay construction until good weather Lock up all materials and equipment, hire security service, big dog Lock in finances by paying a premium