Software Project Management

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
CS487 Software Engineering Omar Aldawud
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Chapter 2 The Software Process
W5HH Principle As applied to Software Projects
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
Chapter 21 Project Management Concepts
Introduction to Software Engineering Dr. Basem Alkazemi
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Project Management Concepts
1 Project Management CIS 375 Bruce R. Maxim UM-Dearborn.
Project Management Instructor: Dr. Jerry Gao. Project Management Jerry Gao, Ph.D. Jan The Management Spectrum - People - The Players - Team Leaders.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Process: A Generic View
Before we start construction, let’s lay the groundwork.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Chapter 21 Project Management Concepts
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1M.Sc.(I.T.), VNSGU, Surat. Structured Analysis Focuses on what system or application is required to do. It does not state how the system should be implement.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
CSEB233: Fundamentals of Software Engineering
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
Chapter 3 Project Management Concepts
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
Software Project Management Lecture # 2. Outline The Management Spectrum  4 Ps in Project Management W 5 HH Principle.
1 Chapter 3 Project Management. 2 Project Management Concerns staffing? cost estimation? project scheduling? project monitoring? other resources? customer.
1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.
Project Management Concepts 1. What is Project Management? Project management is the process of the application of knowledge, skills, tools, and techniques.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Lecture 16: Chapter 24 Project Management Concepts
 Management ◦ The activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of other in order.
PROJECT MANAGEMENT CONCEPTS. The Management Spectrum The key concept behind the an effective software engineering process is the management spectrum.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Company LOGO CSEB233 Fundamentals of Software Engineering Module 9: Software Project Management Badariah Solemon 2010.
Software Project Management Lecture # 2. Outline The 4 Ps in Project Management Detailed Insight of each P.
Project Management Concepts By: Sohaib Ejaz Lecturer,UoS.
Chapter 4 프로세스 모델 Process Models
Process: A Generic View
Chapter : Project Management Concept
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Project Management Michael L. Collard Department of Computer Science Kent State University.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
Dr. Rob Hasker. Avoiding failure  Standish Report, 2014 Standish Report 31% projects cancelled before completion 53% projects ~190% of original estimate.
Programming Techniques Lecture 15 Project Management Based on: Software Engineering, A Practitioner’s Approach, 6/e, R.S. Pressman Lecture 4 An Introduction.
Interacting with consumer Software Engineering. So far… What is Software Engineering? Different software process models waterfall, incremental, spiral.
Chapter : Project Management Concept
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Project Management Why do projects fail? Technical Reasons
INTRODUCTION: Project management involves the planning, monitoring, and control of the people, process, and events that occur as – software evolves from.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
CIS 4251 / CIS 5930 SOFTWARE DEVELOPMENT Fall 1999 Sept. 1, 1999 Marge Holtsinger.
PROJECT MANAGEMENT Software Engineering CSE
1 Supplementary Slides for Software Engineering: A Practitioner's Approach, 6/e Part 4 Supplementary Slides for Software Engineering: A Practitioner's.
Software Project Management Unit 1. Evolving role of software S/w now a days resides in the mobile, mainframes The main role of the s/w is to transform.
Software Project Management
Software Engineering (CSI 321)
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Chapter 3 Project Management
SE 3800 Note 10 Project Management
Chapter 31 Project Management Concepts
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Software Project Management
Chapter 26 Estimation for Software Projects.
Presentation transcript:

Software Project Management

4P’s in Project Management Spectrum People Product Process Project

The People

People… …the most important factor in success of software project. “Companies That sensibly manage their investment in people will prosper in the long run” . Cultivation of motivated and highly skilled software people has always been important for software organizations. The “people-factor” is so important that has developed People Management Capability Maturity Model (PM-CMM).

PM-CMM In simple words - to enhance the people’s capabilities through personnel development Organizations that achieve high levels of maturity in PM-CMM have a higher likelihood of implementing effective software engineering practices

PM-CMM (Contd.) Key Practice Areas of PM-CMM Recruiting Selection Performance Management Training Compensation Career development Organization and work design Team/culture development

People Involved in Software Process The Stakeholders They can be categorized into one of the following Senior Managers they define business issues that often have significant influence on business Project (technical) managers they must plan, motivate, organize and control the practitioners who do software work Practitioners They deliver the technical skills necessary to engineer a product or application Customers They specify the requirements for the software to be engineered End Users They interact with the software after it is released for production use

The Product

The Product The product and the problem it is intended to solve must be examined at very beginning of the software project. The scope of product must be established and bounded. Bounded scope means establishing quantitative data like no. of simultaneous users, max. allowable response time. etc. Constraints and limitations

Software scope Scope is defined by Context (1st step in scope determination) Functional location of the software product into a large system, product or business context Constraints involved Information Objectives (2nd step) What data objects are required as i/p or o/p Function and Performance (3rd step) What function does the software system perform on i/p to produce o/p What level of performance is required

The Process

Common Process Framework Activities These characterize a software process and are applicable to all software projects Communication Planning Modeling Construction Deployment These are applied to software engineering work tasks (e.g., different product functions) Refer to book page 640 – fig. 21.1

The Process Models Different process models: Linear sequential, Prototyping, RAD, Spiral, Formal … Project manager must decide about which model to use depending on Customers who have requested the product People who would work on project Product characteristics Project environment Project planning begins once model is selected

Process decomposition The way a process is decomposed depends on project complexity Decomposition involves outlining of work tasks involved in each process framework activity

The Project

Signs of Projects Risk Software people don’t understand customer needs Product scope is poorly defined Changes are managed poorly The chosen technology changes Business needs change Deadlines are unrealistic

Signs of Projects Risk (Cont…) Users are resistant Sponsorship is lost Team lacks skills Managers avoid best practices

How to avoid problems? Start on the right foot Maintain Momentum Involves detailed understanding of project setting realistic objectives & expectations Selecting the right team Facilitating the team Maintain Momentum Provide incentives Reduce bureaucracy and give autonomy to team members but with supervision Track Progress Assess progress as work products are produced

How to avoid problems? (Contd..) Make smart decisions When possible, use existing software components / COTS software Choose standard approaches and keep it simple Avoid risks and allocate more time than needed for complex/risky tasks Conduct a postmortem analysis Compare planned and actual schedule Collect and analyze project metrics (standards) Get feedback from team and customers Establish record of lessons learnt for each project