there are various "frameworks" in the world. from basic things such as "5w1h" and "pdca", "3c analysis", "swot analysis", "pest analysis", "vrio analysis", etc. the advantage of using the framework is to organize thinking and information that does not progress even if you think vaguely, and to make it easier to get hints to solve problems of individuals and organizations. i think readers have used some kind of "framework" and felt the effect.
The "framework" mentioned above is called a business framework, but there is a representative "framework" called PMBOK in project management as well. For details of PMBOK, it is written in "Project Management Course" written by our representative Umeda, so please read there.
pmbok is a "framework" for a successful project, but if it is introduced, will the project succeed? unfortunately it doesn't seem to be. companies with many pmp qualifications are still suffering from failure projects. that's because pmbok has a strong conceptual element and doesn't show as specific a way as a business framework.
By thoroughly utilizing the PROJECT management tool SI Object Browser PM (OBPM) that complies with PMBOK, we have incorporated the concept of PMBOK as a more practical "framework", realizing rational project management.
this time, i would like to introduce the "framework" of project management that we are using based on some of the functions of obpm.
This is an integrated project management tool with 150 deployments today. Developed and released by us eight years ago, we continue to use it as a heavy user, making a significant contribution to improving our project management operations. There are only tools that claim to be PMBOK compliant, and the functions are diverse. In addition to quality(Q)man-hour cost(C),progress(D),there are all the functions necessary for project management, such as personnel management, communication, risks, issues, etc. One of the distinctive features of OBPM is the "domain" function. This "domain function" is the "framework" of project management.
here are some of the 15 standardization items that are particularly useful as frameworks:
As the name 2010, this standardization item 2010 WBS(Work Breakdown Structure) It is a "framework" in creation. By preparing the processes and tasks that always occur for each project type, the deliverables created in it, and the pattern of review for the deliverables as a "framework" in advance, it is possible to eliminate omissions during project planning and at the same time reduce the wasted time on planning. PL For inexperienced people, it can help you think about how far you need to break down early in the project, what deliverables you create, and more to avoid missing outs.
process task deliverable registration screen
This standardization item is a "framework" of the check criteria when performing work quality checks and deliverables checks for each process of the project. By preparing the quality standards that must be cleared at a minimum as a company or the quality standards required for each customer as a "framework", we can improve the quality. Not only can quality checks be carried out on a different basis for each person, but also as > previous < process task deliverable<b10>registration, pl For inexperienced people, you can learn the points of quality assurance to be considered.
quality standard registration screen
this standardization item is a "framework" for raising risks that must be considered for each project type. It is used to prevent troubles in the post-process due to risk consideration omissions. For pls, etc., which are similarly inexperienced in the previous two, it will exert a significant effect in eliminating the risks to be considered.
Risk list screen
advantages and disadvantages of the framework again, the advantage of using the framework is to organize vaguely thinking and information that doesn't go ahead, making it easier to get tips on solving individual and organizational issues.
it is a "framework" that can expect the same effect in both business and project management, but of course there are disadvantages. it's about relying too much on the framework. if it's a business framework, there can be a point of view of thought. since it is a major premise to think in "framework" = "framework", even though it is necessary to think from other perspectives, thinking only within the prepared "framework" may limit thinking.
In project management, covers the perspective, and it is unlikely to have disadvantages like a business framework, but a detailed "framework" that is too close to practice will deprive you of the opportunity to think with your own head. By using it after understanding that there are such disadvantages in the "framework", you can exert a greater effect.
Summary
This is a framework that should be introduced to improve project management operations. However, in order to obtain a practical "framework" and effect, it is necessary to think together with tools and systems. Excel and free tools can do things, but of course there are limits. Until nine years before we developed by, we tried to realize pmbok-based project management with a framework called "PYRAMID" based on Excel, but unfortunately it did not work.
The reasons are the limitations of standardization due to Excel's high degree of freedom and the cost of aggregation and analysis. That was born from the reflection. Currently, more than 150 companies that have experienced the same problems and issues have used it to improve project management operations.
Since march this year, it has continued to evolve to improve the project management operations of more companies with the addition of three products: "engineering version", "for lite version it" and "light version for manufacturing". we hope that your company will consider introducing it once.
No comments:
Post a Comment