Functions of Management in Business Organizations

Managers perform certain activities or duties as they effectively and efficiently coordinate the work of others. In the early part of the twentieth century, a French industrialist named Henri Fayol first proposed that all managers perform five functions: planning, organizing, commanding, coordinating, and controlling. In the mid-1950s, a management text book first used the functions of planning, organizing, staffing, directing and controlling as a framework. Today, most management text books still continue to be organized around the management functions, although they have been condensed to four basic and very important ones: planning, organizing, leading, and controlling. Let us briefly define what each of these management functions encompasses.

If you have no particular destination in mind, then you can take any road. However, if you have some place in particular you want to go, you have got to plan the best way to get there. Because organizations exist to achieve some particular purpose, someone must clearly define that purpose and the means for its achievement. Management is that someone. Managers perform the planning function, define goals, establish strategies for achieving those goals, and develop plans to integrate and coordinate activities.

Managers are also responsible for arranging work to accomplish the organization’s goals. We call this function organizing. When managers organize, they determine what tasks are to be done, who is to do them, how the tasks are to be grouped, who reports to whom, and where decisions are to be made.

Every organization includes people, and a manager’s job is to work with and through people to accomplish organizational goals. This is the leading function. When managers motivate subordinates, influence individuals or teams as they work, select the most effective communication channel or deal in any way with employee behavior issues, they are leading.

The final management function is controlling. After the goals are set (planning), the plans formulated (planning), the structural arrangements determined (organizing), and the people hired, and motivated (leading) there has to be some evaluation of whether things are going as planned. To ensure that work is going as it should, managers must monitor and evaluate performance. Actual performance must be compared with the previously set goals. If there are any significant deviations, it is management’s job to get work performance back on track. This process of monitoring, comparing, and correcting is what we mean by the controlling function.

Project Management Intersects With Business Analysis

Business Analyst skills are important to have on the project team, and not a bad thing for a Project Manager to have! In either case, the business analysis function is one that needs to be managed with care and the wisdom of experience. This entails putting the business analysis function into perspective.

Consider the roles that business analysts typically play: requirements management, systems analysis, business analysis, requirements analysis, or consulting. One key concept within the framework of a project is that the business analysis process does not just happen once. It is not just executing on a task in the Work Breakdown Schedule. It is a task that takes continuous monitoring, and it starts at a high level near the beginning of the project.

Here are some key timeframes within the project lifecycle where business analysis comes to the forefront:

1. Enterprise Analysis and Making a Business Case – Each project must fit into the plans of the organization as a whole. In depth familiarity with that plan, and understanding where the subject project fits into that is a key step in building the business case. The business case must align with the strategic objectives of the organization.

2. Requirements Planning – Developing requirements is a challenge in part because of the time dimension. Requirements planning needs to describe a phased approach that forecasts and schedules how the requirements will unfold. It thus should have, as an output, a schedule for various time-based requirements gathering and documenting tasks.

3. Requirements Management – Managing requirements as they evolve is an important task. In some organizations there is a formal Configuration Management function. There are many Configuration Management business applications out there for requirements. It is important to understand the degree of complexity, the expected level of change or evolution over the course of the project, and the risks involved related to requirements change developments.

4. Eliciting Requirements – Drawing requirements out of various stakeholders is as much an art as a science. The science part provides a framework, usually in the form of ways the structure questions, common pitfalls, and how to document. However, it is an art to develop rapport with varying stakeholders and probe deeply to uncover the core needs.

5. Requirements Analysis and Models – The documentation of requirements is important to assuring that everyone is “on the same page”. Often this requires developing sophisticated architectures, drawings, mathematical models, and prototypes that consolidate requirements input and reflect back to stakeholders the proposed solution. This provides further subject matter for conversations around the continuously unfolding requirements.

6. Communicating and Implementing Requirements – With a given set of requirements, the business analysis function must assure stakeholder buy-in, but also must ensure that those who will implement the requirements are equally “plugged in”. One challenge is to ensure that the stakeholders are in clear and in agreement with what will be implemented, and the implementers are clear on what they need to do. Due to the detailed and often technical nature of the work, work packages at the implementation level are well removed from the stakeholder, so the business analyst servers to bridge that gap and “broker” that relationship.

The Project Management and Business Analysis functions do overlap, but are distinctly different. The Project Manager is concerned with the totality of the project, and is concerned mostly with ensuring progress against schedule, risk management and mitigation, and delivering of the product of the project on time, within budget, and to specified quality standards. The Business Analyst focusses on defining the product of the project and ensures it meets the targeted business needs. This job is a project lifecycle function and does not end until the stakeholders verify that the product meets their requirements. A combination of Project Management and Business Aanalysis skills is quite valuable, and only benefits the project, program, organization, and professionals in their careers.