UNIVERSITY OF ALBERTA School of Business
DEPARTMENT OF ACCOUNTING & MIS MIS 424
COURSE OUTLINE
Course website: http://www.business.ualberta.ca/catalogue/CourseDetails.aspx?Course=MIS424
Instructor: Mark Mullaly Term II, 2009/2010
Office: N/A Class Time & Location:
Office Hours: By Appointment Only MW 1530-1650; BUS B-5
Phone: 780.414.6391
E-mail: [email protected]
COURSE OVERVIEW:
MIS 424 – Introduction to Information Systems Project Management is designed to provide in-depth, hands-on experience in understanding project management – particularly as it applies to the process of software and information systems development – through a combination of class lectures and the conducting of a project case study.
The project case study will be conducted within project teams, which will be established by the third workshop. In an effort to be as practical and relevant as possible, students will have an opportunity to select their project case study topic from a set of defined scenarios. This will allow them to undertake a case study that best aligns with their experience and courses taken to date, and the specific interests and abilities of their team.
Students are expected to actively participate in MIS 424, in both a group projects and class lectures. Marks will be based upon both the completed project assignments, and also participation in lectures, as discussed in the Grading section, below.
The objectives of MIS 424 are to:
• Establish a clear and relevant understanding of project management, and how project management contributes to successfully delivering information systems work.
• Provide a practical opportunity to integrate the results of the theoretical learnings of individual MIS courses, and begin to apply these skills to identify, address and resolve project problems and challenges.
• Provide students with an opportunity to apply these skills in conducting a project case study that is based upon a specific, real-world problem.
COURSE PRE-REQUISITES
Students are expected to have successfully completed MIS 311.
COURSE MATERIALS:
The text book for this course is Project Management, 3rd Edition by Harvey Maylor.
Additional handouts will be provided by the instructor during classes to illustrate points and topics being discussed.
COURSE FORMAT:
Lectures will be a combination of formal presentations, case studies and group discussions. The lectures will establish the framework and expectations for the course, provide the introductory information necessary to be able to manage a project successfully, and build on these basics to be able to successfully deliver the team’s project. Later classes will also allow project teams to present interim deliverables from their project case studies, as well as provide updates of project status.
While there is no scheduled lab time for the course, completion of the project case study is intended to be a significant proportion of time invested by each student, and will serve as the greatest contribution to the final grade.
The instructor is available on an as-requested basis to consult regarding specific challenges or questions.
INDIVIDUAL OBJECTIVES:
The first assignment of the course is a brief paper providing an overview of your objectives in taking the course. The individual objectives are due at the end of the third class, on 13 January 2010.
GROUP PROJECTS:
The project case studies will be based upon the expertise and desired direction of the student groups. Group participation is mandatory; teams for each project will consist of at least three, and typically no more than six, students. Individual projects are not permitted.
Student teams will be formed by the fourth lecture.
It is the responsibility of each student team to identify and prioritize the projects that they wish to conduct, based upon the case studies provided by the instructor.
The first deliverable of each project will be a project plan, in the format provided by the instructor, which will outline the objectives, scope, deliverables, resource requirements, assumptions and constraints of the project. The project plan is due no later than 5:00pm MST on 22 February 2010.
The second deliverable of each project will be the deliverables of the project, based upon what has been identified that the project team will produce in the project plan. The deliverables of the project are due no later than 5:00pm MDT on 12 April 2010.
The final deliverable of each project will be a group project review, in the format provided by the
instructor, which will evaluate the successes, challenges and lessons learned by the team in conducting the project. The project review report is due no later than 5:00pm MDT on 12 April 2010.
PEER ASSESSMENTS:
A component of the grade will be based upon peer assessments, which will be completed by each student for each of the other participants on their team. Peer assessments will be completed using the forms provided by the instructor, and are due by 5:00pm MDT on 19 April 2010.
INDIVIDUAL REPORTS:
In addition to completing the project and the required deliverables, as identified in the Grading section, below, students are expected to complete an individual report, which is due and must be received by no later than 5:00pm MDT on 19 April 2010.
FINAL EXAMINATION:
There will be no final examination for MIS 424.
GRADING SCHEME:
The following criteria will be used in preparing the final grade:
Group Deliverables
• Project Plan (Deadline: 5:00pm MST on 22 February 2010) 15%
• Project Deliverables (as identified in the project plan) 25%
• Final Project Review Report (Deadline: 5:00pm MDT on 12 April 2010) 20%
Individual Deliverables
• Individual Objectives (Deadline: end of class on 13 January 2010) 5%
• Class Participation 10%
• Peer Assessment (Deadline: 5:00pm MDT on 19 April 2010) 10%
• Individual Report (Deadline: 5:00pm MDT on 19 April 2010) 15%
All assignments are to be completed by their deadlines. Late assignments will lose 5% per day for each day past the deadline.
Final grades will be determined based upon the results for both group and individual assignments, using roughly the following schedule:
Overall % Grade
95-100 % A+
90-100% A
85%-89% A-
80%-84% B+
70%-79% B
60%-69% B-
50%-59% C+
ACADEMIC INTEGRITY:
The University of Alberta is committed to the highest standards of academic integrity and honesty.
Students are expected to be familiar with these standards regarding academic honesty and to uphold the policies of the University in this respect. Students are particularly urged to familiarize themselves with the provisions of the Code of Student Behavior (online at avoid any behavior which could potentially result in suspicions of cheating, plagiarism, misrepresentation of facts and/or participation in an offence. Academic dishonesty is a serious offence and can result in suspension or expulsion from the University.
Policy about course outlines can be found in LECTURE SCHEDULE:
The following table summarizes the schedule for class lectures:
# Date Topic
1 2009/01/06 Introductions
Syllabus Review 2 2009/01/11 Definition of a project
Defining project management
Relating project management & software development Chapter 1 – p. 1-17
3 2009/01/13 Project structures and frameworks Understanding project complexity Chapter 2 – p. 23-39
4 2009/01/18 Project Team Structures Chapter 9– p. 220-230
*Project teams formed 5 2009/01/20 Impacts of personality
Managing the team Chapter – p. 232-242
6 2009/01/25 Stakeholders & Customer Definition Defining Project Requirements Chapter 3 – p. 50-55; 60-67
7 2009/01/27 Defining Project Scope
Driving Priorities
Assumptions & Constraints Chapter 4 – p. 76-88
8 2009/02/01 Defining Work
Work Breakdown Structures
Deliverables
Milestones Chapter 4 – p. 88-99
9 2009/02/03 Estimation
Standard Day
Estimating Effort
Validating Estimates Chapter 6 – p.135-148
10 2009/02/08 Project Budgetting
Chapter 7 – p. 154-166 11 2009/02/10 Developing Project Plans
Change & Contingency Budget Presenting Estimates
Chapter 8 – p. 179-190 2009/02/15-19 Reading Week – No Lectures 12 2009/02/22 Impacts of Methodologies
Waterfall
Iterative
Agile
*Assignment 1 Due - Project Plan
13 2009/02/24 Effort Tracking
Schedule Tracking Budget Tracking Chapter 11 – p. 271-286
14 2009/03/01 Status Reporting
Status Meetings
Status Reports
15 2009/03/03 Managing Risk
Chapter 8 – p. 191-204
16 2009/03/08 Managing Quality
Walkthroughs
Deliverable Acceptance
Defect Tracking Chapter 13 – p. 318-335
17 2009/03/10 Scheduling Tools I
Using Microsoft Project Chapter 5 – p.104-124
18 2009/03/15 Scheduling Tools II
Case Study using Microsoft Project
19 2009/03/17 Scheduling Tools III
Review of Microsoft Project Case Study 20 2009/03/22 Management & leadership in project environments
Chapter 10 – p. 245-267
21 2009/03/24 Project Close-out
Post Implementation Review Chapter 14 – p.344-361 22 2009/03/29 Improving Project Performance
Chapter 15 – p. 371-385 23 2009/03/31 Project Presentations 1
2009/04/05 *** Easter Monday – No Lecture ***
24 2009/04/07 Project Presentations 2 25 2009/04/12 Planning For Next Time
*Assignment 2 Due – Group Report 2009/04/19 *Assignment 3 Due – Individual Report
