 Chapter 1: Introduction NET481: Project Management Afnan Albahli.

Slides:



Advertisements
Similar presentations
CSE 470 : Software Engineering The Software Process.
Advertisements

CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Chapter 2 – Software Processes
Project What is a project A temporary endeavor undertaken to create a unique product, service or result.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Applied Software Project Management INTRODUCTION Applied Software Project Management 1 5/20/2015.
Project Management: A Managerial Approach
Project Management November 2, Introduction Eric Lemmons Customer Project/Program Manager III Gary Obernuefemann Business Consulting IV.
Project Management October 2011 Inf Sys 3810 Information Systems Analysis Fall 2011 Understand Project Management principles.
Project Management February 28, Introduction Eric Lemmons Gary Obernuefemann.
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.
Software Processes: Traditional CSCI102 - Systems ITCS905 - Systems MCS Systems.
1 Software project management (intro) An introduction.
Project Management: A Managerial Approach
Fundamentals of Information Systems, Second Edition
Project management INTRODUCTION. Information Technology Project Management, Fourth Edition 2 IT projects have a terrible track record. A 1995 Standish.
Introduction to Project Management
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Software Project Management
© The McGraw-Hill Companies, An Introduction Chapter 1 Software Project Management 4 th Edition Robert Hughes and Mike Cotterell.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
Management & Development of Complex Projects Course Code MS Project Management Project Life Cycle & PM Process Groups Lecture # 4.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Md. Masukujjaman, lecturer, NUB
Lecture 7: Requirements Engineering
Introduction Project Management. Projects A unique process, consisting of a set of coordinated and controlled activities with start and finish dates,
Concepts of Software Development Chapter 1. Separation of Concerns Break the system down into less complicated parts, and concentrate on each one in turn.
1 INEN 261: Week 1 Chapter 1: Projects in Contemporary Organizations Presented by: Jasim Alnahas.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
University of Sunderland COM369 Unit 1 COM369 IS Project Management.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Project management Topic 1 Project management principles.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
SWE 513: Software Engineering
Software Engineering for Capstone Courses Richard Anderson CSE 481b Winter 2007.
Project Management Basics. 2 Please introduce yourself…  Name  Business Unit / Function / Process  Current Project / Process  Team Size  Ice Breaker.
Project Management Training
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Project Management
Testing throughout Lifecycle Ljudmilla Karu. Verification and validation (V&V) Verification is defined as the process of evaluating a system or component.
 Overview of Project management. ◦ Management. ◦ Project Management. ◦ Software Project Management. ◦ Project(Dimensions, Characteristics, Complexity,
Introduction to Software Project Management Lecture1.
University of Palestine Faculty of Applied Engineering & Urban Planning Civil Engineering Department Engineering Project Management Chapter 1 Introduction.
Introduction to Project Management Project management.
Software Project management
Project Management Processes
Software Project Management
Software Project Management
Project Management Framework
Software Development Life Cycle (SDLC)
Characteristics of an Effective Team
Introduction: Why Project Management?
By Kean Tak, MSc, Lecturer at RUPP
Introduction: Why Project Management?
FOUNDATIONAL CONCEPTS
Project Management Framework
INTRODUCTION TO SOFTWARE PROJEC'T MANAGEMENT
INTRODUCTION TO SOFTWARE PROJEC'T MANAGEMENT
Project Management Processes
CS310 Software Engineering Lecturer Dr.Doaa Sami
Introduction to Project Management
Presentation transcript:

 Chapter 1: Introduction NET481: Project Management Afnan Albahli

Topics to be covered  Introduction  The definition and characteristics of projects  Why project management  Software project management Vs. other projects  The project life cycle  Project stakeholders  Project objectives  Project and Business Success and Failure  Project management

What is a Project?  Project:  PMI defined project as: “ A temporary endeavor undertaken to create a unique product or service ”  A problem with a known solution scheduled for completion—unique and non-routine activities  A planned activity

Program and Project  Program :  Program : refer to an exceptionally large, long-range objectives that is broken down into projects  Project :  Project : are divided further into tasks  Tasks:  Tasks: are split into work packages  Work packages:  Work packages: are split into work units ProgramProject1Task1Task2 Work package1 Work package2 Work unit1 Work Unit2 Project2

Projects characteristics  Non-routine tasks  Planning is required  Specific objectives are to be met  Predetermined time  Work is carried out for someone  Carried out by people who don't normally work together  Has several phases  Large or complex

Exercise  Determine which of the following is considered as a project:  Checking your  Flight from Riyadh to U.S.A  Introducing a new production line  Writing an operating system

Answer  Checking your - NO  Flight from Riyadh to U.S.A - NO  Introducing a new production line - YES  Writing an operating system - YES

Why project management?  A lot of money is at market with ICT projects e.g. In UK in more money was spent on contracts for ICT than contracts for roads ( £ 2.3 billion as opposed to £ 1.4 billion )  Mismanagement of ICT projects means less money will be left to spend on important things such as hospitals

Why project management? (continued)  Projects are not always successful.  A report published in 2003, the Standish Group in the United States analyzed 13,522 projects and found:  Only a THIRD of projects were successful  82% of projects were LATE  43% exceeded their budget  The reason of these shortcomings is often the management of these projects

Software project management Vs. other projects  Invisibility : Progress in software is not immediately visible.  Complexity : per dollar, pound or euro spent, software products contain more complexity than other engineered artifacts.  Conformity : software developers have to conform to the requirements of human clients. Humans can be inconsistent.

Software project management Vs. other projects (Continued)  Flexibility : the software is easy to change which is considered a strength. Usually, a software that will interface with a physical or organization system, is expected to change to accommodate the system not the opposite.

The project life cycle  Three successive process that bring a new system into being Feasibility study Plan Project execution

The project life cycle (continued)  Feasibility study : Is it worth? Will benefits exceed the cost?  Plan : How do we do it?  An outline plan for the whole project  A detailed plan for earlier stages  Planning for later stages near their start  Project execution : Do it.  Design  Implementation

The project life cycle (continued) Requirements Analysis Architecture Design Detailed Design Code and TestIntegration Qualification Testing Installation Acceptance Support

Project stakeholders  Stakeholders: are people who have stake or interest in the project.  They could be:  Internal to the project team  External to the project team but within the organization  External to both the project team and the organization

Project Objectives  Objectives should define what the project team must achieve for project success  Objectives should identify the shared intentions for the project based on the stakeholders requirements  Objectives focus on the desired outcomes rather than the tasks to take it

Project Objectives (continued)  SMART is used to describe a well defined objectives  S: Specific  M: Measurable  A: Achievable  R: Relevant  T: Time constrained

Exercise  Comment on the following objectives  To design a system that is user-friendly  To produce full documentation for the new system

Answer  To design a system that is user-friendly  Comments:  User-friendly is not specific  User-friendly is not measured  To produce full documentation for the new system  Comments:  Full documentation is not specific  A list of the types of documents to be produced is more meaningful

Project and Business Success and Failure  Project Success  Delivered on time  Within budget  Within the agreed on functionality  Within a certain level of quality  Business Success Benefits (value) exceeds the cost (development and operational)

Project and Business Success and Failure (continued)  Project Success but a Business Failure  That you complete a project and produced a product on time, on budget, with the required functionality and the required degree of quality then no body buys it because for example another competitive product is cheaper  Project Failure but a Business Success  The project may accede the budget but later the product attract a lot of customers and make good business

Project Management  Project Management:  Is a carefully planned and organized effort to accomplish a successful project  The science and art of solving the problem within predetermined time and resource parameters