Chapter 6: Database Project Management

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Chapter 3 Managing the Information Systems Project
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
© 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.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
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.
Chapter 2.
MSc project specification Unit PJ45P Dr Jim Briggs
Lecture 13 Revision IMS Systems Analysis and Design.
What is a project? Project Management Institute definition
Chapter 3 Managing the Information Systems Project
Fundamentals of Information Systems, Second Edition
Systems Engineering Management
@ Industrial Engineering by Bopaya Bidanda David I. Cleland.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
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.
Computer System Analysis
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.
CIS 321—IS Analysis & Design
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Lecture 3 Managing the Development Project SFDV Principles of Information Systems.
Objectives 4 Understand the basic concepts of project planning and control 4 Explain PERT and Timeline (Gantt) charts.
Managing the Information System Project Dr. Dania Bilal IS 592 Spring 2005.
© 2014 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected by Copyright and written permission should be obtained.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Project & Risk Management
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Managing programs that promote personal effectiveness.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
(M) Chapter 12 MANGT 662 (A): Procurement, Logistics and Supply Chain Design Purchasing and Supply Chain Analysis (1/2)
The Planning Phase Recognize the problem MIS steering committee 7. ManagerSystems analyst Define the problem Set system objectives Identify system constraints.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Chapter 7 Project Management and Event Implementation
Systems Analysis & Design 7 th Edition Chapter 2.
HNDIT23082 Lecture 10:Software Project Management
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
Chapter 3 Managing the Information Systems Project
Chapter 16 – Project Management
Project Management Systems
Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 4th Edition
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
2.2 | Use Planning Tools.
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
CIS 210 Systems Analysis and Development
Importance of Project Schedules
Software Risk Management
Information Systems Development (ISD) Systems Development Life Cycle
Chapter 3 Managing the Information Systems Project
Chapter 2 Managing the Information Systems Project
System Analysis and Design:
Definition of Project “An organized endeavor aimed at accomplishing a specific non-routine or low-volume task.” Definition of Project Management “The.
Chapter 3 Managing the Information Systems Project
Presentation transcript:

Chapter 6: Database Project Management Information Technology Department Bryar Hassan (MSc Eng.) bryar.hassan@kissr.edu.krd

Contents Project Management Overview Project Development Life Cycle (SDLC) Project Management Toolset Project Management Documentation Project Scheduling and Control Project Time Estimation Project Risk Management Database System Concepts

Project Management Overview Projects are singular, but non-routine, events with precise objectives which must be achieved within a set timeframe. The following need to be considered when planning a project Purpose and aim of the project Resources available both human and material Costing, human and time constraints The tasks, procedures or activities required to complete the project Database System Concepts

Project Development Life Cycle (SDLC) The development of information products and systems will usually follow a process that involves a number of distinct phases. Each of the phases has a series of events or steps that are completed in order to arrive at the final product. There are five phases of the SDLC: The planning phase The Analysis phase The design phase The implementation phase The use/evaluation phase Database System Concepts

The Planning Phase The planning phase is the initial steps that take place to define the project and set the objectives that will be used to evaluate the overall success of the final solution. The planning phase will normally follow a sequence of steps including: Recognising the problem Defining the problem Setting project objectives Identifying constraints Conducting feasibility studies Creating project proposals Establishing control mechanisms. A GANTT chart may be used to assist in the planning of a new system. Database System Concepts

The Analysis Phase The analysis phase of the SDLC is where existing system(s) are studied with the aims of designing a new or improved system. In this phase, a number of important decisions are made - including who will work on the system, and the setting of specific performance goals for the system to achieve. The analysis phase has the following steps: Announcing the project Creating the project team Defining information needs Defining system performance criteria Creating a design proposal Database System Concepts

The Design Phase The design phase, as the name suggests, is where the new system will be designed. In this phase, it is important that a number of different alternatives are investigated to ensure that the most efficient and effective solution is adopted. In this phase, the steps that are followed include: Preparing a detailed system design Identifying and evaluating alternative system configurations Selecting the best configuration Preparing an implementation proposal. Database System Concepts

The Implementation Phase The implementation phase is where physical and conceptual resources that are required for the project are obtained and integrated into the existing system to produce the final working system. There are a number of steps that are followed in this phase, including: Planning and announcing the implementation Acquiring the hardware resources Acquiring the software resources Preparing the physical facilities Educating the participants and users Preparing an implementation schedule (or changeover) Changing over to the new system. Database System Concepts

The Use/Evaluation Phase Once the system has been implemented, the final phase in the project will be the use and evaluation phase. In this phase, the system should be in full use to meet the objectives that were initially identified in the planning phase. The use/evaluation phase has a number of steps: Using the system Auditing the system (including a post implementation review) Maintaining the system Re-engineering proposals. Database System Concepts

Project Management Toolset This resource covers the tools used by a Project Manager beginning with 'GANTT' charts. GANTT Chart PERT Diagrams (network diagrams) Database System Concepts

What is Gantt Chart? A Gantt chart, commonly used in project management, is one of the most popular and useful ways of showing activities (tasks or events) displayed against time Gantt Chart allows you to see at a glance: What the various activities are When each activity begins and ends How long each activity is scheduled to last Where activities overlap with other activities, and by how much The start and end date of the whole project a Gantt chart shows you what has to be done (the activities) and when (the schedule). Database System Concepts

Gantt Chart Example Database System Concepts

PERT Diagrams (network diagrams) They differ from GANTT charts in that they are better at identifying the relationship between tasks rather than the progress of tasks over time. Database System Concepts

Project Management Documentation Documentation is essential for the success of any information system. Documentation provides anyone who interacts with a particular system an overview of the system capabilities and its software. Types of Documentation Program Documentation Program documentation System and technical documentation User documentation Paper based documentation Electronic documentation Documentation media Documentation for different users Database System Concepts

Project Scheduling and Control Gantt Chart - Timeline Chart Development of Activities Milestones Deadlines With resources People Equipment Money Database System Concepts

Project Time Estimation Most optimistic time (OT) Nothing goes wrong Most pessimistic time (PT) Everything that could go wrong does • Most likely time (LT) Estimate = ((OT + 4*LT + PT)/6) Example: calculate the estimation time of a project if you know the most optimistic time is 6 weeks, the most pessimistic time is 12 weeks, and the most likely time is 9 weeks. Estimation time = ((6 + 4*9 + 12)/6) = 9 weeks Database System Concepts

Project Risk Management Reactive do nothing until something goes wrong move into fire fighting mode move into crisis management mode Proactive identify and analyse risks avoid risks Database System Concepts

Types of Risks Product size Management or marketplace constraints Users Level of project definition Development tools (environment) Newness of the technology (early v late adoption) Team size and experience Database System Concepts

Risk Assessment Identify risk and its type (eg User) Estimate the probability it will occur Estimate its severity Catastrophic Critical Marginal Negligible Develop a risk mitigation (avoidance), monitoring and management plan Database System Concepts