Syllabus

IT Resource Planning: IT343, Sections 2 & 3

Spring 2007

Professor James Moody
email jmoody@gmu.edu
Office Bull Run Hall, Room 122
Office Hours Wednesdays: 3:30 to 4:30 PM
Teaching Assistants Section 2: Vishnu Paturi; Section 3: Kavyashree Devarajaiah
email vpaturi@gmu.edu; kdevaraj@gmu.edu
Office Bull Run Hall, Room 122
Office hours Paturi: TBA
Devarajaiah: TBA

 

Class hours Section 2: Wednesdays, 4:30 to 7:10 PM,
Section 3: Fridays, 1:30 to 4:10 PM.
Classroom Bull Run Hall,
Section 2: Room 256,
Section 3: Room 258

Text:

Required: Schwalbe, Kathy, Information Technology Project Management, FOURTH Edition. Course Technology, 2005. ISBN: 0-619-21526-7
This text runs about $80.

Additional electronic texts posted on WebCT: see detailed reading assignments.

Course Objectives:

  1. Understand the importance of project management in improving the success of information technology projects.
  2. Understand the constraints of project management.
  3. Learn the project lifecycle, project management knowledge areas and process groups.
  4. Learn tools and techniques of project management, such as:
  5. Appreciate the importance of good project management and share examples of good and bad project management.

Course Structure:

The course will be conducted as a mixture of lecture and discussion. Students are expected to actively participate. Teams of students are expected to research a project management knowledge area and present their findings to the class. Students are expected to write a research paper on the management of a real-life project as a whole.

Assignments:

Assigned exercises are due as specified below. Exercises are more fully described in the assignment tool in WebCT. Late assignments will not be accepted. In some cases the exercise calls for a short paper to be written; such papers should not exceed 700 words.

Research Paper:

Students will research a project of their choosing (not necessarily, at least not required to be, an IT project) and write a paper (between 1500 and 2500 words) describing the management of the project in PMI terms, that is, mapping what was actually done by the project manager to what would have been done had the theoretical PMI project management structure been followed.

Presentations:

Developing presentation skills is important for everyone, plus it's a good way to share information. Students will sign up to be part of a team to present on each of the PMI-defined knowledge areas. Each student will prepare and present a presentation coordinated with the rest of their team on some aspect of their knowledge area. The combined presentations of the team should cover its knowledge area. Students should sign up for their preferred knowledge area as soon as possible: first come, first served. Presentations should be intended to run approximately 10 minutes. Presentations will be evaluated on coordination, content and delivery.

Exams:

There will be two exams: a Midterm and a Final. Both will be closed book, in-class. There will be no makeup exams for any reason.

Grades:

Course scores are computed as follows:
Assigned exercises 24%
Presentation 16%
Midterm exam 15%
Paper 20%
Final exam 25%
Total 100%

The numerical score is then translated into a letter grade using the following scale:
A: 94-100
A-: 90-93
B+: 86-89
B: 83-85
B-: 80-82
C+: 75-79
C: 70-74
D: 60-69
F: 0-59

Academic Honesty:

Plagiarism and cheating are serious offenses and may be punished by failure on an exam or assignment or failure in the course. They are also violations of the GMU Honor Code and may be reported to the Honor Committee.

Schedule:

When Lecture Topic Reading Presentations Assignments Paper
Week 1;
Jan 24th
Jan 26th
Introduction, Context, Professional Responsibility        
Week 2;
Jan 31st
Feb 2nd
Process Groups, Case Studies Schwalbe, Chapters 1 through 3;
ResNet Case Study (large pdf on WebCT);
CHAOS Report (link from WebCT)
  Summarize the CHAOS Report  
Week 3;
Feb 7th
Feb 9th
Integration Management,
Communications Management
Schwalbe, Chapters 4 & 10;
McCready, How to do ROI (pdf on WebCT)
  Summarize outputs of process groups in ResNet Case Study  
Week 4;
Feb 14th
Feb 16th
Scope Management Schwalbe, Chapter 5 Scope Management Stakeholder Analysis  
Week 5;
Feb 21st
Feb 23rd
Work Breakdown Structure   Cost Management   Topic and Plan due
Week 6;
Feb 28th
Mar 2nd
Cost Management Schwalbe, Chapter 7;
Longstreet, Function Point Manual, Chapters 1-3 (pdf on WebCT)
Time Management Cost Spreadsheet  
Week 7;
Mar 7th
Mar 9th
Time Management,
Review For Midterm
Schwalbe, Chapter 6   Network Diagram  
Week 8;
Mar 14th
Mar 16th
Spring Break:
No Class
Study for Midterm!      
Week 9;
Mar 21st
Mar 23rd
Midterm Exam        
Week 10;
Mar 28th
Mar 30th
Midterm Review,
Quality Management
Schwalbe, Chapter 8;
Spolsky, on Bug Fixing and on Bug Tracking (links from WebCT)
Quality Management   Data and Draft due
Week 11;
Apr 4th
Apr 6th
Using Microsoft Project Schwalbe, Appendix A   Pareto Diagram  
Week 12;
Apr 11th
Apr 13th
Risk Management Schwalbe, Chapter 11 Risk Management Risk Identification  
Week 13;
Apr 18th
Apr 20th
Procurement Management Schwalbe, Chapter 12 Procurement Management MS Project Exercises  
Week 14;
Apr 25th
Apr 27th
Human Resource Management Schwalbe, Chapter 9;
Spolsky, Guerilla Guide to Interviewing (link from WebCT)
Human Resource Management   Paper due.
Week 15;
May 2nd
May 4th
Project Management as a process
Review for Final Exam
Benkler, Wealth of Networks, Chapters 3 & 4 (pdfs on WebCT)      
Week 16;
May 9th
May 11th
Final Exam