Vrije Universiteit Amsterdam Faculty of Exact Sciences. Exam: Software Project Management Version A. Dr. Nelly Condori-Fernandez. Date: May 27, 2015

Similar documents
SENG380:Software Process and Management. Software Size and Effort Estimation Part2

C S E USC. University of Southern California Center for Software Engineering

Software Project Management. Software effort

MTAT Software Economics. Session 6: Software Cost Estimation

COCOMO II Demo and ARS Example

Chapter 3 Managing the Information Systems Project

SOFTWARE EFFORT AND SCHEDULE ESTIMATION USING THE CONSTRUCTIVE COST MODEL: COCOMO II

CHAPTER 6 AN ANALYSIS OF EXISTING SOFTWARE ESTIMATION TECHNIQUES

Prepared by: Mr.M.SYED SHAHUL HAMEED CHAPTER 3 SYSTEMS PLANNING - MANAGING SYSTEMS PROJECTS

Chapter 2: Project Management

Modern Systems Analysis and Design Seventh Edition

PMP Exam Preparation Course Project Time Management

Software Efforts and Cost Estimation with a Systematic Approach

Determining How Much Software Assurance Is Enough?

6 PROJECT TIME MANAGEMENT

THE PMP EXAM PREP COURSE

nam I BIA Un IVERS ltv OF SCIEnCE AnD TECHnOLOGY

Project Management. Learning Objectives. What are Projects? Dr. Richard Jerz. Describe or Explain:

Project Management. Dr. Richard Jerz rjerz.com

Project Management. Time and Resources DPLE 157

CSCI 510 Midterm 1, Fall 2017

Operations Management

BA /14/2010. PSU Problem Solving Process. The Last Step 5. The Last Step 8. Project Management Questions PLAN IMPLEMENT EVALUATE

Information Technology Audit & Cyber Security

12/08/2012 INFO2110. Chapter 3: Project Management. Copyright Warning. Learning Objectives. Introduction. Project Identification

User Manual. COCOMO II.2000 Post-Architecture Model Spreadsheet Implementation (Microsoft Excel 1997)

Life Cycle Plan (LCP)

Objectives of Project Management Framework. What are the Characteristics Of Project. Activities involved Project Management

MGT/437. Project Management. Session #2 University of Phoenix 02/12/2004 Brian Smithson. 02/12/2004 MGT/437 #2 -- Brian Smithson 1

PMP PMBOK Guide Sixth Edition Training Course Agenda

ECE-492 SENIOR ADVANCED DESIGN PROJECT

DAMELIN CORRESPONDENCE COLLEGE

Life Cycle Plan (LCP)

A Process for Mapping COCOMO Input Parameters to True S Input Parameters

Cambridge International AS & A Level Computer Science

Managing Complexity in the Face of Uncertainty

COCOMO II Based Project Cost Estimation and Control

CIPRIANI COLLEGE OF LABOUR & CO-OPERATIVE STUDIES BSC IN PROJECT MANAGEMENT PRM 135: PROPOSAL DEVELOPMENT & COSTING WEEK 8

Object-Oriented Software Engineering Practical Software Development using UML and Java. Chapter 11: Managing the Software Process

3. December seminar cost estimation W 2002/2003. Constructive cost model Department of Information Technology University of Zurich

Life Cycle Plan (LCP)

Seminar 6: Project Management Part 1 Semester 1, 2005

Topic # 12. CIS Project Management: an overview

For the PMP Exam using PMBOK Guide 5 th Edition. PMI, PMP, PMBOK Guide are registered trade marks of Project Management Institute, Inc.

Seminar 6: Project Management Part 1 Semester 1, 2005

Software User Manual Version 3.0. COCOMOII & COCOTS Application. User Manual. Maysinee Nakmanee. Created by Maysinee Nakmanee 2:07 PM 9/26/02 1

Technology Impact Analysis Tool. A. Winsor Brown

Management level case

Time Management PLANNING

Software Project & Risk Management Courses Offered by The Westfall Team

1.Which of the items listed below is not one of the software engineering layers?

Lecture 10 Effort and time estimation

Program Evaluation and Review Technique (PERT)

Project Management PSGLE 122. Time and Resources

Project Management. Agenda - What will you learn today? Theory Lecture Plan. A Software Life-cycle Model Which part will we talk about today?

Project Scheduling with GanttProject. EGR 386w

Project Time Management

You document these in a spreadsheet, estimate them individually and compute the total effort required.

Project vs Operation. Project Constraints. Pankaj Sharma, Pankaj Sharma,

PMP Course Content. Chapter 1. Introduction to PMP Objectives of PMP Requirements for PMP Exam About PMP Exam PMP Exam Syllabus.

Question Paper Solution (75:25), April 2015 Subject : Software Project Management

Contents. Today Project Management. What is Project Management? Project Management Activities. Project Resources

FACULTY OF MANAGEMENT DEPARTMENT OF APPLIED INFORMATION SYSTEMS

Life Cycle Plan (LCP)

Project Management Professional (PMP) Boot Camp

Project Management Professional

Luis R. Garcilaso March 13, Lecture #22. Service Processes & Systems Dept. of Mechanical Engineering - Engineering Mechanics

Project Plan: MSE Portfolio Project Construction Phase

Q&As. Managing Projects with Microsoft Project Pass Microsoft Exam with 100% Guarantee

Introduction to Project Management

KADI SARVA VISHWAVIDYALAYA BCA SEMESTER III BCA 309 Project Work On Processor Architecture & Utility (304) OR Software Project Management (305)

Implement. Control. Integrate. Knowledge Leverage. Course Overview

RESULTS OF DELPHI FOR THE DEFECT INTRODUCTION MODEL

Software cost estimation

Project Plan Community Forum Version 1.0 Submitted by Nayan Ancha

Project Time Management

PMP EXAMINATION PREP CHAPTER 6 SCHEDULE MANAGEMENT. PMP Exam Prep

A Comparative study of Traditional and Component based software engineering approach using models

E2-E3: MANAGEMENT. CHAPTER-3 PROJECT MANAGEMENT (Date of creation: )

SYED AMMAL ENGINEERING COLLEGE (An ISO 9001: 2008 Certified Institution)

THE BASICS OF PROJECT MANAGEMENT. People~Connect Institute Dr. Dean Russell

12/26/2013. Sharif University of Technology. Session#11. Instructor. Class time. Course evaluation. International Campus Kish

Planning Tools and Techniques Part 2

MINGGU Ke 2 Analisa dan Perancangan Sistem Informasi

Software Engineering. Lab Manual. Software Engineering BE(comp) VII semester

Darshan Institute of Engineering & Technology for Diploma Studies

Software Engineering QUESTION BANK

Successful Project Management

Planning & Scheduling

Unit 9 Information Systems

Software Engineering II - Exercise

Lesson Three: Business Analysis Planning and Monitoring BANA 110 Analyzing Business Needs and Requirements Planning Gary Mesick and Shelly Lawrence,

Project Plan. For Building a Data Management System for FORCE. Prepared for: Andrew Lowery Fundy FORCE

A Primer for the Project Management Process by David W. Larsen 1. Table of Contents

Information Technology Project Management, Seventh Edition

Chapter 4 Document Driven Approach for Agile Methodology

Introduction. Project Scheduling. Morgan State University ARCH 738: REAL ESTATE PROJECT MANAGEMENT. Jason E. Charalambides, PhD, M.

A system is a group of elements organized and arranged so that the. elements can act as a whole toward achieving a common goal; is a collection of

2. What is a phase? A phase is a collection of related activities or tasks that produce a deliverable or work product.

Duration Level Technology Delivery Method Training Credits

Transcription:

Vrije Universiteit Amsterdam Faculty of Exact Sciences Exam: Software Project Management Version A Code: Coordinator: X_401093 Dr. Nelly Condori-Fernandez Date: May 27, 2015 Duration: Calculator allowed: Graphical calculator allowed: 2 hours 45 minutes Yes Yes Number of questions: 8 Type of questions: Open and close questions Total points: The maximum amount of points is 10. Grades: The grades will be made public on: June 10, 2015 Number of pages: 7 (including Appendix)

SOFTWARE PROJECT MANAGEMENT-EXAM All the required tables and formulae can be found in the appendix. FIRST PART First read the following scenario: I was hired by the company Solutions when only the Project Manager (PM) and one senior analyst were on board. As I was the only person with significant experience in building similar recommender systems to the product that our customer needed, the PM asked me to give him an estimate of the project to help him produce a reasonable plan. I estimated the project to take approximately 12 months if we had a team of 4 or 5 members, depending on their skills. My estimates were mainly based on the fact that the customer wasn t sure what exactly they wanted. However, the company had signed a contract for 8 months with the possibility of counting with one senior developer that could be added later to the team. Given that PM agreed completely with my estimates, he and I decided to ask the project sponsor for more staff and for new negotiations with the customer for more time. After a long negotiation, only the customer agreed to extend the total duration to 12 months. But during the project our customer insisted for adding some more features. At the end, we got to complete the project in 16 months! but we had to work day-and-night. 1) Select one of the life cycle models in the list below that you think that PM considered as the most appropriate to complete the project. Explain your rationale (1 point). a) Evolutionary prototyping b) Sashimi model c) Evolutionary delivery d) Design to schedule 2) Identify two risks that the PM could have considered, and propose its respective risk planning. (1.5 point) No Risk Category Root cause Probability Impact 3) Explain what estimation method (s) was (were) used for estimating the development duration of this project. (0.5 point)

SECOND PART 4) Assume that you have information for matching on the basis of two parameters: the number of reads (R), and writes (W) data movements. As PM of a new project, interested in estimating its cost, you found two past cases A and B as more similar to your new project (See table). (1 point) a) Which source case would you use for estimating the new project, A or project B? Justify your choice Projects Read Write Source cases Project A 34 32 Project B 32 34 Target case New Project 30 32 5) Considering that the size of an information system is 800 Cosmic function points (CFP), and it will be developed in FoxPro, estimate the development time required for this project, by considering the following characteristics: - Clear understanding of objectives and requirements, - Number and criticality of risk items is very low, but - Software conformance with external interface specifications is highly needed. - Development team is extensive experienced and highly motivated! (1.5 point) Language SLOC/CFP FoxPro 36 6) The following table represents all the activities of a small project carried out by three developers Maria, Joseph and Fermin. Activities Predecessors Duration A 4 B A 2 C A 6 D A 6 E B 4 F C 5 G D 7 H E,F 3

Activities Predecessors Duration I E 8 J I, G 2 K J, H 3 Draw the activity network (graph), and answer the following questions, by considering the following responsibilities distribution: Resources Activities Maria A, D,G, K Joseph C, F, H, Fermin B, E, I, J a) Identify the developer (s) responsible of critical activities: b) Joseph needs to take 2days-of after finalizing the activity F. Do you think it would cause any delay on the project? Explain your rationale Do you think it would cause any delay on the following activity? Explain your rationale (2 points) 7) Given the following activity network diagram, and estimates for each activity, calculate the probability of meeting the target of 19 weeks. (1.5 point) Activity Optimistic Most Pessimistic duration likely Duration A 3 5 6 B 5 6 8 C 14 18 20 D 13 10 15 E 5 8 10 F 6 7 9

A C 2 4 E 1 0 0 D 3 F 5 B THIRD PART 8) Indicate whether the following statements are true or false, and for the false statements explain the mistake: (1 point) a) A risk is an uncertain event that, if it occurs, has a negative effect on the project's objectives. b) Risk exposure allows us to evaluate the cost-effectiveness of a risk reduction action. c) COCOMO II allows estimating the effort at two different stages of the development process: early design and post architecture. d) Network diagrams help us to identify when resources will need to be deployed to activities. e) A Gantt chart for a project does not show the life cycle model. f) The Work Breakdown Structure (WBS) is used to discuss and validate the requirements with the customer.

Appendix I: Basic COCOMO Table Effort (E) = A size B (person-months) Development time (D) = i (effort) J months People required (P)= E/D Appendix II: COCOMO II Effort= A(size)^(sf) (em1) (em2) (em3). sf = 1.01 + 0.01 Σ scale factors PREC = Precedentedness FLEX = Development flexibility RESL = Architecture/risk resolution TEAM = Team cohesion PMAT = Process maturity

Appendix III: Assessing the Risk to the schedule with PERT Expected duration of an activity/task: te = ( a + 4m + b ) / 6 Standard deviation of an activity/task: s = (b - a) / 6 Standard deviation of a project event S = ((s A ) 2 + (s B ) 2 + (s C ) 2. + (s N )2) = s i 2 i Task Z value: Z = Target duration Expected duration S Appendix IV: Graph of Z-values