Course ObjectiveAt the end of the course, students should be able to:
1. Apply best practices to in planning projects to ensure successful
outcomes; (Apply knowledge and understanding)
2. Understand the differences between different project management
methodologies such as waterfall and agile; (Knowledge and understanding)
3. Identify and avoid typical risks and mistakes made in managing
software projects; (Make judgements)
4. Create a software project plan using different management techniques,
including financial analysis, activity scheduling and risk management;
(Apply knowledge and understanding)
5. Appreciate the need for careful planning, monitoring and control of
software projects; (Lifelong learning skills)
6. Be able to present and evaluate project ideas. (Lifelong learning
Course ContentDuring the course, different aspects of project management are explained
in the lectures. The lectures are structured to follow a typical project
plan structure: project vision, functional scope, non-functional
requirements, effort estimation using different methods, scheduling,
communication and risk management. In each lecture project management
modern software project management practices are explained. Experts from
industry are also invited to give guest lectures.
Throughout the course, students work in groups to create their own
project plan for a
software application of their own choice. Each week they must create one
new chapter using the techniques from that week’s lecture.
Teaching MethodsTheory classes are alternated by hands-on sessions where the theory is
put into practice through individual and group assignments. The
practical sessions are not mandatory but are an opportunity for groups
and students to get their work reviewed, ask additional questions and
obtain feedback on their project plan.
The study load is 16-20 hours per week for a period of 8 weeks. Some but
not all lectures will have mandatory attendance since students must
practice presenting their project plan.
Method of AssessmentThe students will receive an overall grade based on four components:
Midterm exam (individual) = 15%
Final Exam (individual) = 45%
Software project Plan: Written Report (group assignment) = 25%
Software project Plan: Presentation (group assignment) = 15%
Literature- Software Project Management, Bob Hughes and Mike Cotterell. Mc Graw-
Hill, 2008. ISBN 978-007712279-9
- The Scrum Guide, Ken Schwaber and Jeff Sutherland. Available online
- The course lectures slides (will be made available in Canvas). The
lecture contents is also readable at the ICT Institute website:
Recommended background knowledgeBasic knowledge of requirements engineering is highly recommended.
A basic statistical background would be helpful, too.
|Language of Tuition||English|
|Faculty||Faculty of Science|
|Course Coordinator||dr. S. Lusini|
|Examiner||dr. G.C. van de Weerd|
dr. G.C. van de Weerd
You need to register for this course yourself
Last-minute registration is available for this course.
|Teaching Methods||Seminar, Lecture, Practical|
This course is also available as: