CIS 479 Software Project Management

1. CIS 479Software Project Management Dr. Robert J. Hammell II rhammell@towson.edu

2. Software Project Management CIS 479, Fall 2014 Meeting Times:Tues/Thur, 5:00 – 6:15 pm, YR401 Professor:Dr. Robert J. Hammell II Office:462YR E-Mail:rhammell@towson.edu Phone:410-704-6050 Office Hours:Tues: 4:00 pm – 5:00 pm 6:15 pm – 7:00 pm Thur: 4:00 pm – 5:00 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. IS Program Objectives • Students can use their proficiency in information systems principles & practices and quantitative analysis to solve a variety of problems. • Students can explain the quantitative and business principles that underlie information systems. • Students will understand the ethical and societal concerns and dilemmas facing information systems professionals and can formulate appropriate solutions and courses of action. • Students can work effectively in teams and communicate effectively.

6. Textbook: Gido, J. and Clements, J., Successful Project Management, 5th Edition, South-Western Publishing, 2006. (ISBN: 978-0-538-47897-7)

7. References: • PMI, A Guide to the Project Management Body of Knowledge: PMBOK(R) Guide, Project Management Institute, 2013 • Kerzner, H., Project Management: A Systems Approach to Planning, Scheduling, and Controlling, 11th edition, Wiley, 2013 • Thamhain, H., Managing Technology-Based Projects: Tools, Techniques, People and Business Processes, Wiley, 2014. • Schwalbe, K., Information Technology Project Management, Cengage Learning, 2013. • Richardson, G., Project Management Theory and Practice, 2nd edition, Auerbach Publications, 2014. • Brewer, J. and Dittman, K., Methods of IT Project Management, 2nd edition, Prentice Hall, 2013. Journals: • International J. of Project Mgmt • MIS Quarterly • Project Management Journal • PM Network

8. Prerequisite: CIS 379 – Systems Analysis & Design Grading:

9. Notice that this scale may be different than that of other classes!

10. 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.

11. 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.

12. Homework: Numerous 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. **Note: I reserve the right to add announced or unannounced quizzes as needed to gauge and/or motivate class involvement and comprehension. These will be counted as additional homework assignments.

13. 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.

14. 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 and you will be given an opportunity to make up any in-class graded exercises that were missed; unexcused absences will cause the loss of any in-class exercise/quiz points that were missed. 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. It is the student’s responsibility to seek out the instructor and provide documentation regarding any absence – absences will be presumed to be unexcused unless the student establishes otherwise. Note that students are expected to arrive at class on time!

15. 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 after the start of the class period count as one-day late. The normal procedure is to turn in completed assignments as a hardcopy at the beginning of the class for which they are due (there may be cases when emailed assignments are preferred – these will be announced). Emailed assignments are permitted if you will miss the class for which they are due, or to submit late assignments.

16. Academic Dishonesty: The Towson University policy on academic integrity is in Appendix F of the Undergraduate Catalog and at http://www.towson.edu/studentaffairs/policies/. Academic dishonesty specifically includes acts of plagiarism, fabrication and falsification, cheating, complicity, 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.

17. 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: Sep 5: Last day to drop with no grade posted Nov 5: 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.

18. 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 lectures. 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.

19. ABSOLUTELY NO FOOD IS ALLOWED IN THIS ROOM! *Drinks are ok…clean up after yourself!

20. Day-to-day schedule Web site Initial Project Information