TU BCA Introduction to Management Master Guide: Fayol’s 14 Principles, Leadership Styles & Motivation in IT Firms
Author: Bhuban Subedi | Subject: Introduction to Management (CAMG302) | Semester: Fifth Semester
Leading successful technology organizations requires more than technical architecture expertise; it demands effective project management, organizational structuring, conflict resolution, and motivational leadership. In the Tribhuvan University BCA fifth semester, Introduction to Management (CAMG302) introduces IT professionals to management science, strategic planning, human resource dynamics, and team leadership.
In the final 60-mark TU board examination, examiners emphasize Henri Fayol’s 14 Principles of Management, The Planning Process, Maslow’s Hierarchy of Needs vs. Herzberg’s Motivation-Hygiene Theory, and Leadership Styles within modern Agile software companies.
In this guide, I will break down these core management frameworks with clear, structured explanations.
1. The 5 Fundamental Functions of Management (POSDCORB)
Management is the process of planning, organizing, leading, and controlling resources to achieve organizational goals efficiently and effectively.
[1. PLANNING] ──► [2. ORGANIZING] ──► [3. STAFFING] ──► [4. DIRECTING / LEADING] ──► [5. CONTROLLING]
▲ │
└────────────────────────── (Feedback & Adjustments) ─────────────────────────────────┘
2. Henri Fayol’s 14 Principles of Administrative Management
+---+-------------------------------+-------------------------------------------------------------------+
| # | Principle | Core Concept & Application in Tech Companies |
+---+-------------------------------+-------------------------------------------------------------------+
| 1 | **Division of Work** | Specialization increases efficiency (e.g., Frontend vs Backend). |
+---+-------------------------------+-------------------------------------------------------------------+
| 2 | **Authority & Responsibility**| Managers must possess the authority to issue orders and be held |
| | | accountable for results. |
+---+-------------------------------+-------------------------------------------------------------------+
| 3 | **Discipline** | Respecting organizational rules, sprint deadlines, and contracts.|
+---+-------------------------------+-------------------------------------------------------------------+
| 4 | **Unity of Command** | Each employee receives orders from only **one direct supervisor** |
| | | to eliminate conflicting instructions. |
+---+-------------------------------+-------------------------------------------------------------------+
| 5 | **Unity of Direction** | One team, one plan, one objective under a single project lead. |
+---+-------------------------------+-------------------------------------------------------------------+
| 6 | **Subordination of Individual | Organizational objectives supersede personal interests. |
| | Interest** | |
+---+-------------------------------+-------------------------------------------------------------------+
| 7 | **Remuneration** | Fair and equitable financial compensation for all developers. |
+---+-------------------------------+-------------------------------------------------------------------+
| 8 | **Centralization** | Balancing central executive authority with decentralized teams. |
+---+-------------------------------+-------------------------------------------------------------------+
| 9 | **Scalar Chain** | Unbroken chain of communication from C-suite to junior dev. |
| | *(Gangplank exception)* | (*Gangplank* allows direct cross-department communication). |
+---+-------------------------------+-------------------------------------------------------------------+
| 10| **Order** | Right person in the right technical role with proper tooling. |
+---+-------------------------------+-------------------------------------------------------------------+
| 11| **Equity** | Equal, fair, and kind treatment for all team members. |
+---+-------------------------------+-------------------------------------------------------------------+
| 12| **Stability of Tenure** | Minimizing employee turnover through job security and growth. |
+---+-------------------------------+-------------------------------------------------------------------+
| 13| **Initiative** | Encouraging developers to propose architectural improvements. |
+---+-------------------------------+-------------------------------------------------------------------+
| 14| **Esprit de Corps** | Fostering team unity, mutual trust, and high morale. |
+---+-------------------------------+-------------------------------------------------------------------+
3. Leadership Styles in Software Engineering Organizations
+-------------------+-----------------------------------+---------------------------------------+
| Leadership Style | Characteristics | Ideal Use Case in IT |
+-------------------+-----------------------------------+---------------------------------------+
| **Autocratic** | Leader makes unilateral decisions | Critical cybersecurity incidents, |
| *(Authoritarian)* | without consulting team members. | production server outages. |
+-------------------+-----------------------------------+---------------------------------------+
| **Democratic** | Decisions made collaboratively via| System design sprint planning, |
| *(Participative)* | developer voting and consensus. | tech-stack selection discussions. |
+-------------------+-----------------------------------+---------------------------------------+
| **Transformational**| Inspires innovation through shared| High-growth tech startups, |
| | vision and continuous mentorship. | research and development divisions. |
+-------------------+-----------------------------------+---------------------------------------+
| **Laissez-Faire** | Full autonomy given to developers | Senior research scientists, |
| *(Delegative)* | with minimal supervision. | open-source core engineering teams. |
+-------------------+-----------------------------------+---------------------------------------+
4. Theories of Employee Motivation
+-------------------------------------------------------------------------------+
| MASLOW'S HIERARCHY OF NEEDS (BOTTOM TO TOP) |
| |
| 5. Self-Actualization: Achieving full creative potential (Lead Architect role)|
| 4. Esteem Needs: Recognition, awards, bonuses, and promotions. |
| 3. Social Needs: Collaborative team culture, friendships, peer support. |
| 2. Safety Needs: Job security, health insurance, provident fund. |
| 1. Physiological Needs: Base salary, food, housing, standard working hours. |
+-------------------------------------------------------------------------------+
Herzberg’s Two-Factor (Motivation-Hygiene) Theory:
- Hygiene Factors (Prevent Dissatisfaction): Salary, company policies, workplace conditions, job security. (Their presence does not motivate, but their absence causes severe demotivation).
- Motivators (Drive High Performance): Challenging projects, personal achievement, career growth, professional recognition.
Frequently Asked Questions (FAQ)
Q1: What is Fayol’s “Gangplank” concept?
A Gangplank is a direct shortcut mechanism in the scalar chain allowing two employees at the same hierarchical level in different departments to communicate directly during urgent matters without routing through every intermediate superior.
Q2: What is SWOT Analysis in strategic management?
SWOT is a strategic planning tool evaluating internal Strengths and Weaknesses alongside external market Opportunities and Threats.
