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

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.
brought to you by: jeremy miller brought to you by: jeremy miller.
United Nations Statistics Division Revision policy and dissemination practices Training Workshop on the Compilation of Quarterly National Accounts for.
Systems Analysis and Design 8 th Edition Chapter 3 Managing Systems Projects.
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.
Informatics 43 – April 21, Things to know Midterm on Thursday – Closed book, closed notes, bring pen/pencil – Questions available on web site (updated)
Systems Analysis and Design 8th Edition
Informatics 43 – May 12, Restatement of Goals for Testing Want to verify software’s correctness  Need to test  Need to decide on test cases 
Chapter 1: Key Points Program = Useful to the programmer in the garage Programming Product = Useful to anyone Programming System Component = Part of a.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
CS189A/172 - Winter 2008 Lecture 5: Project Management.
The Mythical Man-Month Due Today: Code & Coding Standards Due Next Class: Quiz #3; see webpage Mythical Man-Month I Bio Break Mythical Man-Month II Questions.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 4.
Mythical Man Month Fred Brooks, Why are software projects late? Estimating techniques are poorly developedEstimating techniques are poorly developed.
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
CSE 230: Introduction to Software Engineering Topics covered: Introduction.
Project Management March 9, 2001 Dr. Richard Chung Dept. Chemical & Materials Engineering San Jose State University.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
1 Project Planning CIS 375 Bruce R. Maxim UM-Dearborn.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
Copyright © 2009 T.L. Martin & Associates Inc. Chapter 3 Requirements of a realistic CPM schedule.
Toolkit 4.
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Why is software engineering worth studying?  Demand for software is growing dramatically  Software costs are growing per system  Many projects have.
CSC 354 – Software Engineering, Spring 2013, Week 2 Mythical Man-Month Ch. 1-5 Tar Pit, Mythical Man-Month, Surgical Team, Aristocracy / Democracy & System.
The Mythical Man-Month the MYTH behind the REAL
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.
Software Project Management
Software cost estimation Predicting the resources required for a software development process 1.
1 Software Process and Project Metrics. 2 Normalization for Metrics.
Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
Chapter 23 – Project scheduling Lecture 1. Project scheduling  Project scheduling is the process of deciding how the work in a project will be organized.
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.
Chapter 15 GIS Design and Implementation Management Information Systems –Systems Analysis –Systems Design –Systems Implementation.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.
Lecture 6 24/9/15. Project … is a planned undertaking that has a beginning and an end and that produces a desired result or product Organized activities.
Chapter 3 Managing the Information Systems Project
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.
Chapter Eighteen Proposition of the Mythical Man Month: True or False?
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
Project Management Overview U08784Software Project Management Rosemary Phillimore.
CSE-332 Software Design Methods The Mythical Man-Month 박성우 POSTECH October 20, 2015.
Unit 14 University of Sunderland CSEM04 ROSCO 1 Unit 14: The Link with Project Management CSEM04: Risk and Opportunities of Systems Change in Organisations.
Slide 1 CS 310 Ch5: Project management What do you think is involved? Proposal writing Project costing Project planning and scheduling Project monitoring.
Lecture 6 Title: Project Cost Management MIS 434.
CSC 480 Software Engineering Project Planning. Proposal writing Project planning and scheduling Project costing Project monitoring and reviews Personnel.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
IT-301 Project Management I: Unit 4: Cost Management.
Estimation Questions How do you estimate? What are you going to estimate? Where do you start?
Why is software engineering worth studying?
Informatics 43 – May 10, 2016.
IS301 – Software Engineering V:
Software Project Planning and Tracking
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION
THE MYTHICAL MAN-MONTH
Informatics 43 – April 19, 2016.
Informatics 43 Discussion 13 May, 2016
Project management Lecture 9
Chapter 23 – Project planning
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
CSE 403 Scheduling These lecture slides are copyright (C) Marty Stepp, 2007, with significant content taken from slides written by Valentin Razmov. They.
Presentation transcript:

Mythical Man Month By Ryan Ruzich

 More software projects have gone awry for lack calendar time than all other reasons combined.

 Our techniques of estimating are poorly developed  Our technqiues confuse effort with progress  We are therefore uncertain of our time estimates, and thusly software managers lack stubbornness to stick to schedules.  Our techniques of estimating are poorly developed  Our technqiues confuse effort with progress  We are therefore uncertain of our time estimates, and thusly software managers lack stubbornness to stick to schedules.

 Schedule Progress is poorly monitored in most projects  When schedule slippage is noticed, the gut reaction is to put more men on the task, which is the worst thing that can happen.  Schedule Progress is poorly monitored in most projects  When schedule slippage is noticed, the gut reaction is to put more men on the task, which is the worst thing that can happen.

 Cost does indeed vary as the product of the number of men (X) and the number of months (Y). X*Y  Progress does not.  Hence, the man month as a unit for measuring the size of a project is flawed.  Cost does indeed vary as the product of the number of men (X) and the number of months (Y). X*Y  Progress does not.  Hence, the man month as a unit for measuring the size of a project is flawed.

 Men and Months can be interchanged when a task can be partitioned among many workers with no communication.  When workers need to communicate, the formula changes to n(n-1)/2.  Men and Months can be interchanged when a task can be partitioned among many workers with no communication.  When workers need to communicate, the formula changes to n(n-1)/2.

 A successful division of a total projects time is:  1/3 for Planning  1/6 for coding  1/4 for component and early systems test  1/4 for systems test  A successful division of a total projects time is:  1/3 for Planning  1/6 for coding  1/4 for component and early systems test  1/4 for systems test

 Adding Manpower to a late project *ONLY* makes it later.  The number of months of a project depends upon its sequential constraints.  The maximum number of men depends on the number of independent subtasks.  Adding Manpower to a late project *ONLY* makes it later.  The number of months of a project depends upon its sequential constraints.  The maximum number of men depends on the number of independent subtasks.