Week |
Subject |
Related Preparation |
1) |
"Agile project management Fundemantels / Orientation: • Agile project management histyory
• Agile manifesto
• Entrance to diferent types of agile project management types"
|
|
2) |
"ASD (Adaptive Software Developement), RUP (Rational Unified Process), DSDM (Dynamic System Development Method) : • Process
• Roles and responsabilities
• Practices
• Adoption and experiences"
|
|
3) |
"XP (Extreme Programming), CFM (Crystal Family of Methodologies), FDD, TDD (Feature and Test Driven Development): • Process
• Roles and responsabilities
• Practices
• Adoption and experiences"
|
|
4) |
"Open Source Software Development: • Getting started
• Technical Infrastructure
• Social and political infrastructure
• Communicaiton and conflict amangement"
|
|
5) |
"Open Source Software Development: • Packaging and release maangement
• Managing volunteers
• Licenses, patent and copyrights
• Budgeting"
|
|
6) |
"Kanban: • Process
• Roles and responsabilities
• Practices
• Adoption and experiences"
|
|
7) |
"Scrum: • Team Structure
• Team working
• Product backlog management
• Sprint execution"
|
|
8) |
Midterm
|
|
9) |
"Scrum: • Planning and meetings
• Quality
• Change management"
|
|
10) |
"Scaling agile: • Scaling agile manifesto
• Lean thinking and lean leadership"
|
|
11) |
"Agile Release Management
• Release train structure
• Roles and responsibilities"
|
|
12) |
"Agile release management • Release planning
• Vision, mission and roadmap"
|
|
13) |
"Agile release management
• Sprint execution
• Program Increment execution"
|
|
14) |
"Portfolio management:
• Strategic theme
• Budgeting and forecasting"
|
|
|
Program Outcomes |
Level of Contribution |
1) |
Be able to specify functional and non-functional attributes of software projects, processes and products. |
|
2) |
Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. |
|
3) |
Be able to develop a complex software system with in terms of code development, verification, testing and debugging. |
|
4) |
Be able to verify software by testing its program behavior through expected results for a complex engineering problem. |
|
5) |
Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. |
|
6) |
Be able to monitor and control changes in the complex software system, to integrate the software with other systems, and to plan and manage new releases systematically. |
|
7) |
Be able to identify, evaluate, measure, manage and apply complex software system life cycle processes in software development by working within and interdisciplinary teams. |
|
8) |
Be able to use various tools and methods to collect software requirements, design, develop, test and maintain software under realistic constraints and conditions in complex engineering problems. |
|
9) |
Be able to define basic quality metrics, apply software life cycle processes, measure software quality, identify quality model characteristics, apply standards and be able to use them to analyze, design, develop, verify and test complex software system. |
|
10) |
Be able to gain technical information about other disciplines such as sustainable development that have common boundaries with software engineering such as mathematics, science, computer engineering, industrial engineering, systems engineering, economics, management and be able to create innovative ideas in entrepreneurship activities. |
|
11) |
Be able to grasp software engineering culture and concept of ethics and have the basic information of applying them in the software engineering and learn and successfully apply necessary technical skills through professional life. |
|
12) |
Be able to write active reports using foreign languages and Turkish, understand written reports, prepare design and production reports, make effective presentations, give clear and understandable instructions. |
|
13) |
Be able to have knowledge about the effects of engineering applications on health, environment and security in universal and societal dimensions and the problems of engineering in the era and the legal consequences of engineering solutions. |
|