The Earned Value Management System (EVMS) is adopted as a method of progress management in PMBOK (A guide to the Project Management Body of Knowledge). It has not widely accepted in the field of software development in Japan as a tool for progress management yet. Though the more cost reduction will be inevitable. In this situation, the need for EVMS will intensify. This paper will describe how to make full use of EVMS as a progress management tool in the software development for Project manager.

View full abstract

It is said that a Project Management using EVM has several merits. For instance, it enables quantitative time management, and it enables to get hold of changing cost according project progress. In the system development area, Japanese Government's announcement of "Changing the government procurement institutions for IT system procurement" shows the direction of using EVM in IT system development. The need of EVM application is expanding rapidly. However, when we try to apply EVM in a system development, we sometime have difficulty in practical business, especially in execution phase in which we evaluate progress and cost performance rater than in planning phase. A system development has a peculiar problem in application of EVM because the development cannot define detail WBS until some designing task is done. For an effective application of EVM, we should find a reasonable way to use EVM in a task level. In this paper, for an application of EVM of practical system development, I would like to find the difficulties and the solutions for them and describe an approach to the practical application of EVM.

View full abstract

When e-business is expanded, the customer has required that we build a system at a short period of time and low cost rather than before. Therefore, our company is promoting improving the accuracy of a plan, and attaining a target certainly through practicing the project management by PMBOK. Those activities are a part of the process improvement activities that utilized CMM model. Furthermore, we are also promoting the introduction and spread of support tools for the purpose of practicing project management effectively and efficiently. This report was written based on the opinion and question from users when introducing and spreading MS-Project at a project. In this report, we present the bottom line of utilizing MS-Project in alignment with the view of time management, and the example that fixed and spread the support tool that cooperated with MS-Project.

View full abstract

Critical Path Method technique is very popular and seems to be a main stream methodology of Project Management area, as it is well described in PMBOK guide book. On the other hand, TOC-PM, that adopting Critical-chain-methodology, has also been famous especially in US and Europe, is now focused in Japan very recently, as it proved many actual improvements onto the actual Projects. TOC-PM has many unique characteristics compared with other methods. This paper mentions about human behaviors which is one of the unique characteristics which TOC-PM have, and I will describe how it affect to the variance of duration of project. I also would like to mention about human behavior characteristic will influences how it is effect for the shortenings to the IT-system development area

View full abstract

For researching of TOC, we attempted to apply the theory to real world and find out where are the difficulties will be. Because the data collected from practice might not be enough, it was necessary to presume there are some rate-determining steps hiding in the raw data, and devise methods for processing and analyzing the data based on them. With this assumption, we tried to find out how to implement TOC in the right way by deploying it on a small model, and then proved the effect of TOC. After knowing the process of applying TOC to the model, it will be noticed that TOC is really effective and can be improved. In this case of the small company, the average production days was reduced from 4.64 days to 1.41 days, the delay of delivery became 0,and the most excellent result was that the hills of stock in processing had been found here and there were disappeared. Consequently, it was possible to make the procurement of materials become much closer to the delivery of goods, and then the material stock also had an obvious decrease. Finally the cash flow became much better. On next step, we will try to collect more accurate data and find out where is upper limit to increase orders without delay of delivering goods to customers.

View full abstract

Project management (PM) has been continuously developed by adopting PERT and EVA methodologies by the experts. Finally it was authorized and published onto PMBOK and P2M guidebook as a body of knowledge of the project management. It is not easy to complete each project as originally planned, though PM-knowledge has been well organized. Furthermore, there is a strong and common needs for the PM's environment, that is, "Shortening the lead time of the project", and/or "Effective use of important resources". No one provided a clear answer for that. I also have had the same concern about that, although I have had various and long experience of the product development projects. Recently, I had an opportunity to learn about TOC-PM's contents in deeply and found that those answers were in TOC-PM Methodology. Those are "How to realize shortening of the project L/T, how to manage resources, and how to manage multi projects in reality". I am pleased to have an opportunity to introduce the abstract of TOC-PM. This paper mentions about the summary of TOC-PM from following point of view, "To realize shortening lead time of the project in the research and development environment".

View full abstract

It is said in the upstream software development of IT systems development that progress management is very difficult. The greatest reason is clear in the determination of the result thing unit of analysis and a design, grasp and estimate of the amount of whole, and a guarantee of quality from the viewpoint of anyone-it is because a form cannot be carried out. But, if work of this upstream software development and management of a result thing are not carried out correctly, the reliability of the result thing of upstream software development will become low, and a result which puts greatly the work and the master schedule of subsequent aspects of affairs out of order will be brought. Although the upstream software development of IT systems development project was late from the visitor recently, since there was a request with whether there is any way progress understands where for whether it is a problem more clearly, it was coped with by analyzing the work of upstream software development. Based on these contents, the method of progress management of the upstream software development of IT systems development is considered.

View full abstract

The acquisition management guide compiled by DCMA, a department that belongs to the U.S. Department of Defense, is composed basing on the risk management processes in order to secure high quality in acquisition. In this paper, we study the contents of this guide, and the relation between risk management and quality management, and then discuss on the quality assurance based on the risk management processes.

View full abstract

The exact grasp of risk in project is very important requisite for Project Management. In Software Development, for the purpose of allotment of resource for risk hedge, there are some precedents which are examinations and trials of the risk estimation tool for explanation of risk level and comparison between some Project's risk. In this paper, for risk hedge, we propose the tool, which estimate and visualize the risk on early stage of Software Development, trace the condition of risk until end of the Project, and grasp the key characteristic of risk very easily.

View full abstract

Projects are affected by risks caused by inconsistent scope development. It is, therefore, necessary to trace a risk to its source of mal scopes and prepare counteraction for reducing its propagation. In this study, the authors deeply concerned a general structure of client's scopes and a propagation framework inside the structure.

View full abstract

This study deals with the team building based on the personality score. Big Five Model of personality was used for evaluating personality and impression of members. The experiment was conducted three times. It was investigated the change of each scores.

View full abstract

The outcome of software development projects greatly depends on motivation of the project members as well as the number and competence of them. This paper establishes patterns of problems about communication in the project and makes a communication model focusing on recipience derived from the patterns. We propose the way with recipience for managers to maintain the motivation of the members by Japanesque team management and communication way.

View full abstract

In project execution, team members have to show their team performance to achieve the project goal. In this paper, the authors propose a team performance index based on required tasks in a project and psychological characteristics of each team member. Additionally, the applicability of proposed index is evaluated by an experiment where 30 teams were participated.

View full abstract

These days, the view of project management is introduced widely-not only in a single project but also in two or more projects or through a whole company, and the motion has become strong that it is going to advance actual business with a project style. With such a tendency, the number of the research is on the increase which treats the program management from the viewpoint of the organization theory or training talented people. However, it is not clear what is needed at the place to practice. This paper considers requirements as the base construction for making program management successful. "Platform" -base of cooperation between projects- is taken up from the viewpoint of information system, based on the example implemented as a practice matter in the company.

View full abstract

Current projects of developing information systems are characterized by "short term" and "high quality". It is necessary to communicate tightly among project members, and to collect effective knowledge from the outside. We developed the collaboration tool based on e-mail system for project management and have been used it. We are confirmed that it is useful for effective communication management.

View full abstract

Maintaining a lot of information systems (especially IT-application systems) by an information system department or an IT-business outsourcer has been carried out in many companies. It is one of the most important things that "required knowledge for maintenance" is kept and extended in such difficult situations. Quality-up and productivity-up in maintenance is so, too. In this paper, through a case study of an IT-business outsourcer, one method of "maintenance" using "knowledge management" is stated.

View full abstract

Training of The project manager is an important issue for the organization which accepts an order of the system development project as a business. So, we, our company promoted Readership and motivation training. This report says about an approach to the development of project management ability in the Readership and motivation training.

View full abstract

Our company is promoting the continuous process improvement for the purpose of offering the high quality solution to which a customer is satisfied, and we have achieved the level 3 in some enterprise fields. However, project members are not satisfied still more to an improvement result, as a following stage, they have demanded the improvement of accuracy of estimation by feedback of measurement data. In this report, we present about establishment of the estimated technique, and analysis of measurement data.

View full abstract

In order to obtain the primary data for the derivation of effort estimation model based on Object Points analysis, the analysis of the actual effort data corrected from the development of Client / Server Systems are tried by using statistical method. Results show that 1) the relationships between the size and the effort are linear. 2) the development experience of personnel and the type of programming language used are found to have an influence on the productivity.

View full abstract

As a basis of project size estimation, we have studied quantity of testing (the number of test cases). In this study, we have found that the number of test cases of the certain testing has a strong correlation with the effort of project through an analysis of a project's metrics data which is stratified by their attributes. In this paper we report our partial practical estimate-models, and also we discuss the possibility of the project size estimation technique as a new solution.

View full abstract

It is important for 「Migration of Langauage Environment」 as one project to plan it's working plan at initial phase as well as anoter project. This paper discuss the best way to raise precision in working plan under shotage of project's information. Also, this paper discuss the relation of working plan and test.

View full abstract

We have often heard the organization with ISO9000 approval saying that they obtain no effect and become a mere facade so that it doesn't contribute to the improvement of quality and ability of organization. They also don't know how to set about to break through the stultified improvement activities. Therefore by conducting questionnaire survey for applicability of ISO9000,which is focused on effectiveness and load (on effort of work and on one's mind), we were able to develop and implement the plan which enable us to know what activities to take to maintain and improve the effective and efficient quality management system (QMS).

View full abstract

The importance of the quality management in a system development project is needless to say. The quality management in the project management becomes more important and influences a success of the project, as the scale of the project grows larger. We developed the gateway system for the cellular phone, which had 39million user in 2003 from 2001. In this paper I consider the key points of the quality management based on the know-how that I acquired through the development of the gateway system.

View full abstract

ISO15408 is an international standard for security evaluation which defines how to design and evaluate the security functions of an information system or a system component. To obtain ISO15408 certification, the system maker has to present an independent evaluation facility with all security-related materials produced in the system development. As the materials should be well organized to be evaluated by the third party, this additional procedure inevitably increase the development cost. To deal with this problem, we set some rules in the development process and developed a document management system. When a developer writes a design document, the developer marks the security-related part in the document with some information to denote how this part is related in the whole security function. The document management system analyze the marks and organizes the materials automatically. In this paper we show how this management system works.

View full abstract

The success of a project often hinges on the workload estimation, especially in early stages, by the project manager. This is because such workload estimation becomes the basis for the sponsors to make business decisions on cost and resources. Unlike traditional businesses, however, the workload estimation in the IT industry is still premature. This paper examines the reasons for the complex nature of workload estimation in IT projects and discusses how it may evolve in the future.

View full abstract

In a systems development project, the improvement in productivity of application development, the improvement in quality, and the improvement in conservativeness serve as a key factor of cost reduction. By applying an "Application Framework" in an "Open Mission Critical System" development project, improvement in productivity, quality, maintainability and the cost reduction accompanying improvement in conservativeness. The example is introduced here.

View full abstract

Establishment of the standard WBS, how it is tailored to meet the project's needs, identification of work products for each work package, and how the project schedule is established based on the WBS are described. The aim of these activities is to enhance quantitative project management. As a matter of fact, collecting the data on development size, effort and cost foreach work package provides more detailed way of quatitative project management. As a result, it enables us to statistically analyze the process performace data.

View full abstract

In the mixed section in outsourcing and system integration, developers used to have job of both area, and it's difficult to manage their actual job. This describes about actual management technique and points of analysis actual report.

View full abstract

NEC has been performing "the project management audit program" in these three years. This program is promoted based on training for project managers and information-sharing of management data. Project audits performed by document review, face-to-face interview, and on-site assessment. This paper shows the formats used for the audit and the points for each audit step, and describes benefits and issues on this program.

View full abstract

[in Japanese]

View full abstract

To manage software development project successfully, it is necessary to break tasks down into a clear plan. However, additional tasks suddenly occur during the project execution, since the people concerned to the project contracts additional promises, or since the project purpose are hindered by pending questions. For this reason, the project plan needs to be updated to reflect these tasks. There are following problems to update the project plan : when there are several tasks for one promise or problem, it is hard to grasp the relationship between these tasks. And, when tasks must be done at specific a stage of the plan, the relationship between the tasks and the stage must be visible to avoid postponing or forgetting to solve the tasks. These problems cannot be solved by using only the work breakdown structure (WBS), because the relationships between promises, problems, and tasks are different from the relationships between the works of the project WBS. In this article, we propose a methodology for managing promises and problems by using tree structures for the relationships between promises, problems, and tasks, and connecting the tasks to the WBS stages. Additionally we describe the system to support the software development using the methodology.

View full abstract

The idea that the medical and health care process should be considered as service activity is accepted by general. The change of the quality of medical treatment is required by the severe conditions, for example, the new requirement of patients and/or the cost problems. Project Management, which has many good experiences in industrial sector, will be considered as an effective method to solve such problem in medical treatment. In this paper, the application of the project management to the most fundamental clinical medical activity called hospitalization is discussed. The competition of characteristics between the medical activity and IT project shows the homogeneity of them in basic approach. This result shows the possibility that project management would solve the problem in the medical activities..

View full abstract

This paper is an example of new seminar development in a project manner. We are seeking if our activity can be defined as a project, and if it is appropriate as a project, how we can apply our activity to the PMBOK processes. Our activity is characterized as we were facing following challenges. 1) All project members were volunteers. 2) Some members have been taking part in this project in a distant location. We'd like to describe how we could deal with these issues.

View full abstract

CMMI model which CMU/SEI developed is the compilation of best practices in software development process. CMMI model is more complete than other CMM model. In relation to CMMI CMU/SEI trains the advanced talented people that it is represented by the Lead Appraiser. Therefore people of the world who is related to software process improvement, have a interest in CMMI model. However CMMI model is a process model but not a process itself. We must consider approach to apply CMMI model for as a process which we can practice. In this paper, we mention how we applied CMMI model for establishing our organization's standard process. And we mention how we promoted our organization's standard process to our staff in the field.

View full abstract

Our company is aiming at offer of a quality solution which a customer satisfies, and at achievement of the business goal, is promoting the process improvement based on the (CMM)^[○!R] for the purpose of carrying out a project as planned. Consequently, we attained the level 3 in December 2002 in the section for an improvement which used as the base (SW-CMM)^[○!R], attained in June 2003 in the section for an improvement which used as the base (CMMI)^[○!R]. In this paper, we introduce the improving point in systematic process improvement activities that used (CMMI)^[○!R] as the base, and its effect.

View full abstract

This document describes details of introduction of (CMMI)^<SM> to the software company, where the ISO9001 and ISO9001 : 2000 are already authenticated and fully deployed. It covers evaluation of the (CMMI)^<SM> and the coexistence with the ISO9000. It also states comparison of (CMMI)^<SM> with ISO9001 : 2000.

View full abstract

Many IT system projects go wrong by the difference in the recognition to the scope between the vendor and the customer. It is not only because the customer cannot present detailed requirements at the time of estimate or contract negotiation, but also because many vendors in Japan often show an infeasible estimate by ambiguous expression owing to severity of bidding competition. By exchanging the scope statement which describes the scope definition of the services with which the vendor provides the customer, it is possible to aim at avoidance or mitigation of this problem. This paper concretely describes the contents and effects of the scope statement.

View full abstract

The purpose of this paper is to define "the PM seven tools" and to clarify the application of the tools for successful project. The PM seven tools include Work Breakdown Structure (WBS), Network diagram, Gantt chart, Earned Value Management (EVM), brain storming/KJ method, graphic representation and checklist/template. The PM seven tools are basic tools and broadly support project management activities. In addition, we think that the PM seven tools are effective not only in operation of project management but also in learning basic concepts of project management.

View full abstract