SOFTWARE PROJECT MANAGMENT

Course Syllabus

Prepared By:

GENERAL DATA

SUBJECT CODE 10681361

Credit Hours

PUBLICATION DATE

DEGREE IN WHICH IT IS
TAUGHT
CONTEXT OF THE SUBJECT

RESPONSIBLE TEACHER
Name

LIST OF TEACHERS
THEORY

PRACTICE WITH PC

COMPETENCES AND LEARNING OUTCOMES

Upon successful completion of this course, students should be able to:

LEARNING OUTCOMES
 1- Demonstrate knowledge of the key concepts and processes of software project
management
2- Explain the difference between software project management and the management
of “other” projects
3- Produce a software project plan
4- Select the appropriate software management approach
5- Estimate effort required for project completion
6- Show ability to work effectively in teams

TECHNICAL COMPETENCES
1. Abilities to make decision in software project management to plan activities, allocate
resources and manage contracts.
2. Abilities to identify risks and to perform a realistic risk assessment and include it in
the making decision process to minimize impact.
3. Motivate and document decisions that are made during the software project plan.
4. Abilities to monitor and control a software project plan.
5. Abilities to perform accurate software effort estimation by using different
techniques.
6. Understand and apply the tools needed for software project management

TRANSVERSAL COMPETENCES T
1. Acquire abilities to work effectively in a team to successfully manage a software
project
2. Acquire abilities to perform a negotiation, to exercise leadership and keep effective
work habits.
3. Acquire abilities to prepare structure and write documents and report with the right
level of formality and technical detail.
4. Acquire abilities to communicate and transmit knowledge in an oral manner.

CONTENT

GENERAL DESCRIPTION
This course introduces the various aspects related to software projects management including software
life-cycle models, software project scheduling, effort estimation, resource allocation, and risk
management. Other topics include teamwork, contracts and ethical practice. This course will include
guest speakers from industry; and authentic projects from industry are integrated in the course procedure.
Students will work on developing detailed plans for a real project. Team work skills will be crucial to
success in project implementation. This course is planned to be delivered at the final year of study. During
the course student supposed to have the experience of real word software project management. Students
is expected to be senior and have the enough knowledge about software development process and
techniques.

THEORETICAL
Theoretical contents
a) Introduction to SW project management
b) Project evaluation and management
c) Overview of project planning
d) SW effort estimation
e) Activity Planning
f) Risk Management
g) Resource Allocation
LEARNING PLAN

TEACHING METHODOLOGY FACE-TO-FACE SELF STUDY

ACTIVITY HOURS HOURS
The teaching approaches 15 weeks per semester, Each student supposed
and methods of learning 45 hours in total. 3 per to spend 2 self-study
used on the course will week. The last week hoursfor each one-hour
Theory include traditional lecturing. (No. 16) will be lecture. 6 hours per
Seminars, tutorials, general reserved to the final week.
and case studies discussion examinations.
will also be used.
Student teams will work on Each team supposed to Each studentsupposed
completing the development meet with the tutor to work practically on
of an authentic software from the private sector the assignments for
project to be provided from face-to-face at least two hours per week. In
the industry by the private one time for two hours addition of two hours
Practice with
company partner. In per week. per week on their
PC
addition, students will work projects.
on different practical
assignments to be applied on
the case studies given during
the course.
TOTAL 75 hours 150 hours

Weekly detail

*****(T)for theoretical, (P) for practical

FACE-TO- SELF
WEEK Type UNIT HOURS HOURS
FACE STUDY
Introduction to software project
1 T X 3 X 6
management

Working in teams
2 P - Private Company Guest 1: working in teams X 3 X 6
- Activity 6: Working in team training

Project evaluation and program

3 T management X 3 X 6
- Private Company Guest 2: Project selection and
evaluation in actual company setting
An overview of project planning
4 P - Activity1: project definition and developing its X 3 X 6
master plan.
Selection of an appropriate project
5 T X 3 X 6
approach
Private Company Guest 3:managing
6 P projects using agile methodology in actual company X 3 X 6
application.
6-7 T Software effort estimation X 6 X 12
7 P Private Company Guest 4:company X 4 X 8
 approaches to effort estimation.
Team assignment 1 : produce time frame for three
8 activities and compare with actual time frame from X 2 X 4
company experience
First Exam
9 T Activity planning X 3 X 6
- Activity 3: Develop a project detailed plan

10 P Risk management X 3 X 6
- Private Company Guest 5: Our risks in Palestine
Team assignment 2: management plan
11 T X 3 X 6
for risks given by company tutor
12 P Resource allocation X 2 X 4
- Activity 5: Allocating resources for the project
13 T X 3 X 6
- Lab: Project planning software

14 P Managing contracts X 2 X 4
- Private Company Guest 6: contracts and ethics
15 T - Project presentations X 3 X 6
Final Exam

EVALUATION SYSTEM

 Since this course is project/industry-based, a significant portion of the course grade will go for the project tasks, and
the industry will be part of the evaluation process. The project grade will be divided into four parts: first exam, final
exam, course project, and team assignment. Rubric for PBL assessment is attached.
 First Exam
 Final exam
 Course project
 Team assignment

Tools and Criteria for the evaluation

TYPE CRITERION DESCRIPTION WEIGHT

Midterm written exam for one and a half
CONTINOUS hour. Given in the class room and covers all
First exam 20
EVAL. the theoretical part of the course up to
week seven.
Final written exam for two hours. Given in
CONTINOUS the class room and covers all the
Final exam 30
EVAL. theoretical part of the course.
A real software project will be given to
students by company partner. The
company partner will explain important
specifications and environment issues
during weeks 1-2. The students will work in
teams and they will play the role of project
CONTINOUS
Course project managers throughout the course (activities 30
EVAL.
1 -5). The company partner will play the
role of project owner and will help in
guiding the project activities and in the
evaluation of student projects at the end of
the course.

Students will be divided into six teams with

five students in each one. Each team will
CONTINOUS Team
work on completing the development of 20
EVAL. assignment
an authentic software project to be
provided from the industry by the private
 company partner. Rubric for assessment is
attached.
TOTAL 100

BIBLIOGRAPHY

TITLE SOFTWARE PROJECT MANAGMENT

(Main Text Book)
AUTHOR(s) Robert Hughes and Mike Cotterell
EDITION Fifth Edition
ISBN ISBN-13 978-0-07-712279-9
RECOMMENDED BY -
Access to the resource

TITLE SOFTWARE PROJECT SECRETS WHY

SOFTWARE PROJECTS FAIL(Additional
Resources)
AUTHOR(s) George Stepanek
EDITION
ISBN
RECOMMENDED BY -
Access to the resource

Resources:
1. Team building exercises: http://www.mindtools.com/pages/article/newTMM_52.htm
2. IEEE Standard for Software Project Management Plans, IEEE Std 1058-1998(Revision and redesignation of
IEEE Std 1058.1-1987,incorporating IEEE Std 1058-1998 andIEEEStd 1058a-1998)
3. SOFTWARE PROJECT SECRETS WHY SOFTWARE PROJECTS FAIL, George Stepanek, Apress 2005
4. https://www.comp.glam.ac.uk/staff/dwfarthi/projman.htm
5. http://www.pmi.org/en/Certification/Project-Management-Professional-PMP.aspx (be careful it is project
management site not software project management you need to read (3) to know the differences.