BBS674 - INFORMATION SYSTEMS PROJECT MANAGEMENT
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| INFORMATION SYSTEMS PROJECT MANAGEMENT | BBS674 | Any Semester/Year | 3 | 0 | 3 | 6 |
| Prequisites | - | |||||
| Course language | Turkish | |||||
| Course type | Elective | |||||
| Mode of Delivery | Face-to-Face | |||||
| Learning and teaching strategies | Lecture Discussion Question and Answer Preparing and/or Presenting Reports Project Design/Management | |||||
| Instructor (s) | Dr. Ebru Yüksel | |||||
| Course objective | To give information on project life cycle and project phases To present applications of project management methodology in information systems To give information on project time management To give information on project resource planning To give information on project budgeting To introduce computer programs used for project management | |||||
| Learning outcomes |
| |||||
| Course Content | Project definition and project phases Project organization structures Work breakdown structure Project time planning Project resource planning Project budget Project risk analysis Project evaluation and project closure | |||||
| References | Shtub, A., Bard, J.F., Globerson, S. 2005. Project Management: Processes, Methodologies, and Economics, 2nd ed., Prentice Hall. Kerzner, H. 2009. Project Management: A Systems Approach to Planning, Scheduling, and Controlling, 10th ed., Wiley. Sommerville, I., 2011. Software Engineering, 9th ed., Addison-Wesley. | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | Project life cycle and project phases |
| Week 2 | Project organization, strategy, structure |
| Week 3 | Project selection and portfolio management |
| Week 4 | Project tasks and work breakdown structure |
| Week 5 | Cost estimation and budgeting |
| Week 6 | Midterm exam |
| Week 7 | Project scheduling: Networks, duration, critical path |
| Week 8 | Project scheduling: Lagging, crashing |
| Week 9 | Resource scheduling and management |
| Week 10 | Project evaluation and control |
| Week 11 | Presentation |
| Week 12 | Earned value analysis |
| Week 13 | Managing project risk, project closeout and termination |
| Week 14 | Project presentations |
| Week 15 | |
| Week 16 | Final exam |
Assesment methods
| Course activities | Number | Percentage |
|---|---|---|
| Attendance | 0 | 0 |
| Laboratory | 0 | 0 |
| Application | 0 | 0 |
| Field activities | 0 | 0 |
| Specific practical training | 0 | 0 |
| Assignments | 0 | 0 |
| Presentation | 1 | 20 |
| Project | 1 | 20 |
| Seminar | 0 | 0 |
| Midterms | 1 | 20 |
| Final exam | 1 | 40 |
| Total | 100 | |
| Percentage of semester activities contributing grade succes | 3 | 60 |
| Percentage of final exam contributing grade succes | 1 | 40 |
| Total | 100 | |
WORKLOAD AND ECTS CALCULATION
| Activities | Number | Duration (hour) | Total Work Load |
|---|---|---|---|
| Course Duration (x14) | 14 | 3 | 42 |
| Laboratory | 0 | 0 | 0 |
| Application | 0 | 0 | 0 |
| Specific practical training | 0 | 0 | 0 |
| Field activities | 0 | 0 | 0 |
| Study Hours Out of Class (Preliminary work, reinforcement, ect) | 13 | 5 | 65 |
| Presentation / Seminar Preparation | 1 | 15 | 15 |
| Project | 1 | 30 | 30 |
| Homework assignment | 0 | 0 | 0 |
| Midterms (Study duration) | 1 | 10 | 10 |
| Final Exam (Study duration) | 1 | 15 | 15 |
| Total Workload | 31 | 78 | 177 |
Matrix Of The Course Learning Outcomes Versus Program Outcomes
| D.9. Key Learning Outcomes | Contrubition level* | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1. Has detailed knowledge about Information Systems (IS). | X | ||||
| 2. Understands the interaction of theory and practice and the links between them. | X | ||||
| 3. Has a good understanding of common concepts such as abstraction, complexity, security, concurrency, software lifecycle and applies their expertise to the effective design, development and management of IS. | X | ||||
| 4. Has the ability to think at different levels of abstraction and detail; understands that an IS can be considered in different contexts, going beyond narrowly identifying implementation issues. | X | ||||
| 5. Solves any technical or scientific problem independently and presents the best possible solution; has the communication skills to clearly explain the completeness and assumptions of their solution. | X | ||||
| 6. Completes a project on a larger scale than an ordinary course project in order to acquire the skills necessary to work efficiently in a team. | X | ||||
| 7. Recognises that the field of informatics is rapidly evolving. Follows the latest developments, learns and develops skills throughout their career. | X | ||||
| 8. Recognises the social, legal, ethical and cultural issues related to informatics practice and conduct professional activities in accordance with these issues. | X | ||||
| 9. Can make oral presentations in English and Turkish to different audiences face-to-face, in writing or electronically. | X | ||||
| 10. Recognises that informatics has a wide range of applications and opportunities. | X | ||||
| 11. Is aware that informatics interacts with different fields, can communicate with experts from different fields and can learn necessary field knowledge from them. | X | ||||
| 12. Define a research problem and use scientific methods to solve it. | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest