Monday 24 January 2022

How simple is to defining purpose of project management?

If you want to absorb knowledge and know-how related to project management such as PMBOK(Project Management Body of Knowledge) and challenge project management, let's return to the beginning.

"what is the purpose of project management in the first place?"

in fact, even project leaders who have acquired project management methods, knowledge, know-how, etc. often manage projects without knowing what they need to know before, not just the basics.

ask yourself and your team members if they have a good understanding of the purpose of project management. if you don't get an answer right away, it's a red light. projects that you are about to start or are currently working on may fail.

even if you don't go through failure, you'll end up without getting enough results. it's so important that you understand or don't understand the purpose of project management.

this time, i would like to explain the purpose of project management. in fact, as many people as possible can understand the original purpose and elements of project management, such as not clearly understanding the purpose of project management or forgetting the original purpose.

project management objectives

the reason why the original purpose of project management is not understood is also the word "project management". what it means is that the word management is simply to meet a fixed budget and delivery date and create a system or product that meets specifications.

protecting budget, delivery time, specifications (quality) = qcd is a matter of course in project management, and is the basic "ki". protecting qcd is an important part of project management. however, it understands itself as the purpose of project management.

far from exceeding customer expectations, we present systems and products as expected, and we complete the project without knowing whether it is a success or a failure. this is a project that does not benefit both the company and the customer. instead of having qcd as your primary objective, there must be a business to achieve with that project. shouldn't you be aware of the purpose of the project from the perspective of business?

the "quality" required by customers is changing

in information systems and manufacturing sites in the early 1990s, project management was aimed at providing products that were requested by customers with as short delivery times, low cost, and high quality as possible. the customer didn't want to do more, so they were able to focus solely on qcd management.

however, in the mid-1990s, the quality changes that customers demanded began. until now, products that pursue only qcd have not been satisfied, and if we do not provide originals for each customer and what we need at the necessary time, we will not be evaluated.

some people say, "delivery time is also one of the quality!"

however, the era of making high-quality products at low cost and with short delivery times will gradually come to an end.

that's why the elements required for project management have also changed dramatically. what was good only for qcd management has become essential for management from a management perspective.

the purpose of project management is not only to manage qcd, but also to comprehensively manage the process leading up to it, and to deliver what the customer wants at the right time.

what is the other purpose of project management?

in the field of software development and product development, customer requirements tend to become stricter year by year. in addition to high quality, low cost, and short delivery time, there are many cases where people demand added value.

not many companies are competitive enough to keep their opinions and still win deals in response to these customer demands. everyone is more or less desperate to compromise and meet the customer's needs. there are many companies whose projects are "barely in the red every time".

in order to maximize profits even in demanding requirements, it is important to thoroughly manage projects and reduce overall costs. simply put, the cost of developing a single software product is as low as possible and the profit margin is increased.

however, since the quality cannot be reduced, it is not a good idea to reduce the cost of work such as work on the development process. in fact, if you look around the entire project with a broad perspective, you will notice that there are surprisingly many "wastes".

for example, the approval flow for a product design. if it takes a week for a lot of approvers to just turn the flow around, the project will be delayed and labor costs will be high. simply reducing this to a day is probably a significant cost savings.

another purpose of project management is to increase profit margins by quickly discovering and resolving these wastes.

elements of project management

The pmbok that appeared at the beginning was a systematic compilation of project management methods and know-how by the Project Management Institute (PMI), an American non-profit organization, 30 years ago. Today, this PMBOK is the "Bible" of project management and has penetrated all over the world.

pmbok classifies knowledge about project management into 10 knowledge areas. in addition to the three areas of q (quality) c (cost) d (delivery date), which is the final goal of the project, there are a total of 10 knowledge areas, including six areas such as procurement management, risk management, scope management, personnel management, communication management, and stakeholder management, as well as "integrated management" that manages the entire project.

integrated management

we aim to promote the entire project by integrated and managing detailed project management knowledge areas such as project start and end, control and command, etc.

cost control

manage the overall cost of a project, such as pre-production in addition to cost control, budget control, and so on.

procurement management

we manage suppliers in the manufacturing industry and contractors for software development to prevent project delays caused by external stakeholders such as suppliers.

risk management

it is very rare for a project to carry as originally planned. risk management anticipates and responds to potential problems to avoid risk.

scope management

clarify the project guidelines by dividing them into two types: the project scope of "what to do" and the "what to make" deliverable scope.

key management

it is management to grasp the load situation of each project member, sort tasks, and realize the right person in the right place.

communication management

by managing communication within project members, we aim to promote the project smoothly.

schedule management

accurately manage your plans and achievements using gantt charts and more. it is also important to manage the system so that it is flexible to respond to planned changes.


in addition to simply managing quality, you can manage even quality testing tasks to make your quality management schedule more efficient.

stakeholder management

we aim to promote projects smoothly as a whole by managing not only external customers and suppliers, but also project members and related parties as internal stakeholders.


i forgot the original purpose of project management. or, if you did not know the original purpose, i would like you to keep in mind the contents introduced this time. in recent years, it is important to incorporate the concept of project management not only for those engaged mainly in project management, but also for individual engineers. i hope that those who do so will have a deep interest in project management in the future.


No comments:

Post a Comment