CIS 479 Section 101 Software Project Management

1
CIS 479 - Section 101Software Project Management

• Dr. Robert J. Hammell II
• rhammell_at_towson.edu

2

• Software Project Management
• CIS 479 - Spring 2007
• Meeting Times Wed, 700 pm 940 pm, YR301
• Professor Dr. Robert J. Hammell II
• Office 476YR
• E-Mail rhammell_at_towson.edu
• Phone [phone]
• Office Hours Mon 330 pm 430 pm
• Wed 600 pm 700 pm
• Thur 330 pm 430 pm
• Other times by appointment

3

• Course Description
• This course examines the factors necessary for
  the successful management of information systems
  development or enhancement projects.
• Both technical and behavioral aspects of project
  management are discussed. Topics include project
  management concepts, needs identification, the
  software project manager, software teams,
  software project organizations, project
  communications, software project planning,
  scheduling, control and associated costs.
• Project management software tools will be an
  integral part of the course.

4

• Course Objectives
• Upon completion of this course, students will
  be able to
• Define a project
• Describe the project life cycle
• Explain the project management process
• Analyze and evaluate a request for proposal
• Develop a project proposal
• Formulate a plan and schedule for an IT project
• Perform cost performance analysis for a project
• Discuss the responsibilities and required skills
  of a project manager
• Explain project team development, effectiveness,
  and communication
• Operate as part of a project team
• Identify the characteristics of each type of
  project organization structure

5

• Textbook
• Gido, J. and Clements, J., Successful Project
  Management, 3rd Edition, South-Western
  Publishing, 2006. (ISBN 0-324-22428-1)

6

• References
• Bennatan, E., On Time and Within Budget
  Software Project Management Practices and
  Techniques, 3rd Edition, Wiley, 2000.
• Doss, G., IS Project Management Handbook,
  Prentice Hall, 2000.
• Friedrichsen, L. and Bunin, R., Microsoft
  Project 2000, Course Technology, 2000.
• Kemerer, C., Software Project Management
  Readings and Cases, Irwin, 1997.
• Olson, D., Information Systems Project
  Management, Irwin, 2000.
• Pinto, J. (editor), Project Management Handbook,
  Jossey-Bass, 1998.
• Journals
• International J. of Project Mgmt MIS
  Quarterly
• Project Management Journal PM Network

7

• Prerequisite
• CIS 379 Systems Analysis Design
• Grading

8
(No Transcript)
9

• Exams
• The exams will include questions from the
  lectures, readings, presentations, and projects.
• Note that, under most circumstances, makeup
  exams will not be given. Please ensure your
  attendance on the scheduled exam dates.

10

• Presentations
• Each student will be required to present a
  published paper on an IT project management
  topic. The presentations will be conducted as
  follows
• 3 or 4 papers will be assigned to be read outside
  of class.
• During the next class, students will form into
  groups. Each group will be assigned
  responsibility for preparing the discussion for
  one paper
• After the group work period, one person per paper
  will be selected to present the paper to the
  class
• The format for the presentation will be provided
• The presentation should last 5-7 minutes, plus
  questions
• Not all groups will present each week
• During the semester, every person will present at
  least once
• Information from the papers is testable
• The process for conducting the presentations may
  be changed or refined as the semester progresses.

11

• Homework
• Several homework assignments will be given
  throughout the semester to reinforce the topics
  discussed in class.
• Most will be individual assignments unless the
  assignment is specifically and clearly indicated
  to be a team assignment it must be completed by
  individual effort only.

12

• Term Project
• Students will be required to work in teams on a
  major IT term project. Note that this project
  comprises 25 of the course grade!
• The project will entail completing all steps of
  the systems development life cycle (except for
  actual implementation) for a given scenario. The
  deliverables for the project are a comprehensive
  report and an in-class presentation.
• Details on the specific scenario will be provided
  when the project is assigned.

13

• Attendance
• Attendance will be taken in every class session.
  
• Absences are considered excused if they are
  for an illness, an illness or death of a
  relative, or a religious observance. If
  documentation is provided for an excused
  absence, it will not count against you.
• After your first unexcused absence, each
  additional unexcused absence will cause 1 to be
  deducted from your final grade at the end of the
  semester.
• Note that students are expected to arrive at
  class on time!

14

• Assignments
• Assignments are due at the beginning of class on
  the due date.
• Any assignments that are submitted late will
  have 10 deducted from the total grade for each
  day that the assignment is late. Assignments
  submitted at the end of the class period count as
  one-day late.
• Unless told otherwise, assignments may not be
  submitted by email attachment (there may be cases
  when emailed assignments are preferred).

15

• Academic Dishonesty
• The Towson University policy on academic
  integrity is in the undergraduate catalog.
  Academic dishonesty specifically includes acts of
  plagiarism, fabrication and falsification,
  cheating, abuse of academic materials, and
  multiple submissions.
• Especially note that students may not re-use
  research papers submitted in other classes, group
  projects submitted in other classes, or work
  performed by someone else. Academic dishonesty
  is disrespectful to your fellow students and your
  professor.
• If an incident of academic dishonesty is
  discovered, the student or students involved
  will, at a minimum, receive a zero (0) on the
  related assignment(s). All occurrences of
  academic dishonesty will also be reported to the
  appropriate university officials. There will be
  no exceptions.

16

• Repeating a course
• University policy requires that we inform you
  that students may not repeat a course more than
  once without prior permission of the Academic
  Standards Committee.
• Dropping this course
• Feb 6 Last day to drop with no grade posted
• Apr 9 Last day to drop with a grade of W
• Posting of grades
• Please note that it is university and
  departmental policy not to post grades in a
  public place after the semester is completed. It
  is also departmental policy that the departmental
  office cannot distribute individual grades. If
  you would like to receive your individual grade
  at the end of the semester, please make
  arrangements with me.

17

• Cell phones, laptops, etc. Please ensure that
  all cell phones, beepers, and any other devices
  that can potentially disrupt the class are turned
  off each day upon entering the classroom. Such
  devices must also be in pockets, purses,
  bookbags, etc. and not out on the desk during
  class. Laptops are to be turned off and closed
  during class.
• Web site A link to the CIS 479 web site can be
  found at
• http//triton.towson.edu/rhammell/
• Students should check the site frequently for
  updates on assignments, assignment due dates, the
  day-to-day schedule, readings, and other
  announcements.

18

• ABSOLUTELY NO FOOD
• IS ALLOWED IN THIS ROOM!
• Drinks are okclean up after yourself!

19

• Day-to-day schedule
• Web site
• Initial Project Information