Project Management. Introduction  Project management process goes alongside the system development process Process management process made up of three.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Software Quality Assurance Plan
1 SW Project Management (Planning & Tracking) Dr. Atef Z Ghalwash Faculty of Computers & Information Helwan University.
 Chapter 6: Activity Planning – Part 1 NET481: Project Management Afnan Albahli.
Chapter 3 Managing the Information Systems Project
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
© 2008 by Prentice Hall 3-1 ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
CS3500 Software Engineering Project Management (1) In 1986 one well-known software engineer (Tom DeMarco) made the simple but important observation: “You.
Systems Analysis and Design 9th Edition
Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.
Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George.
Chapter 3 Managing the Information Systems Project
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 Scope Management
Planning. SDLC Planning Analysis Design Implementation.
Project Management and Scheduling
Introduction to Computer Technology
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Chapter : Software Process
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
© 2005 by Prentice Hall 3-1 Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition.
 Probably the most time-consuming project management activity.  Continuous activity - Plans must be regularly revised.  Various different types of.
PROJECT PLANNING. PLANNING Planning is essential and software development is no exception. Achieving success in software development requires planning.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
N By: Md Rezaul Huda Reza n
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Lecture4 : Project planning Lecturer: Kawther Abas 447CS – Management of Programming Projects.
Software Project Management
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.
Project Management Formal Methods. How do you monitor a project?
Software Project Management By Deepika Chaudhary.
Work Systems and the Methods, Measurement, and Management of Work by Mikell P. Groover, ISBN ©2007 Pearson Education, Inc., Upper Saddle.
Software Engineering 2 Software Testing Claire Lohr pp 413 Presented By: Feras Batarseh.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Project Management All projects need to be “managed” –Cost (people-effort, tools, education, etc.) –schedule –deliverables and “associated” characteristics.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Chapter 3 Managing the Information Systems Project
Information System Project Management.  Some problems that org faced with IS dev efforts include schedule delays, cost overrun, less functionality than.
Chap 4. Project Management - Organising, planning and scheduling
Chapter 7 – PERT, CPM and Critical Chain Operations Management by R. Dan Reid & Nada R. Sanders 4th Edition © Wiley 2010.
SOFTWARE PROCESS IMPROVEMENT
Project Management Why do projects fail? Technical Reasons
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Slide 1 CS 310 Ch5: Project management What do you think is involved? Proposal writing Project costing Project planning and scheduling Project monitoring.
SOFTWARE PROJECT MANAGEMENT
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Project Management Planning and Scheduling. “Failing to plan is planning to fail” by J. Hinze, Construction Planning and Scheduling Planning: “what” is.
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
© 2008 Prentice Hall6-1 Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and.
Chapter 3 Managing the Information Systems Project
Management should be based on effective and thorough planning
Chapter 6: Database Project Management
CS4311 Spring 2011 Process Improvement Dr
Software Planning Guidelines
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Activity Planning.
SE Tasks for a Concept Development Project
Software life cycle models
I love the sound they make as they fly by.
Software Engineering Lecture 16.
Project management Learning Unit 5.
Software Engineering I
Information system analysis and design
Presentation transcript:

Project Management

Introduction  Project management process goes alongside the system development process Process management process made up of three components:  Creating a project plan  Monitoring whether project is proceeding according to plan and putting in place the procedures for quality assurance.  Quality assurance is managed by in place the quality assurance steps for review of project deliverables.

Measuring the process  LEVEL1: Initial - where the process is ad hoc.  LEVEL2: Repeatable – where there is a basic development process together with a project management process to track costs, schedule and functionality  LEVEL3: Defined – where the project management process is documented and integrated with the development process, with quality review in place  LEVEL4: Managed – where detailed measures of the development process are made and correlated with the product quality.  LEVEL5: Optimized – where measure are used as feedback to improve the process.

Planning  Planning must determine how each task fits into the process.  Plan defined the sequence in which tasks are carried out.  Include stating how long a task will take and defined its starting and completion time.  Estimates of the effort needed to complete each of the required tasks. These estimates are then used to allocate resources to a task and in turn determine how long it will take.

Estimating  Evaluating the amount and complexity of work to be done in each task. This information used to determined the resources needed to complete the work.  Estimates will depend on the type of work carried out in the task. Experience related of the type of task can be where:  Existing software is used  Previous experience exists  Similar experience exists  Totally new development

Identifying and evaluating risk  Idea of risk management has become important  Most likely factors that cause project to fail or estimate to be incorrect and then take precaution either to avoid them or deal with them.  Minimum risk is to use evolutionary or prototype cycle where we are deal with system and have no historical precedence to suggest needed recourse  Proper risk management require additional planning to evaluate the difficulties of achieving project goals.

Cont..  Risk of incorrect requirements leading to frequent change – provide for change management, use evolutionary or prototyping, better customer involvement.  Risk posed by new technology – hire or train technology experts in technology

Organizing Resource  Important part project management process is to organize the resource need to carry out the project.  Project organizing includes a variety of resource, choosing the right people for the project and organizing them into team, other resource to be organized such as computers and terminals, building space or productivity tools.

Defining the Project schedule  Once tasks are determined and their time requirements knows, then its necessary to determine their sequence.  The project plan will define the timing will define the timing of tasks, including start end time, the resource, included the people needed for each task.

Tools used in project scheduling  The considerable information is necessary to keep of project estimates and to monitor progress.  Necessary to maintain a database on project status and resource.  Database assists management with quantitative controls.  Planning and usage data is input to the database and reports about current resource status.  Activity start and end dates can form part of the inputs. The start and end dated can be monitored and deviation from the planned schedules output as exception reports.

Network chart  A network chart as well as showing the schedule times for each task, shows the dependence of one task on other task.  There is one line for each task on the Pert chart. The line for each task is a continuation from lines of a previous task.  A task cannot start until all its incoming tasks have been completed  The output from Pert network:  Determine a critical path – These are the activities that must commence on time;  Determine the earliest and latest start time for each activity.