brought to you by: jeremy miller brought to you by: jeremy miller.

Slides:

Advertisements

Similar presentations

Effort metrics: Man-month. Mythical Man Month – the book Brooks lead development of OS/360 and reflected on the problems experienced in the project. The.

Advertisements

Robert Lockyer.

Project Management Information Systems and Management.

Project Management Information Systems and Management.

LiberRATE Estimating It thinks like you do! Edition 3 Instructions Click on buttons to advance or to repeat the previous slide PreviousNext.

CHAPTER 6 BUDGETING How Will You Use Your Money?

1 Software Processes Name:Wassim Jamal Salem ID: Name:m3taz El Dweak ID:

Software Process Models

The Crippled Team The Story of CONFIRM CS 524 – Software Engineering Dr. Sheldon X. Liang 18 Sept 2007 Darryl Nakata.

The Mythical Man-Month By: Zac Lippard CS 470. What is the “Man-Month”? This is the idea that men and months are interchangeable between each other. This.

1 Software process models Name :Mohammed Khalid Alkhalily ID: Name:Wassim Jamal Salem ID:

Informatics 43 – April 21, Things to know Midterm on Thursday – Closed book, closed notes, bring pen/pencil – Questions available on web site (updated)

INSE - Lecture 6a Prototyping. Or: “ Not building a Leaning Tower …”

Systems Analysis and Design 8th Edition

What will you choose?  Benefits  Good Grades  High GPA  Pass Class  Detriment  No time to socialize  Takes too long.

Informatics 43 – May 12, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases 

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.

Project Management Lecture Resource Analysis. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.

Software Engineering About the Course Software Engineering Qutaibah Malluhi Computer Science and Engineering Department Qatar University.

Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.

Software Technology Support Center BE AMERICA’S BEST The Problems in Software Estimating Dr. Randall Jensen Software Technology Support Center Hill AFB,

SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.

Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.

Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.

Client Logo LEAN ENTERPRISE Implementation Workshop.

Date: April 8, 2013 Topic: Unemployment Aim: How does unemployment manifest itself? Do Now: Multiple Choice Questions.

Full Time Employment A full time employee generally works five days a week. Employment is often permanent. The amount of hours worked by the average full.

Why is software engineering worth studying?  Demand for software is growing dramatically  Software costs are growing per system  Many projects have.

Slide TMMM.1/28 The Mythical Man-Months. Slide TMMM.2/28 Overview Fred Brooks and OS/360 The Mythical Man-Month What has and has not changed? No Silver.

Time-Cost Tradeoffs Time-Cost Tradeoff Example Time-Cost Tradeoff Example (cont’d) Project Duration (weeks)Critical Path(s)Task(s) Reduced Total Direct.

Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.

Advanced Project Management Project Time Management Ghazala Amin.

Cost Estimation What is estimated? –resources (humans, components, tools) –cost (person-months) –schedule (months) Why? –Personnel allocation –Contract.

Managing Resources Program Evaluation and Review Technique (PERT) Production Process.

CS 501: Software Engineering Fall 1999 Lecture 6 Management I: Project Management.

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.

Chapter 15 GIS Design and Implementation Management Information Systems –Systems Analysis –Systems Design –Systems Implementation.

Project Schedules Chapter 4 Applied Software Project Management, Stellman & Greene See also:

Mythical Man Month By Ryan Ruzich.  More software projects have gone awry for lack calendar time than all other reasons combined.

Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.

Tata McGraw CHAPTER 3 Project Management. Chapter 3 Project Management.

Tempus Software Project Management SE603 Unit 1: SPM Basics Vasa Case Study Egypt,

Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.

CSE 403 Lecture 25 Scheduling and Planning a Large Project Reading: The Mythical Man-Month, Ch. 2, by F. Brooks slides created by Marty Stepp

CSE-332 Software Design Methods The Mythical Man-Month 박성우 POSTECH October 20, 2015.

Costs by Category  Purchasing hardware  Purchasing software  Purchasing computerized delivery system  Adding bar codes to holdings  Moving costs 

CSC 480 Software Engineering Project Planning. Proposal writing Project planning and scheduling Project costing Project monitoring and reviews Personnel.

Toolbox Meetings What is a toolbox meeting? An informal 5 to 15 minute meeting held by supervisors used to promote safety.

By: Amjad M. Omari 1.  Time is a competitive weapon. Even the best strategies, tactics, systems, and people will lose the battle if they arrive at the.

COMPUTER NETWORKS Quizzes 5% First practical exam 5% Final practical exam 10% LANGUAGE.

1 Team Skill 4 Managing the scope Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and Information Technology Based.

Multiplication Timed Tests.

Section 11.1: Solving Linear Systems by Graphing

Project Management Operations -- Prof. Juran.

Why is software engineering worth studying?

Lecture 3 Prescriptive Process Models

Informatics 43 – May 10, 2016.

Software Process Models

THE MYTHICAL MAN-MONTH

Informatics 43 – April 19, 2016.

Software life cycle models

Project management Lecture 9

4th Edition Chapter 20 Design Teams.

Software Process Models

cs205: engineering software

Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.

Warm Up 1) A t-shirt company makes shirts in sizes S, M, L, XL and XXL and in the colors chartreuse, burgundy, fuchsia and mauve. How many different types.

CSE 403 Scheduling These lecture slides are copyright (C) Marty Stepp, 2007, with significant content taken from slides written by Valentin Razmov. They.

Four seasons T T P 2012.

Complete the family of four

Presentation transcript:

brought to you by: jeremy miller

brought to you by: jeremy miller

 What it’s NOT:  It’s NOT an imaginary man month in which the Super Bowl BCS Championship World Series NBA Finals The Final Four The Masters Deer Season Elk Season Duck Season Pheasant Season …all take place!

 What it IS :  It IS a software engineering scheduling monster  It IS a commonly used practice of project management  It IS useless in most software engineeringenvironments.

 The ‘Man-Month’ is a calculation: 1 Man = 1 Month i.e. A job that would take 1 man 5 months to complete will take 5 men 1 month to complete.

 The ‘Man-Month’ will not work for a software engineering project  Software Engineering is governed by sequential constraints and is linear.

 The ‘Man-Month’ will not work for a software engineering project  Each new worker would require time to bring them ‘up to speed’  Extends the amount of time required to complete the project.

 System Testing – does not benefit from additional resources.  Systems Testing is the biggest pit-fall in project planning  Systems Testing should be allowed at least ½ the total time allotted for project completion.  More time allotted for testing instead of more personnel.

 Be liberal with project completion estimates.  Too often an estimate of completion is based on what the boss or client want to hear.  A more realistic time estimate or padding of time estimate (set yourself up for success, give yourself a chance to be a hero)

 System Testing – does not benefit from additional resources.  Systems Testing is the biggest pit-fall in project planning  Systems Testing should be allowed at least ½ the total time allotted for project completion.  More time allotted for testing instead of more personnel.

 Failing to meet un-aquireable goals.  A snowball effect happens when inadequate time is allotted and incorrect steps are taken to correct the issue.  Makes you look incompetent  Wastes money/time/resources

 When more manpower works for Software Engineering  More manpower should be directly related to the number of independent subtasks  “Adding manpower to a late software project makes it later” Brooks Law

“More software projects have gone awry for lack of calendar time than for all other causes combined.” P roper P roject P lanning P revents P reposterously P athetic P roblematic P rojects