Planning and Budget.

Slides:



Advertisements
Similar presentations
PROJECT MANAGEMENT Chu Eu Ho Dept. of Civil and Environmental Engineering Massachusetts Institute of Technology.
Advertisements

TK3333 Software Management Topic 7: Schedule Control.
ES=32 EF=34 LS=33 LF=35 ES=10 EF=16 LS=10 LF=16 ES=4+6=10 EF=10 LS=4
Responsibility Assignment Matrix (RAM) — Purpose  Ensure that all tasks are assigned to people  Show levels of involvement of people to work.
PERT / CPM PERTProgram Evaluation & Review Technique CPMCritical Path Method.
WEEK 15A – PROJECT MANAGEMENT (CHAPTER 3) Characteristics, tools, Pert/CPM, critical path, slack calculation, crashing SJSU Bus David Bentley1.
System Analysis (Part 1)
Precedence Network Calculations the basic information that should be calculated in the precedence network are: 1) Early activity start (ES) 2) Early activity.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
ACS 567: Software Project Management Spring 2009 Instructor: Dr. John Tanik.
Ch 4 The Process page 1CS 368 Building Software is Difficult often delivered late often over budget always with errors must be a custom solution complexity.
Introduction to software project management. What is a project? One definition ‘a specific design or plan’ ‘a specific design or plan’ Key elements non-routine.
Information Systems Development Lecture 2: the idea of the Life Cycle.
Software project management (intro) Scheduling Network.
Roberta Russell & Bernard W. Taylor, III
Project Management Ross L. Fink. Definition of Project  A project is a specific, finite task to be accomplished.
Time Management Ahmed Awad, Ph.D., PMP. Time Management It includes the processes required to ensure timely completion of the project. b Activity Definition.
OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.
Project Scheduling Professor Stephen Lawrence Graduate School of Business Administration University of Colorado Boulder, CO
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
Toolkit 4.
System design technique  System Development Life Cycle  Prototyping  Rapid Application Development.
Management Information Systems, 4 th Edition 1 Chapter 15 Systems Development.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Laudon & Laudon: Canadian Edition
DISCLAIMER I HEREBY MAKE NO CLAIM THAT THE SAME QUESTIONS WILL BE REPEATED OR ASKED IN THE INTERVIEW AND AS YOU DOWNLOAD THIS POWERPOINT SLIDES IT IS UNDERSTOOD.
Systems Development Lifecycle Testing and Documentation.
111 Notion of a Project Notes from OOSE Slides – a different textbook used in the past Read/review carefully and understand.
PROJECT SCHEDULING By Deepika chaudhary. Project Scheduling Scheduling means estimation of time and resources required to complete activities and organise.
Local Government Reform Project WA E - Government System.
ISYS 562 Microcomputer Business Applications David Chao.
Summary of Rulemaking in California for the Forensic Alcohol Laboratories Regulation Review Committee Cathy L. Ruebusch, RN, MSN Office of Regulations.
MIS 673: Database Analysis and Design u Objectives: u Know how to analyze an environment and draw its semantic data model u Understand data analysis and.
Monitoring Information System Greece Working Group Meeting Brussels, June 2000 STRUCTURAL FUNDS
Introduction and Overview of Project Planning and Management (Session 1 in the Project Planning And Management Module) Russ Pimmel Electrical and Computer.
Negotiation and Conflict Resolution (Part I) Chapter 6.
CISB113 Fundamentals of Information Systems IS Development.
Irwin/McGraw-Hill  The McGraw-Hill Companies, Inc Project Scheduling IENG 321 IENG 321.
Unit 15: SDLC I October 12, Systems Development.
(M) Chapter 12 MANGT 662 (A): Procurement, Logistics and Supply Chain Design Purchasing and Supply Chain Analysis (1/2)
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.
PROJECT MANAGEMENT ENCE-7323 TO 763-N CLASS 3 September 17, 2001 Carl E. Edlund
Survey Training Pack Session 17 – Budgeting and timelines for survey design and implementation.
Software Design and Development Development Methodoligies Computing Science.
The Information Systems Development Processes Chapter 9.
The Network Diagram. When to Do What?  Carrying out one activity after the other may result in project completion, but it will take the longest possible.
Database Systems: Design, Implementation, and Management Tenth Edition
PERT CPM assumes duration of activity is known with certainty.
Introduction to Project Management
Project Management: PERT/CPM
Computer Data Security & Privacy
Database Systems: Design, Implementation, and Management Tenth Edition
Systems Analysis and Design
Project planning Unit 3 Employability and Professional Development
Project Planning & Scheduling
Project Management and scheduling
Project scheduling Precedence diagram method & Resource scheduling
Business System Development
Project Scheduling Chapter 14.
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
PERT-CRITICAL PATH-DECISION MAKING PROCESS/TOOLS
Systems Design, Implementation, and Operation
Business Application Development
תזמון פרויקטים.
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Project management concepts
System analysis and design
Language Independent Code Analysis
Lecture 23 CS 507.
Presentation transcript:

Planning and Budget

PERT chart 1 8 3 11 3 6 9 12 5 4 3 5 8 1 5 13 3 17 18 1 2 5 8 9 17 18 5 13 3 2 4 8 4 13 4 7 9 13

PERT chart 2 TF = lf - es - t FF = ef - es - t IF = ef - ls - t es ef n n+1 ls lf TF = lf - es - t FF = ef - es - t IF = ef - ls - t

Estimation matrix Size complexity simple medium difficult small medium large

Analysis: Interview Size complexity simple medium difficult small # man-days per interview simple medium difficult small 1.3 1.8 2.7 Size medium 1.8 2.7 3.6 large 2.7 3.6 4.5

Analysis: Data Flows Size complexity simple medium difficult small # days per technical element simple medium difficult small 0.2 0.3 0.6 Size 0.3 0.6 1.0 medium 0.6 1.0 1.5 large

Analysis: Database design complexity # man-days per file simple medium difficult small 1.0 1.5 2.2 Size medium 1.5 2.2 3.2 large 2.2 3.2 4.5

Analysis: Functional program design # man-days per program complexity simple medium difficult small 1.3 1.8 2.7 Size medium 1.8 2.7 3.6 2.7 3.6 5.4 large

Implementation: coding, testing # man-days per program complexity simple medium difficult small 10 15 20 Size medium 15 20 30 large 20 30 35

Environment corrections vague or unclear system requirements additions or modifications accepted other type of users real time systems unclear or complex interfaces with other systems modifications to other people’s programs badly defined rules, procedures or standards ICT-people have no experience with similar projects system bigger than in previous projects

Environment corrections 2 system contains legal procedures or regulations end-user must provide initial database no choice in project team end-user must officially accept the system third party must officially accept the system end-user has no system development experience work environment allows easily interruptions negative expectations concerning the system negative expectations concerning project team