Applied Science University
Faculty: Information Technology
Department : Software Engineering
( Course Syllabus )
CourseTitle
Project Management
Coordinator Name
Dr. Aiman Turani
Credit Hours
3
Course No.
1302383
Lecturer
Dr. Aiman Turani & Dr
Marwan Elsaed
Prerequisite
1302281
Room No.
1224
Year (semester)
2011-2012 (2)
E-mail
aimant@asu.edu.jo
Mode of study
Lecture: 2 hs.
Lab : 2 hs.
Office Hours
Posted on the door
Course Objectives:
The Project Management Course objective is to address issues involving the creation, development and
maintenance of software Projects. This area includes team and project management, project planning, project
schedules and cost estimation models, risk analysis, project a divines tat on and configuration Management.
Course Description:
This course aims at introducing the major topics in project management. It seeks to explain the
basic principles and provide practical steps for managing projects. It also seeks to expose
students to a spectrum of activities involved in project management with a specific focus on IT
projects. Further, students are also expected to understand and demonstrate knowledge of managing
group projects and of project presentation. This course will cover the following topics: Overview
of project management; Understanding the nature of projects; Principles and basic techniques of
project management; Project management tools; Integration of tools and principles; Setting up a
project; Project stages; Planning and controlling a project; Role and personal qualities of a project
manager.
Intended Learning Outcomes :
Successful completion of this course should lead to the following learning outcomes :
A- Knowledge and Understanding :
A1) Understand the need for the software project management.
A2) Understand the five software project management phases.
A3) Understand the nine PM knowledge areas based on the PMI classification.
A4) Understand the role of each of the software project management phases.
A5) Understand the inputs and the outputs of each of the software project management phases.
A6) Understand how to select a potential software project based on a set of methods.
B- Intellectual Skills:
B1) Distinguish the differences between the five software project phases.
B2) Distinguish the differences between the nine PM knowledge areas.
B3) Build a set of SPM documentations, such as, project charter, business case, and project
management plan.
C) Subject Specific Skills:
C1) Using MS project 2003 to manage the software projects.
C2) Develop the Gantt chart, network diagram, and WBS for the software projects.
C3) Estimate the NPV, ROI and payback year for the potential software projects
1
D) Transferable Skills:
D1) Discuss and work in a group of 2-4 students in order to select and manage a project in order to
produce a set of project management deliverables
Course Contents :
Week
Topics
Topic Details



1.
Introduction of
generic project
management
concepts





2.
Introduction of
generic project
management
concepts




3.
4.
5.
6.
7.
Reference
(chapter)
WHAT IS A PROJECT?
CHARACTERISTICS OF
PROJECTS
The Project Management Life Cycle
WHY DO SOME PROJECTS
FAIL?
PROJECT’S LIFE CYCLE
Chapter1-(Ref
PROJECT PHASES
no 1)
PROJECT MANAGER ROLE
TEAM LEADER
PROJECT TEAM
COMMUNICATION
COORDINATION
PROJECT PORTFOLIO
MANAGEMENT
PROGRAMME MANAGEMENT
Chapter1-(Ref
no 1)
Setting Up for
Success


SELECTING THE APPROPRIATE
PROJECT
THE BUSINESS CASE
Chapter 1 & 2COST BENEFIT ANALYSIS
(Ref no 1
Software Effort
Estimation




Software Effort Estimation
A taxonomy of estimating methods
Sizing the project
Function Points



Effort Estimation Models
COCOMO
COCOMO II






Project planning and Scheduling
techniques
Defining activities
Work Break Down Structure WBS
Scheduling
PERT/CPM
Critical Path



Uncertain Activity Times
Gantt Charts
Microsoft Pro
Effort Estimation
Part 2
Project Planning
and Scheduling
Project
Scheduling
2
Chapter5-(Ref
no 1
Chapter5-(Ref
no 1- Fuller
Assessment
Pioneering and
demonstrating the
way we will follow
in order to
accomplish the
course objectives
(emphasizing on
team work projects
and written
assignments
distributed over the
academic semester)
Pioneering and
demonstrating the
way we will follow
in order to
accomplish the
course objectives
(emphasizing on
team work projects
and written
assignments
distributed over the
academic semester)
Getting started with
Microsoft Project
(MS project 2003) as
a tool for managing
IT projects (stage 1)
(Stage 2) of MS
project 2003
supported by a task
given to students in
the lab time
(Stage 3) of MS
project 2003
supported by a task
given to students in
the lab time
Chapter6-(Ref
no 1
(Stage 3) of MS
project 2003
supported by a task
given to students in
the lab time
Chapter 6 (Ref
no 1)
(Stage 4) project
team management
activity using MS
8.
9.
10.
Resource
allocation
Project
Controlling
Risk
Management
















11.
12.
13.
14.
15.
16.
Configuration
Management
Project Quality
Management
Project Quality
Management










project 2003
supported by a task
given to students in
the lab time
Resource allocation
(Stage 5) project time
Resource histogram
management activity
Resource smoothing
Chapter 8 -(Ref using MS project
Resource clashes
no 1)
2003 supported by a
Prioritizing activities
Allocating individuals to activities
task given to students
Cost schedules
in the lab time
The control cycle
(Stage 4) project
Cost monitoring
team management
Estimate at Complete
activity using MS
Chapter 9 (Ref
project 2003
no 1)
supported by a task
given to students in
the lab time
definitions of risk
(Stage 5) project time
Categories of risk
management activity
framework for dealing with risk
Chapter
7
(Ref
using MS project
Plan for risks
no 1)
2003 supported by a
Risk reduction leverage
task given to students
in the lab time
Software Configuration
(Stage 6) project
Management Process
resources and
Change control
allocation activity
Software Configuration
Chapter 9 (Ref
using MS project
Management Process
no 1)
2003 supported by a
task given to students
in the lab time
The importance of software quality
Finishing up the
Types of quality assessment
team-based project
Software Quality Process
Chapter 9 (Ref
using MS project
Quality Measurement
no 1)
2003 and other tools
if needed (stage 1)
Software Quality Function
Finishing up the
‘Clean-room’ software development
team-based project
Testing: the V-process model
Chapter 9 -(Ref
using MS project
no 1 Fuller)
2003 and other tools
if needed (stage 2)
Review lectures
for the Final
Exam Due Date
to submit your
team-based
project for
evaluation
Review lectures
for the Final
Exam Due Date
to submit your
team-based
project for
evaluation
Finishing up the
team-based project
using MS project
2003 and other tools
if needed (stage 2)
Finishing up the
team-based project
using MS project
2003 and other tools
if needed (stage 2)
FINAL
EXAMINATION
Course quality improvement :
3
W EE K


From the market and new subjects in the field.
From the monitoring of students feedback (Evaluation sheet).
Grade Distribution :
Assessment
Grade
Date
- First Exam
20%
TBD
- Second Exam
20%
TBD
- Assignments (reports, quizzes, homeworks, participation, conduct)
20%
TBD
- Final Examination
40%
TBD
* Make-up exams will be offered for valid reasons. It may be different from regular exams in content and format.
Reading List:
Text Book
1. Software Project Management, Bob Hughes and Mike Cotterell, Fifth Edition, McGraw
Hill, 2009
Other
References
2. Project Management: A Systems Approach to Planning, Scheduling
And Controlling/9th E;
Harold Kerzner, John Wiley and sons, 2003.
3. Project Management: Best Practices for IT professionals
Richard Murch; Prentice-Hall, 2001.
Last updated on 20/2/2011 by Dr. Aiman Turani
4