{"id":70,"date":"2011-10-02T15:43:59","date_gmt":"2011-10-02T06:43:59","guid":{"rendered":"http:\/\/se.is.kit.ac.jp\/~o-mizuno\/wp\/?page_id=70"},"modified":"2016-10-27T23:23:31","modified_gmt":"2016-10-27T14:23:31","slug":"characterization-of-runaway-software-projects","status":"publish","type":"page","link":"https:\/\/se.is.kit.ac.jp\/~o-mizuno\/research\/characterization-of-runaway-software-projects\/","title":{"rendered":"Characterization of Runaway Software Projects"},"content":{"rendered":"
\nWe focused on the “runaway” software projects and tried to characterize them using software process metrics.<\/p>\n

During the process of software development, senior managers often find indications that projects are risky and take appropriate actions to recover them from this dangerous status. If senior managers fail to detect such risks, it is possible that such projects may collapse completely.<\/p>\n

We proposed a new scheme for the characterization of risky projects based on an evaluation by the project manager. In order to acquire the relevant data to make such an assessment, we first designed a questionnaire from five viewpoints within the projects: requirements, estimations, team organization, planning capability and project management activities. Each of these viewpoints consisted of a number of concrete questions. We then analyzed the responses to the questionnaires as provided by project managers by applying a logistic regression analysis. That is, we determined the coefficients of the logistic model from a set of the questionnaire responses. The experimental results using actual project data in Company A showed that 27 projects out of 32 were predicted correctly. Thus we would expect that the proposed characterizing scheme is the first step toward predicting which projects are risky at an early phase of the development.<\/p>\n

Related paper<\/h3>\n