426-2 Project Management – (Software Project Planning and estimating)




Скачать 26.06 Kb.
Название426-2 Project Management – (Software Project Planning and estimating)
Дата06.10.2012
Размер26.06 Kb.
ТипДокументы



Northwestern University

426-2 Project Management

Fall, 2009


.

COURSE SYLLABUS

426-2 Project Management – (Software Project Planning and estimating)


Instructor: Mark Werwath, PhD, PMP

Room: D244-Tech

Email: m-werwath@northwestern.edu

Course website: www.courses.nwu.edu

Phone: 847-491-4696


Textbooks:


Software sizing, estimation and risk management. Daniel Galorath and Michael Evans, Auerbach press, 2006


Software engineering economics, Barry Boehm, Prentice Hall, 1981


Software:


All students will need access to a scheduling tool such as Microsoft Project (a demo copy is sufficient and can be obtained from Microsoft’s website or the included CD with the textbook)


All students will need access to PERTMASTER software. A limited use demo copy is available from the PERTMASTER website.


Purpose:

The purpose of this course is to provide an overview of the field of Project Management as applied to software projects with a particular focus in the area of project estimation, planning, performance management and analysis


Philosophy:

The course philosophy is that software development is a particularly challenging problem in industry today and that there is a need for better estimation and planning methodology


Objectives:

Upon completion of the class, the student will be able to:

  1. Apply multiple software estimation methods including DOCOMO, COCOMO and understand feature point, function point and SLOC based estimation techniques

  2. Understand when to use which model and understand the differences between top down and bottoms up planning and estimating

  3. Be able to develop project estimates and plans for various types of software projects in various scenarios and conditions using a variety of analytical tools\

  4. Be able to use software based metrics to manage software projects and to be able to analytically measure performance of a variety of software projects



Syllabus


Week 1: The problem and an introduction to software estimation techniques and estimate planning


Makes the case for why software projects fail and some basic remedies. Overview of the ten step process for software estimation, with a deeper dive on steps one through three

Homework: Read Text Chapter 1 and 2 of Evans textbook. Article: Calculating the PM return on investment




Week 2: Executing the estimate-software sizing and the use of software metrics The software lifecycle


Predicting the size of software in multiple dimensions such as source lines of code and function points/feature points. Deeper dive in steps four through six. A lok at bottoms up estimating and activity based estimates. Also a deep dive on the software lifecycle as defined by Dr Barry Boehm

Homework: Read Text Chapter 3 of Evans textbook. Boehm text chapter 4


Week 3: SLOC versus function points, the eternal debate

The discussion will be focused on which technique makes more sense and under what conditions. SLOC is focused on the output of software development while function points is focused on the expectations or the input


Homework: Read chapter 4 and 5 of the Evans text


Week 4: Software estimation models, Basic and intermediate COCOMO models


Based mostly on the historical work of Dr Barry Boehm and the product level estimates and the component level estimates that he defined in his text. The COCOMO model has been the basis of software estimation models for many years and we will discuss the basic formulas used in his model


Homework: Read Chapters 5 through 9 of Boehm text


Week 5: Software cost estimations-alternative models and detailed cocomo models

We will discuss the alternative estimation models and the detailed cocomo model described in Barry Boehm’s text

Homework Read chapter 21 through 29 of Boehm’s text


Week 6: Software maintenance and lifecycle estimations. This will be a high level overview software maintenance lifecycle estimations. Once again we turn to COCOMO based models and include an example of software cost benefit analysis


Homework: Read Chapters 30-31 of Boehm text


Week 7: Software project planning. This will be a high level overview software project planning using critical path techniques and Microsoft project planning software. In addition, we will highlight the use of Monte Carlo simulation techniques


Homework: Read Chapter 4 of Evans text

Midterm exam to include project planning and all material to date


Week 8: Risk management and performance management of the project

Understanding how to use performance management tools in the project management of the software project.The active management of risks and the creation of risk mitigation strategies will be explored. The use of rigorous decision making and decision analysis techniques will be explored as well as the basics of subcontract management will be explored


Homework: Read Chapters 9-10 of Evans text,


Week 9: Student led discussion on the use of new development methodologies in software development. Particularly the use of agile methods


There is a large number of new software development methodologies incuing RUP, extreme programming and SCRUM. At least four of these new methodologies will be explored with the help of student presenters and facilitators


Homework: read article on agile methods. Four or more students will present their findings on software development methodologies and how they impact software planning and estimating


Week 10: Student led discussion on software estimation tools available on a commercial basis


Many tools are now available on a commercial basis that are built on COCOMO and other estimation frameworks. The purpose of this discussion is to determine which are particularly useful and in what applications. At least 4 students will present their findings on one particular tool each

Course grading

Midterm examination 30%

Estimation exercise 10%

Scheduling/MonteCarlo 10%

In class participation 10%

Methodologies and tools paper 20% each (Includes student led discussions, at least 20 minutes)

Final exam-take home 20%




Paper requirements for 426-1


Estimation exercise


A software project estimation using SLIM, DOCOMO or other software estimation tool will be assigned.

Scheduling exercise



A scheduling exercise will be assigned that requires use of MS Project and PERTMASTER


Program Management Bibliography

Werwath, Fall, 2009


Assessment and Control of Software Risks, Capers Jones, Prentice Hall, 1994. (A classic SW project management text focused on risk management)


Augustine’s Laws, Top Executive Looks at the Complexities of Today’s Business Management and Offers Solutions, Norman R. Augustine, AIAA, 1997. (A sarcastic yet insightful look at modern corporations)


Beyond re-engineering, How the process centered organization is changing our work and our lives, Michael Hammer, Harper Collins Business, 1996. (Among one of the classic Hammer texts on business process re-engineering-BPR)

Breakthrough Technology project management. Kathryn P. Rea, Academic Press, 1998



Comprehensive Project Management: Integrating optimizing models, management principles and computers, Adedeji Badiru, P. Simon Pulat, Prentice Hall, 1994. Somewhat obscure text looking at PM from the enterprise perspective


Creating an Environment for Successful Projects, Robert Graham, Jossey-Bass, 1997 (One of the newer texts on the systemic issues that often block PM implementation-recommended)


Essentials of Project and Systems Engineering Management, Howard Eisner, Wiley, 1997 (Systems engineering focused-Text option 1)


Finding Time, How Corporations, Individuals and Families can Benefit from New Work Practices, Leslie A. Perlow, Cornell University Press, 1997. (A quick read on time management in the 90s)


Fusion Leadership: unlocking subtle forces that change people and organizations, Richard A. Daft,


A Guide to the Project Management Body of Knowledge-PMI Standards committee, 1996 (a bit dry but a useful and well organized reference, the PM standard!)


Handbook of Leadership Development, Center for Creative Leadership, Jossey Bass, 1998


Hope is not a Method, Gordon R. Sullivan, Broadway Books, 1996. (Military approach, written by an ex-general. Great stuff on learning organization and after action reviews- recommended)


Leadership is an Art, Max DePree, Dell Publishing. (Quick but insightful read on leadership-inspirational- recommended)


Managing High technology programs and projects, Russell D. Archibald. 3rd edition, Wiley and Sons, 2003. very practical text from an IT perspective


Managing New Product and Process Development: Text and Cases,

Kim B. Clark and Steve C. Wheelwright, Free Press, 1993. (Somewhat dated casebook from Harvard Business School-A classic in its day)


Mastering Virtual Teams, Deborah Duarte, Jossey Bass, 1999


Organizational Culture and Leadership, Edgar Schein, Jossey Bass, 1992


Presentation of self in everyday life, Erving Goffman, Anchor, 1959


Principle Centered Leadership, Stephen R. Covey, Simon and Schuster, 1991. (Spiritual oriented approach to leadership)


Productive Workplaces, Organizing and Managing for Dignity, Meaning and Community, Marvin Weisbord, Josey-Bass, 1987. (More of an OD text, traces the history of management science very nicely)


Project Manager’s Desk Reference, James P. Lewis, McGraw Hill, 1995. (Alternate text 2, not as robust, more of a soft view of PM)


Project Management, Paul Tinnirello, Auerbach, 2000 (Best practices text)


Project Management Handbook, Jeffrey K. Pinto, Jossey Bass, 1998


Project Management for Business and Technology, John M. Nicholas, Prentice Hall, 2001


Project Management, The Managerial Process. Clifford F. Gray, Erik W. Larson, McGraw Hill, 2003


Project Manager’s Portable Handbook, David Cleland, Mcgraw Hill, 2000


Project Management-Strategic design and Implementation, David Cleland, McGraw-Hill, 1999 (Alternate text 4, somewhat obscure but a refreshing look at PM)


Radical Project Management, Rob Thomsett, Prentice Hall, 2002. This is an unconventional view of project management….one that is needed to balance the more conventional views


Rapid Development, Taming Wild Software Schedules, Steve McConnell, Microsoft Press, 1996 (Very software oriented and a little wild. The author has wonderful, and sometimes fun, insights and it’s a great read but a long read)


Reinventing Work-The Project 50, Tom Peters, Knopf, 1999 (A quick fifty things to do….an unusual book for those who like lists)



Syllabus 426-1 Project Management Page of 05/09 MW

Похожие:

426-2 Project Management – (Software Project Planning and estimating) iconAppears in all copies. Project Management Organizations International Project Management Association (ipma)

426-2 Project Management – (Software Project Planning and estimating) iconSchool planning: new perspectives from project management

426-2 Project Management – (Software Project Planning and estimating) iconSoftware Engineering and Project Management

426-2 Project Management – (Software Project Planning and estimating) iconProject Management Methodology This list of suppliers was pre-qualified for the ict management Consultants multi-use list category of Project Management Methodology. Version 42. 0 – 31 July 2012

426-2 Project Management – (Software Project Planning and estimating) iconPreparing project managers to deal with complexity Advanced project management education 1

426-2 Project Management – (Software Project Planning and estimating) iconProject Governance This list of suppliers was pre-qualified for the ict management Consultants multi-use list category of Project Governance. Version 41. 0 – 30 June 2012

426-2 Project Management – (Software Project Planning and estimating) iconProject Governance This list of suppliers was pre-qualified for the ict management Consultants multi-use list category of Project Governance. Version 43. 0 – 31 August 2012

426-2 Project Management – (Software Project Planning and estimating) iconSuccess driven project management
Эта методология поддерживается пакетом управления проектами Spider Project, который снабжает команду управления проектами следующей...
426-2 Project Management – (Software Project Planning and estimating) iconРешение Microsoft® Enterprise Project Management (epm) 7
Приведенные в качестве примеров снимки экрана и функциональные возможности продукта соответствуют бета-версии Project 2010. Фактические...
426-2 Project Management – (Software Project Planning and estimating) iconSyllabus mgt613 Project Portfolio Management and Program Management Office

Разместите кнопку на своём сайте:
Библиотека


База данных защищена авторским правом ©lib.znate.ru 2014
обратиться к администрации
Библиотека
Главная страница