Last modified September 23, 2018

COMP 477 / 377, Fall, 2018—Schedule

DateTopic(s) ReadingAsgn.
Aug. 27 Course introduction
Brief background and history of I.T. project experience and pitfalls
Roles and responsibilities in a project team.
A phased Life Cycle for system development
- Textbook review
- Brooks: Chapters 1 & 3
- Management Discipline
- Role Definition
1 -
Sep. 3 Labor Day holiday
Sep. 10Specifying a task and its deliverables
Estimating resources and duration for a task
Forming a task network
Analyzing the critical path and aggregating task estimates
Using project-management software (part 1)
Launching an application system development project; the project charter
Assignment #2 team formation and work session
- Waterfall Approach
- Brooks: Chapter 2
- Burden of Proof
- Two Rules
- Planning a Simple Project with MS-Project
2 -
Sep.17Using project-management software (part 2)
Communication within the project team—the project workbook
Determining and documenting business system requirement
Justifying a project; return on investment
Specifying computer system requirements for a proposed new application system—part 1
Brooks: Chapter 7
- Requirements Crisis
- -
Sep 24Specifying computer system requirements for a proposed new application system—part 2: Specifying data
Review of first part of the course.
- Brooks: Chapters 8 & 11
- What Ever Happened to Systems Analysts?
- 1
Oct. 1 Discussion of assignment #3 and team assignments.
Brief (20 minutes) study period for questions.
Mid-term examination
- 3 2
Oct. 8Fall break (Columbus Day) ---
Oct. 15 Mid-Term examination sample answers
Managing changes during the project
Staffing for a major programming effort
- Requirements Are not Discrete
- Defining Data Items
- Implicit Data Dictionaries
- -
Oct. 22 Estimating the life cycle
Highlights of textbook chapters
Brooks: Chapter 4
Legacy Systems
4 -
Oct. 29 Testing an application system
Stages of testing
Manual versus automated testing
Continuous testing strategies
Overview of ESD deliverables
Unit testing
- 3
Nov. 5Status reporting—task level
Incremental and "agile" alternatives
Status reporting—project level
Project planning for purchasing and installing
an application software product
-Have we lost our minds?
- Agile methods
- Task status is binary
5 -
Nov. 12 Late stage decisions:
- testing shortcuts.
- scope reduction
- slippage & overrun negotiation Professional activities, publications, and certification for the project manager.

Post project review and analysis
Human factors and personnel issues
- Deadlines and Target Dates
- Requirements shortcuts for packaged application software products
- Brooks: Chapter 14
- 4
Nov. 19 Professional activities, publications, and certification for the project manager.
Alternatives to the phased life cycle
Impact on project management of "Agile" and other fad methodologies
- Instilling Professionalism
- Brooks: Ch. 15 & 16
- Stereotyping distorts personnel management
- Theory X & Theory Y
6 -
Nov. 26 Assignment 4 in-depth discussion and comparative analysis of alternatives: Application of important principles covered in this course. - Insubordination an Agile Tradition?
- Exceeding Estimates: a "Waterfall" Failure?
- False phases
- Chrysler project
- Unified Process
- 5
Dec 3 Course review & final exam. preparation Déjà Lu Yet Again! - - 6
Dec 10Final examination
Suggested answers (posted after December 10)

Return to Syllabus

Last updated Septem,ber 23, 2018