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.

Slides:



Advertisements
Similar presentations
Chapter 2 – Software Processes
Advertisements

Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Software Processes: Traditional CSCI102 - Systems ITCS905 - Systems MCS Systems.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
1 Software project management (intro) An introduction.
Information Systems Development Lecture 2: the idea of the Life Cycle.
إدارة المشروعات Projects Management
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
socio-organizational issues and stakeholder requirements
S/W Project Management
Software Project Management
N By: Md Rezaul Huda Reza n
© The McGraw-Hill Companies, An Introduction Chapter 1 Software Project Management 4 th Edition Robert Hughes and Mike Cotterell.
Software Project Management Introduction to Project Management.
Why use RequisitePro RequisitePro is a comprehensive tool that supports any of today's requirements management processes. The predominant requirements.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
By: Md Rezaul Huda Reza 5Ps for SE Process Project Product People Problem.
The Architecture Business Cycle. Software Architecture Definition The software architecture of a program or computing system is the structure or structures.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
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 Requirements Engineering: What, Why, Who, When, and How
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
SacProNet An Overview of Project Management Techniques.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Lecture 7: Requirements Engineering
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Lecture 1 :- Introduction Project Lifecycle Project Stakeholders Lecturer: Kawther Abas Monday: 3/4/1435 (8-11) 447CS – Management of Programming Projects.
Formulating a Simulation Project Proposal Chapter3.
University of Sunderland COM369 Unit 1 COM369 IS Project Management.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
 Chapter 1: Introduction NET481: Project Management Afnan Albahli.
Systems Development Life Cycle
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Project management Topic 1 Project management principles.
IT SOFTWARE PROJECT MANAGEMENT
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
1 - 1 Systems Analysis and Design, Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
IS444: Modern tools for applications development Dr. Azeddine Chikh.
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
LOGO Business Analysis and IT Business Analyst An Introduction.
University of Sunderland CIF 301 Unit 1 CIF 301 Lecture 1 IS Project Management.
 Overview of Project management. ◦ Management. ◦ Project Management. ◦ Software Project Management. ◦ Project(Dimensions, Characteristics, Complexity,
Introduction to Software Project Management Lecture1.
Software Project Management
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Exam 0 review CS 360 Lecture 8.
Software Project Management Week 1 Lecture 2
Chapter 18 Maintaining Information Systems
The Systems Engineering Context
TechStambha PMP Certification Training
Software Project Management
CS701 SOFTWARE ENGINEERING
Chapter 4 Systems Planning and Selection
By Kean Tak, MSc, Lecturer at RUPP
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Software Project Management
FOUNDATIONAL CONCEPTS
SOFTWARE PROJECT MANAGEMENT
(System Development Life Cycle)
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

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 non-routine specific objectives specific objectives planned planned predetermined timespan predetermined timespan constrained resources constrained resources

What is a project? More key elements work carried out for a third party work carried out for a third party work involves several specialisms or phases work involves several specialisms or phases size and complexity size and complexity

Are software projects really different from other projects? Not really, but: invisibilitycomplexityflexibility need to conform to human ideas all add to difficulties

Activities The feasibility study PlanningExecution Requirement analysis Requirement analysis Specification Specification Design Design Coding Coding Verification and validation Verification and validation Implementation/installation Implementation/installation Maintenance and support Maintenance and support

Position of planning Feasibility study - decide if project is worth doing Plan how you are going do it, then do it feasibility study planning project Is it worth doing?How do we do it? Do it!

Contents of a feasibility study report  Introduction: identifies what the document is;  Description of current situation  Problem description  Proposed development  business and financial aspects  technical aspects  organizational aspects  Estimated costs  development costs  operational costs  Envisaged benefits  Recommendations

stages typically include implement requirements gathering specificationdesign code testing

Categories Information system vs embedded system IS: Interface with organization IS: Interface with organization ES: interface with a machine ES: interface with a machine Objectives vs product Product  specification by client Product  specification by client Objectives  services Objectives  services

Project as a system System, subsystem, & environment System: a set of interrelated parts System: a set of interrelated parts Subsystems: part of larger system Subsystems: part of larger system Environment: outside the system Environment: outside the system Open System vs Closed System OS: interact with the environment OS: interact with the environment CS: _not_ CS: _not_Sub-optimization detrimental effect on optimization on a subsystem detrimental effect on optimization on a subsystem Sociotechnical systems organization of technology and people organization of technology and people

What is management? Planning — deciding what is to be done Organizing — making arrangement Staffing — selecting the right people Directing — giving instructions Monitoring — checking on progress Controlling — taking action to remedy hold-ups Innovating — coming up with new solutions Representing — liaising with users

Problems Poor estimates and plans Lack of quality standards and measures Lack of guidance about making organizational decisions Lack of techniques to make progress visible Poor role definition Incorrect success criteria

Management control Management The process of setting objectives for a system and then monitoring the system The process of setting objectives for a system and then monitoring the system

Management control (2) Project control cycle Data collection Data collection Data processing Data processing Making decisions/plans Making decisions/plans Implementation ImplementationObjectives Should be clearly defined Should be clearly defined Measures of effectiveness Sub-objectives and goals

Stakeholders They may be: Internal to the project team Internal to the project team External to the project team but within the same organization External to the project team but within the same organization External to both the project team and the organization External to both the project team and the organization External stakeholders may be customers or user affected by system customers or user affected by system contractors contractors There will be different types of users with different interests Need for good communication!

Objectives Different stakeholders will have different objectives need for agreed objectives need for agreed objectives Need for an identifiable project authority to set, monitor and modify objectives to set, monitor and modify objectives can contain user, development and management representatives can contain user, development and management representativesObjectives can be informally expressed as: ‘in order for the project to be a success, the project must….’ can be informally expressed as: ‘in order for the project to be a success, the project must….’

Objectives -continued Objectives must be: concrete concrete have measures of success have measures of success Objectives can be: broken down into sub-objectives or goals broken down into sub-objectives or goals can be informally expressed as ‘in order to achieve A, we must achieve B,C,D etc’ can be informally expressed as ‘in order to achieve A, we must achieve B,C,D etc’ identifying sub-objectives involves considering the ‘how’ as well as the ‘what’ identifying sub-objectives involves considering the ‘how’ as well as the ‘what’

Requirement Specification Functional requirements what the system is to do what the system is to do systems analysis aims to provide these systems analysis aims to provide these Quality requirements other attributes of the system e.g response time; usability; reliability other attributes of the system e.g response time; usability; reliability Resource requirements cost cost time time Trade-offs between the different factors

Information and control Hierarchical information and control systems Management information flows up Management information flows up Control flows down Control flows down Levels of decision making and information Strategic Strategic Tactical Tactical Operational Operational Differences in types of information Effectiveness: doing the right thing Effectiveness: doing the right thing Efficiency: making the best possible use of resources Efficiency: making the best possible use of resourcesMeasurement Performance measures Performance measures Predictive measures Predictive measures

The control cycle real world collect data process data define objectives make decisions modelling implement data information decisions actions