IE 372 | Course Introduction and Application Information

Course Name
Project Management
Code
Semester
Theory
(hour/week)
Application/Lab
(hour/week)
Local Credits
ECTS
IE 372
Fall/Spring
3
0
3
5

Prerequisites
None
Course Language
English
Course Type
Elective
Course Level
First Cycle
Course Coordinator
Course Lecturer(s)
Assistant(s) -
Course Objectives The purpose of this course is to present the basic principles that underlie the successful application of project management applications and to give managerial perspective to the students.
Course Description The students who succeeded in this course;
  • apply modern project management techniques
  • plan a project
  • schedule a project by collecting numerical data about the stages of the project
  • monitor whether the project continues according to the plan in terms of schedule, budget and management
  • apply the project management and scheduling techniques on a practical problem
Course Content This course covers topics related with IE372 and ISE 380

 



Course Category

Core Courses
Major Area Courses
Supportive Courses
Media and Management Skills Courses
Transferable Skill Courses

 

WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES

Week Subjects Related Preparation
1 Introducing to Projects and Project Management Concept Case(s) and formative presentations
2 Selecting projects strategically Case(s) and formative presentations
3 The role of the project manager. Case(s) and formative presentations
4 The role of projects in the organization. Planning the work activities. Case(s) and formative presentations
5 Project costs and budgets Case(s) and formative presentations
6 Project activity scheduling Case(s) and formative presentations
7 Project activity scheduling Case(s) and formative presentations
8 Midterm
9 Allocating resources to the project Case(s) and formative presentations
10 MS Project Case(s) and formative presentations
11 Information requirements for the project. Case(s) and formative presentations
12 Evaluating and Completing the project. Case(s) and formative presentations
13 STUDENT SUMMATIVE PRESENTATIONS:
14 STUDENT SUMMATIVE PRESENTATIONS:
15 Review of the Semester  
16 Review of the Semester  

 

Course Notes/Textbooks Jack R. Meredith, Samuel J. Mantel, Project Management A Managerial Approach, Seventh Edition, Wiley. Instructor notes and lecture slides.
Suggested Readings/Materials Shtub, A., Bard J.F., and Globerson, S. 1994. Project Management: Engineering, Technology and Implementation, Prentice Hall Maylor, H. 2001. Project Management, Prentice Hall Nicholas, J.M., 2000. Project Management: A Managerial Approach, Wiley

 

EVALUATION SYSTEM

Semester Activities Number Weigthing
Participation
10
40
Laboratory / Application
Field Work
Quizzes / Studio Critiques
Homework / Assignments
Presentation / Jury
1
35
Project
Seminar / Workshop
Oral Exams
Midterm
1
25
Final Exam
Total

Weighting of Semester Activities on the Final Grade
100
Weighting of End-of-Semester Activities on the Final Grade
Total

ECTS / WORKLOAD TABLE

Semester Activities Number Duration (Hours) Workload
Theoretical Course Hours
(Including exam week: 16 x total hours)
16
3
48
Laboratory / Application Hours
(Including exam week: 16 x total hours)
16
Study Hours Out of Class
Field Work
Quizzes / Studio Critiques
Homework / Assignments
Presentation / Jury
1
27
Project
Seminar / Workshop
Oral Exam
Midterms
1
30
Final Exam
    Total
105

 

COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP

#
Program Competencies/Outcomes
* Contribution Level
1
2
3
4
5
1

To have adequate knowledge in Mathematics, Science, Computer Science and Software Engineering; to be able to use theoretical and applied information in these areas on complex engineering problems.

2

To be able to identify, define, formulate, and solve complex Software Engineering problems; to be able to select and apply proper analysis and modeling methods for this purpose.

3

To be able to design, implement, verify, validate, document, measure and maintain a complex software system, process, or product under realistic constraints and conditions, in such a way as to meet the requirements; ability to apply modern methods for this purpose.

4

To be able to devise, select, and use modern techniques and tools needed for analysis and solution of complex problems in software engineering applications; to be able to use information technologies effectively.

5

To be able to design and conduct experiments, gather data, analyze and interpret results for investigating complex Software Engineering problems.

6

To be able to work effectively in Software Engineering disciplinary and multi-disciplinary teams; to be able to work individually.

7

To be able to communicate effectively in Turkish, both orally and in writing; to be able to author and comprehend written reports, to be able to prepare design and implementation reports, to be able to present effectively, to be able to give and receive clear and comprehensible instructions.

8

To have knowledge about global and social impact of engineering practices and software applications on health, environment, and safety; to have knowledge about contemporary issues as they pertain to engineering; to be aware of the legal ramifications of Engineering and Software Engineering solutions.

9

To be aware of ethical behavior, professional and ethical responsibility; to have knowledge about standards utilized in engineering applications.

10

To have knowledge about industrial practices such as project management, risk management, and change management; to have awareness of entrepreneurship and innovation; to have knowledge about sustainable development.

11

To be able to collect data in the area of Software Engineering, and to be able to communicate with colleagues in a foreign language.

12

To be able to speak a second foreign language at a medium level of fluency efficiently.

13

To recognize the need for lifelong learning; to be able to access information, to be able to stay current with developments in science and technology; to be able to relate the knowledge accumulated throughout the human history to Software Engineering.

*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest