Project Management Technique By: Penny Leahy Jackie Holohan.

Slides:



Advertisements
Similar presentations
Modern Systems Analyst and as a Project Manager
Advertisements

Software Quality Assurance Plan
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Systems Analysis and Design 8 th Edition Chapter 3 Managing Systems Projects.
Chapter 2 The Analyst as a Project Manager
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.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Degree and Graduation Seminar Scope Management
Chapter 15 Application of Computer Simulation and Modeling.
Systems Analysis and Design 8th Edition
Chapter 5: Project Scope Management
JAMES YUNG DSES-6620 Simulation Modeling and Analysis Project Description: 1. ABSTRACT This report discusses and examines the results from a ProModel software.
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
Systems Development Life Cycle
Chapter 5: Project Scope Management
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Introduction to Systems Analysis and Design
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Monté Carlo Simulation MGS 3100 – Chapter 9. Simulation Defined A computer-based model used to run experiments on a real system.  Typically done on a.
Load Test Planning Especially with HP LoadRunner >>>>>>>>>>>>>>>>>>>>>>
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Managing the development and purchase of information systems (Part 1)
MEASUREMENT PLAN SOFTWARE MEASUREMENT & ANALYSIS Team Assignment 15
Projects CHAPTER 10. Learning Objectives 1. Explain what project management is and why it is important. 2. Identify the different ways projects can be.
Chapter 14 Information System Development
NTUEE DSP Design Lab – Fall 2008 Lecture 8 p. 1 Wednesday - Nov 05, 2008 Lecture 8 DSP Design Lab Fall 2008 NTUEENTUEE Today: Project Planning/Management.
Software Life Cycle Requirements and problem analysis. –What exactly is this system supposed to do? Design –How will the system solve the problem? Coding.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
1 Software Reliability Assurance for Real-time Systems Joel Henry, Ph.D. University of Montana NASA Software Assurance Symposium September 4, 2002.
Introduction to Systems Analysis and Design
Welcome to Session 3 – Project Management Process Overview
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
Formulating a Simulation Project Proposal Chapter3.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Modeling Tough Scheduling Problems with Software Alex S. Brown Mitsui Sumitomo Marine Management (USA), Inc.
Chapter 10 Verification and Validation of Simulation Models
Building Simulation Model In this lecture, we are interested in whether a simulation model is accurate representation of the real system. We are interested.
CS532 TERM PAPER MEASUREMENT IN SOFTWARE ENGINEERING NAVEEN KUMAR SOMA.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Project Monitoring Section A 1.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Project Management Cross lifecycle Activity
Lecture 2 System Development Lifecycles. Building a house Definition phase Analysis phase Design phase Programming phase System Test phase Acceptance.
Software Testing Mehwish Shafiq. Testing Testing is carried out to validate and verify the piece developed in order to give user a confidence to use reliable.
McGraw-Hill/Irwin Copyright © 2011 The McGraw-Hill Companies, All Rights Reserved Chapter 10 Projects.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
Mahindra Satyam Confidential Quality Management System Software Defect Prevention.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Information Technology Project Management, Seventh Edition.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Systems Development Life Cycle
TechStambha PMP Certification Training
SYSTEMS ANALYSIS Chapter-2.
Chapter 3 Managing the Information Systems Project
Chapter 10 Verification and Validation of Simulation Models
Managing the development of information systems (Part 1)
Burn Down charts for Project Management
Engineering Processes
Project Theory and Application
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
DESIGN OF EXPERIMENTS by R. C. Baker
Chapter 2 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Presentation transcript:

Project Management Technique By: Penny Leahy Jackie Holohan

S cope the Model –Defining the Problem, Objectives B aseline Current Process –Data Collection I nvestigate Model Concept –Inputs, Assumptions, Entity Flow C reate the model –Locations, Entities, Path Networks, Processing C ontrol & Verify Model Results –Sample Problem to Solve –Verification & Validation

Scope the Model Today projects developed in Information Technology are often Ê Over BudgetË Not Delivered on Time Project Leaders and Managers are not properly evaluating time requirements and costs for projects before making commitments to customers or upper management. Develop a tool to be used by project leaders, team members and upper management to estimate the amount of time & cost to complete a project in Information Technology.

Current Process ScopeBaselineInvestigateCreateControl Checkpoint 1Checkpoint 2Checkpoint 3Checkpoint 4Checkpoint 5 SBIC C Project Management Technique (PMT) Process Flow Project Leaders and team members complete project tasks at each phase. Checkpoint review meetings are held after each phase to ensure the project is on the right track. Checkpoint 5 represents project completion.

Current Process - Project Tasks Scope Investigate Create Control Baseline

Current Process - Data Collection Time data was collected for each of the project tasks through surveying 18 project leaders.  How long did it take to complete each project task most of the time?  What is the maximum time to complete each project task?  What is the minimum time to complete each project task? Based on your team's experience level: Sample Data MODE MAX MIN Triangular Distribution Service Times

Investigate - Model Inputs Input Factor = Numerical Value 1-9 An Input Factor is used to specify what type of project you’d like to analyze using the simulation model.

Investigate - Assumptions  There is a 15 minute break between project tasks.  There will be no "side-projects".  The work week is 40 hours per week.  The model is based on a 50 week-year, working 5 days per week.  The frequency of the projects can be adjusted as needed by the user.  The model output is in time, but can easily be converted to cost.  This service time for the checkpoint meeting is fit as a triangular distribution model {t(.5,1,1.5)}.

Investigate - Entity Flow Common Tasks: C.1 C.2 C.3 C.4 C.5 C.6 C.7 Checkpoint Reviews : 1 Scope S.3 C.1, C.2 ENTER S.4S.5 S.2 S.1 Baseline 1 C.3, C.4, C.1 2 B.1 Investigate 3 C.3, C.4 2 C.5, C.1, C.6, C.7 I.1 Create C.3 3 C.6, C.5, C.7 4 Cr.2 Cr.1 Control C.2, C.7 C.3 4 EXIT Co.2 Co.3 Co.1 Common Tasks: C.1 C.2 C.3 C.4 C.5 C.6 C.7 Checkpoint Reviews :

Investigate - Entity Flow in ProModel Locations - Project Tasks Entity - Project team member(s) Locations - Project Tasks Entity - Project team member(s)

Create the Model Locations Each project task set up with triangular service times. Entity 1 project team member or a group of team members. Path Networks Paths set up from project task to the next project task (serial processing). Arrivals Enter constant number of projects to complete per model run. Processing If…then…else statements set up to handle input factor.

A new Information Technology enhancement has been requested by one of the key customers. The project entails changing the quoting and ordering software package to include one of the new products just released. The IT project manager has several options in planning for this enhancement request. The maximum amount of time allowed to complete this project is 6 months. Control - Sample Problem

Scope down the request to be a series of 3 small projects with low experience levels on the team. New employees cost $40,000 per person year. The team only would have 2 people on the team. Deliver the request as 1 medium project using moderately experienced people on the team. The team would have 3 people on the team. Moderately experienced people cost $65,000 per person year. Combine the enhancement with the large project currently in progress with highly experienced personnel. These employees cost $90,000 per person year. This project will have 5 people on the team.

Control - Sample Problem Results  No significant difference between Scenario 1 and Scenario 2. (T-test performed; p-value =.83)  Scenario 3 costs about twice as much ($26K more) AND will take 8 months; BUT the business will gain market share and sales.  If the benefit gained exceeds $26K, Scenario 3 is recommended if the customer is willing to wait an extra 2 months.  If the customer is not willing to wait an extra 2 months for the extra benefits, either Scenario 1 or Scenario 2 are recommended. Recommendations

Control - Validate Model Verification Used to remove program bugs from the model. 2 bugs found through structured walk through exercise.  A task was not connected in path network; no output.  Output should be based on hours; it gave minutes. Validation 3 projects validated T-test completed showing 2 projects were represented well by the model. 1 project used wrong input factor; model was not represented of real world.

Based on the data gathered from a GE IT department, the output was validated. In some instances, the output may vary from actual data gathered from the population because of è Assignment of an incorrect input factor Model can be customized for other applications. Conclusion Simulation models can be used to predict the time and cost of projects as long as the data used to create the model is based on the application being studied.