Management Science covers how organisations are run: the principles of management, how operations and people are managed, and the quantitative tools (operations research) used for decisions. It is a gentle subject for engineers, but it is directly relevant to anyone who leads a team, runs a service or has to explain a technical choice to a business audience. This article revisits the five units of the JNTUK course.
Unit 1: Introduction to management and organisation
What management is
Management is the process of getting things done through people by planning, organising, staffing, directing and controlling resources to meet goals. Managers work at three levels:
| Level | Focus | Example |
|---|---|---|
| Top | Strategy, direction | CEO, CTO |
| Middle | Turning strategy into plans | Department head, engineering manager |
| First-line (supervisory) | Day-to-day work | Team lead |
Managerial skills (Katz): technical, human and conceptual; the mix shifts from technical to conceptual as managers move up. Mintzberg described managerial roles: interpersonal (figurehead, leader, liaison), informational (monitor, disseminator, spokesperson) and decisional (entrepreneur, disturbance handler, resource allocator, negotiator).
Schools of management thought
| Approach | Contributor | Key idea |
|---|---|---|
| Scientific management | F. W. Taylor | Study work scientifically; standard methods; pay for output |
| Administrative / classical | Henri Fayol | 14 principles (unity of command, division of work, scalar chain, etc.) and five functions |
| Bureaucracy | Max Weber | Rules, hierarchy, impersonal authority |
| Human relations | Elton Mayo | Hawthorne studies: social factors and attention affect productivity |
| Behavioural | Maslow, Herzberg, McGregor | Motivation and human needs |
| Systems and contingency | An organisation is a system; the best approach depends on the situation | |
| Modern | Drucker, Peters, Senge | Management by objectives, excellence, the learning organisation |
Organisation structures
| Structure | Description | Suits |
|---|---|---|
| Line | Direct chain of command | Small firms |
| Line and staff | Line managers plus specialist advisers | Larger firms |
| Functional | Grouped by function (engineering, sales) | Stable, specialised work |
| Divisional | By product or region | Diverse businesses |
| Matrix | Staff report to both a function and a project | Project-based work; risks confusion |
| Flat, team-based, network and virtual | Few layers, cross-functional or distributed | Agile and remote organisations |
Related concepts: span of control, delegation, centralisation vs decentralisation, and formal versus informal organisation.
Today: engineering organisations use functional, product-aligned or platform-team structures, and Agile teams are cross-functional “pods”. The Hawthorne effect (people work differently when observed) is worth remembering when introducing new metrics. Mintzberg’s roles describe what a tech lead actually does.
Unit 2: Operations and quality management
Operations management
Operations management designs and runs the systems that produce goods or services. Decisions: capacity, location, layout, process choice, scheduling, inventory and quality.
| Topic | Key ideas |
|---|---|
| Plant location and layout | Factors: raw materials, labour, market, transport, cost. Layouts: product, process, fixed-position, cellular |
| Work study | Method study (find the best way) and work measurement (set time standards); ergonomics |
| Production planning and control | Forecasting, aggregate planning, MRP, scheduling |
| Inventory management | Hold stock to avoid shortages, but stock costs money |
Economic order quantity (EOQ)
The EOQ minimises the sum of ordering cost and holding cost:
EOQ = √(2 D S / H)
where D is annual demand, S the cost per order and H the holding cost per unit per year. Example: D = 1,200 units, S = ₹300, H = ₹6 gives √(2 × 1200 × 300 / 6) = √120,000 ≈ 346 units per order. Related: ABC analysis (A items are few and valuable, so control tightly), reorder level, safety stock and just-in-time (JIT).
Quality management
| Concept | Meaning |
|---|---|
| Quality control and assurance | Inspection of output; building quality into the process |
| Statistical process control (SPC) | Control charts show whether a process is in control |
| Acceptance sampling | Decide on a lot by testing a sample |
| Total Quality Management (TQM) | Everyone is responsible for quality; customer focus, continuous improvement, Kaizen, PDCA (plan-do-check-act) |
| Six Sigma | Reduce defects to 3.4 per million using DMAIC (define, measure, analyse, improve, control) |
| ISO 9000 series | Quality management standards |
| Lean | Remove waste (muda): waiting, overproduction, defects and so on |
Today: the ideas moved straight into software operations. Lean’s “waste” is idle pull requests and slow deployments, Kanban comes from the Toyota production system, control charts are the basis of anomaly alerts on metrics, and PDCA is the incident-review loop. EOQ’s trade-off between ordering and holding cost is the same one as reserved capacity vs on-demand.
Unit 3: Human resource management and organisational behaviour
HRM functions
| Function | Activities |
|---|---|
| Human resource planning | Forecast the people needed |
| Recruitment and selection | Sources, interviews, tests, hiring |
| Training and development | Skills, careers, succession |
| Performance appraisal | Rating methods, 360-degree feedback, management by objectives (MBO), OKRs |
| Compensation and benefits | Pay structure, incentives |
| Employee relations | Grievances, discipline, labour laws, trade unions |
Motivation
| Theory | Idea |
|---|---|
| Maslow’s hierarchy | Physiological, safety, social, esteem, self-actualisation; higher needs matter once lower ones are met |
| Herzberg’s two-factor | Hygiene factors (pay, conditions) prevent dissatisfaction; motivators (achievement, recognition, growth) create satisfaction |
| McGregor’s Theory X and Y | Assuming people dislike work (control) or enjoy it (empower) |
| Vroom’s expectancy | Effort depends on belief that effort leads to performance, and performance to a valued reward |
| Adams’s equity theory | People compare their rewards with those of others |
Leadership and group behaviour
Leadership styles: autocratic, democratic, laissez-faire; transformational and transactional; situational leadership (Hersey-Blanchard). Group behaviour covers team building, group dynamics, conflict and negotiation, communication (formal, informal, barriers), organisational culture and change management (Lewin’s unfreeze-change-refreeze; resistance to change).
Today: Herzberg’s idea explains why a raise alone does not stop good engineers from leaving if the work is dull or they get no growth. Performance reviews, OKRs, onboarding, career ladders and blameless culture are HR and organisational behaviour in the engineering world.
Unit 4: Operations research and decision techniques
Operations research (OR) applies mathematical models to find the best decision under constraints.
Linear programming (LP)
An LP maximises or minimises a linear objective function subject to linear constraints and non-negativity.
Example: a team ships product A (profit ₹40) and B (profit ₹30). Each A needs 2 hours of development and each B needs 1 hour; 100 hours are available, and at most 40 units of A can be shipped. Maximise 40A + 30B subject to 2A + B ≤ 100, A ≤ 40, A, B ≥ 0. The best corner point is A = 0, B = 100 giving 3,000, versus A = 40, B = 20 giving 2,200, so B only is best.
| Method | Idea |
|---|---|
| Graphical | Draw the feasible region; the optimum is at a corner point (two variables) |
| Simplex | Move from corner to corner along edges, improving each time; uses slack variables |
| Duality and sensitivity analysis | Shadow prices: the value of one more unit of a resource |
Transportation and assignment
| Problem | Goal | Methods |
|---|---|---|
| Transportation | Ship goods from sources to destinations at minimum cost | Initial solution by North-West corner, least cost or Vogel’s approximation; optimise by MODI (u-v) |
| Assignment | Match n workers to n jobs at minimum cost | Hungarian method |
Queueing, inventory and simulation
- Queueing theory: M/M/1 queue with arrival rate λ and service rate μ; utilisation ρ = λ/μ; average number in the system ρ / (1 − ρ); average time in the system 1 / (μ − λ).
- Game theory: two-person zero-sum games, saddle point, mixed strategies.
- Decision theory: decision trees, payoff tables, criteria under uncertainty (maximax, maximin, minimax regret, expected monetary value).
- Sequencing: scheduling jobs on machines (Johnson’s rule).
- Replacement analysis, simulation (Monte Carlo).
Today: LP and its relatives solve cloud cost optimisation, capacity planning, bin-packing of pods onto nodes and delivery routing. The queueing result explains why latency rises steeply as utilisation approaches 100%. Decision trees and expected value structure build-versus-buy and risk decisions, and Monte Carlo simulation is used for capacity and cost forecasts.
Unit 5: Project and strategic management
Project management techniques
PERT and CPM schedule projects as activity networks (see Software Project Management). PERT uses three time estimates per activity: expected time = (a + 4m + b) / 6 and variance = ((b − a) / 6)². The critical path is the longest path; float is the slack on other paths. Crashing shortens a project at minimum extra cost.
Strategic management
Strategy sets the long-term direction and how the organisation competes.
| Element | Description |
|---|---|
| Vision, mission, objectives | Where we want to be, why we exist, measurable targets |
| Environmental scanning | PEST/PESTLE analysis (political, economic, social, technological, legal, environmental) |
| SWOT analysis | Strengths and weaknesses (internal), opportunities and threats (external) |
| Porter’s Five Forces | Rivalry, threat of new entrants, substitutes, buyer power, supplier power |
| Generic strategies | Cost leadership, differentiation, focus |
| BCG matrix | Products as stars, cash cows, question marks, dogs by market share and growth |
| Value chain | Primary and support activities that add value |
| Corporate strategies | Growth, stability, retrenchment; diversification, mergers and acquisitions |
The process: formulate the strategy, implement it (structure, resources, culture) and evaluate it, with tools such as the balanced scorecard (financial, customer, internal process, learning). Other topics: corporate governance, business ethics and social responsibility (CSR), entrepreneurship, and management information systems (MIS) and ERP that support decisions.
Today: SWOT and Five Forces appear in business cases and vendor comparisons (for example, choosing a cloud provider and understanding supplier power and lock-in). Technology strategy decisions, such as build versus buy, a multi-cloud approach or entering a new market, are strategic management. Startups use lean ideas, the BCG matrix thinking applies to a product portfolio and OKRs cascade vision to team goals.
One-minute recap
| Unit | Key idea | You meet it in |
|---|---|---|
| 1. Management and organisation | Functions of management, Fayol, Taylor, Mayo; org structures | Team and platform structures, tech-lead roles |
| 2. Operations and quality | EOQ, TQM, Six Sigma, lean, control charts | Waste in pipelines, Kanban, anomaly alerting |
| 3. HRM and behaviour | Maslow, Herzberg, appraisal, leadership, change | Hiring, retention, OKRs, engineering culture |
| 4. Operations research | LP, simplex, transportation, queues, decision trees | Capacity planning, pod placement, risk decisions |
| 5. Project and strategic management | PERT and CPM, SWOT, Five Forces, BCG, balanced scorecard | Business cases, vendor choice, technology strategy |
Next in Engineering Revisited: Network Management Systems.
Written by Claude, Anthropic’s AI assistant, as part of Engineering Revisited, a quick refresher of the B.Tech subjects one at a time.