1 A Software Project Management Method: A 3 Sergio Coronado, José Alberto Jaén, UNIVERSIDAD POLITECNICA DE MADRID.

Slides:



Advertisements
Similar presentations
Workshop on Knowledge Technologies within the 6th Framework MayA. Gómez-Pérez Certifying Knowledge and Knowledge Technologies ( based on Sig3 activities.
Advertisements

Chapter 17 Project Management McGraw-Hill/Irwin
Fawzy Al-Alami G Term Paper.  Introduction.  Effect of Teamwork in Design-Build. Construction Contract.  Factors Can Enhance Design-Build.
Validating the Evaluation of Adaptive Systems by User Profile Simulation Javier Bravo and Alvaro Ortigosa {javier.bravo, Universidad.
Project Scheduling for Load Testing Bridges for ENCE 667 Course Project Spring 2001 Justin Myers.
Chapter 26 Estimation for Software Projects
XI- ADVANTAGES SCHEDULING PROCESS
GPII-2A Planning a software project: Estimation & Measurement.
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 Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
Roberta Russell & Bernard W. Taylor, III
Project Time Management
IT Project Management, Third Edition Chapter 11 Chapter 1: Introduction to Project Management.
Project Management March 9, 2001 Dr. Richard Chung Dept. Chemical & Materials Engineering San Jose State University.
Planning a Software Project José Onofre Montesa Andrés Universidad Politécnica de Valencia Escuela Superior de Informática Aplicada
Sylnovie Merchant, Ph.D MIS 210 Fall 2004 Lecture 1: The Systems Analyst Project Management MIS 210 Information Systems I.
Project Management Chapter 13 OPS 370. Projects Project Management Five Phases 1. Initiation 2. Planning 3. Execution 4. Control 5. Closure.
Edward B. Farkas, Managing Director, Project Management Practice
CPTE 209 Software Engineering Summary and Review.
Software Project Management
 Engineers are regularly engaged in projects in their careers!  Middle management continues to shrink  Industry now organizes more around projects.
S.Cholette, based on McGraw-Hill/Irwin Managing Risk.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
IHRIM n International Association for Human Resource Information Management n Professional group - HR, HRIS, IS managers; compensation, computer, and other.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Software Project Management
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 Lecture 17: Chapter 26 Estimation for Software Projects Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman.
Project Scheduling Tools. There are four possible sequencing modes in MS Project. Suppose B follows A. FS: Finish Start – Start B after A is completed.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.
Software Project Management Lecture 11. Outline Brain Storming session  Some simple discussion on questions and their answers  Case studies related.
Agile User Stories Enriched with Usability ANA M. MORENO AND AGUSTÍN YAGÜE UNIVERSIDAD POLITECNICA DE MADRID MADRID, SPAIN
“WHY ARE PROJECTS ALWAYS LATE?” (“and what can the Project Manager DO about that?) Craig Henderson, MBA, PMP ARVEST Bank Operations.
Presented by: Meysam rahimi
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.
IT Software Project Management
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
Q N U Schedule Risk Management By Ursula Kuehn, PMP, EVP UQN and Associates.
1 3. M ODELING U NCERTAINTY IN C ONSTRUCTION Objective: To develop an understanding of the impact of uncertainty on the performance of a project, and to.
1 How Much Planning and Control is Enough Project Costs = Production + Administrative Costs Project complexity Project Size Level of Uncertainty Organizational.
Project Management Cross lifecycle Activity
PRJ566 Project Planning & Management Software Architecture.
Enterprise Risk Management– Fad or Fact?
Estimation for Software Projects 1. Software Project Planning 2 The overall goal of project planning is to establish a pragmatic strategy for controlling,
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Information System Project Management.  Some problems that org faced with IS dev efforts include schedule delays, cost overrun, less functionality than.
Project Management. Introduction  Project management process goes alongside the system development process Process management process made up of three.
Software Engineering (CSI 321) Project Planning & Estimation 1.
Introduction to IT investment decision-making Pertemuan 1-2 Matakuliah: A Strategi Investasi IT Tahun: 2009.
PERT/CPM F G A E H I J K D St T B C
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
These slides are designed for presentation purpose only © Copyright SAIsej Consultancy Services (P) Ltd Why ??? Project Management.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
BSBPMG503A Manage Project Time Manage Project Time Project Time Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit Code.
Project and Project Formulation and Management
Chapter 33 Estimation for Software Projects
Chapter 17 Project Management McGraw-Hill/Irwin
Project Management and Information Security
Software Engineering (CSI 321)
The value of a project-oriented approach to IT and how we do it in IBM
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Prepared by Lee Revere and John Large
SE Tasks for a Concept Development Project
Physics-based simulation for visual computing applications
Chapter 33 Estimation for Software Projects
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
Chapter 26 Estimation for Software Projects.
Project Time Management
Presentation transcript:

1 A Software Project Management Method: A 3 Sergio Coronado, José Alberto Jaén, UNIVERSIDAD POLITECNICA DE MADRID Escuela Técnica Superior de Ingenieros Industriales

2 Content Motivation & Problem Methodology Steps Activity Network Simulation & Sensibility Analysis Examples Conclusion

3 Motivation & Problem (1) Corporate America spends more than $275 billion each year on approximately 200,000 application software projects. Many of these will fail, but not for lack of money or technology; most will fail for lack of skilled project management. (Standish Group, CHAOS Chronicles 2001) MSL Software, a Spanish company, had been contract by IBM to develop all the software need to manage the result system for the Sydney 2000 Olympic games. 37 information systems + integration and communications elements are need.

4 Motivation & Problem (2) Complex development project with high time constrain and requirements complexity. We need a project structure with an activity network to guide the project And of course, we need other elements; people, technology, tools, etc…

5 Methodology Steps - Objective 1.Drive the construction of a complete activity network with schedule and effort estimations 2.Understand the estimation base on uncertainties (probability distributions) 3.Analyze the network to understand the sensible points or possible critical paths

6 Methodology Steps - Network The problem is decompose in small sub-products development project, as we do when we design a system For each sub-product, development and support process are used For each sub-product, CocomoII is used For each sub-product, QA and Risk are model The network is build using integration-products that are sub-products to be compose to create the end product

7 Decomposition & Composition RS CM QA Inf HR Ext PO Sub-Product 1 E:5.87S:6.10 Sub-Product 1 E:5.87S:6.10 Int Doc Risk PO T CM QA Inf HR Ext Int Doc Risk PO C CMQA Inf HR Ext Int Doc Risk PO Integration E:4.21S:10.41 Integration E:4.21S:10.41 Risk 0 Development phases RS: Requirements A: Analysis D: Design C: Construction T: Testing

8 Activity Network

9 Simulation Once all of the elements of the A 3 model are constructed, simulations are carried out using the Monte Carlo technique which permits the evaluation on n repetitions of the probability distributions derived from the estimation process, and the relations between products in terms of effort and costs.

10 Analysis Correlations and Sensibilities are compute in each activity base on precedent activities

11 MSL Olympic Development (1)

12 MSL Olympic Development (2)

13 MSL Advantage The project has a detail activity network Effort distribution is understand by development phases Possible delays are estimate and mitigation plan was build Sensible points are identify and manage

14 Conclusion Helps Software Project Design Helps Build the Project Structure Underway Project Control Project Simulation Project Visualization Mechanism