About

The Field Manual

From the Prologue of the The Field Manual of MIS1:

In The Field Manual for the Members of the Department of Management Information Systems, reader can find various subjects which are related to departmental strategy and viewpoints, intrinsic workflows and approaches, implicit rules and regulations, current functions and actions.

1 The Field Manual of MIS is a manifesto/operations manual for Department of Management Information Systems, it is not a lexicon for the term of scientific field of MIS.

View Online

Download your copy

Approach

Our administration approach is based on the concepts declared below to get works done!

  • Open. Open relationships between agents and parties.
  • Free. Freedom of thought and speech in all processes.
  • Proactive. Getting work done proactively.
  • Creative. Making things as we dream.
  • Responsible and Accountable. Awareness of responsibilities of actions and obligations to report, explain, or justify processes.

Continuous Improvement

  • We are observing: Keeping eyes open for processes to improve.
  • We are listening: Getting feedback from you, in any case.
  • We are taking action: Put something forward, obsessively.

Chair's Office

We have a virtual chair office with an actual chair.

Chair - H. Kemal Ilter, Ph.D.

info@mis.academy

Administrative Office

Department of Management Information Systems has no administrative office, we are communicating in the way of nature. Through smoke signals? Uhm, no.

Secretariat - Yusuf Akkaya

mis@ybu.edu.tr

Department Board

Department related issues are discussed in the Department Board Meeting which is holding one per month. Faculty members have rights to vote on decisions while we are seeking a consensus.

info@mis.academy

Issue Tracking

Send an issue

ID DescriptionAssigned toStatus
ID DescriptionAssigned toStatus
3ECTS credit changing for MIS 209, from 4 to 5B1Closed
2ECTS credit changing for MIS 203, from 6 to 5B1Closed
1Prerequisite relationship between ECON 101 and ECON 102B1Open

Key

Open - an issue is created. Nobody has started working on it so it’s kind of a backlog.
Started - a developer started his work on this task/issue. In kanban terms started tasks/issues fit into the In-Progress category.
Untested - it’s an optional status to show that issue seems to be fixed but needs some Q&A.
Closed - the issue is resolved (or task is complete).
Blocked - it’s a special status that shows that work on the issue/task is not possible at the moment by any reasons.